Certified Quality Engineer Interview Questions And Answers

Discuss not only quality control, QA tests, and monitoring of various kinds (materials, products, electrical systems), but also other related tasks that a QA engineer might be responsible for: improvement processes, quality-oriented staff training, and quality-related customer services.

Quality engineers can serve as the link between customers and suppliers. When a customer complains about product quality, the engineer must then solve the problem between the customer, the company, and its affiliates, including material and parts suppliers. Briefly describe some interesting problems that you have successfully tackled.

Quality Engineers interact with employees at all levels, from minor suppliers to organization management. Describe a specific assignment where you had to use your communication skills, participate in a group endeavor or manage/lead a team. Discuss your routine communication with all levels of management, quality managers and inspectors, development engineering divisions, operations and QA testing staff.

Quality Assurance refers to the planned and systematic way of monitoring the quality of process which is followed to produce a quality product. QA tracks the outcomes and adjusts the process to meet the expectation.

Quality Control concern with the quality of the product. QC finds the defects and suggests improvements. The process set by QA is implemented by QC. The QC is the responsibility of the tester.

Software Testing is the process of ensuring that product which is developed by the developer meets the user requirement. The motive to perform testing is to find the bugs and make sure that they get fixed.

Good time to start the QA is from the beginning of the project startup. This will lead to plan the process which will make sure that product coming out meets the customer quality expectation. QA also plays a major role in the communication between teams. It gives time to step up the testing environment. The testing phase starts after the test plans are written, reviewed and approved.

Training and instruction of staff regarding quality issues is necessary as part of quality control. If you have any experience in this field, describe the specific reason and subject of training. Underscore, without arrogance, your accomplishments with the group.

Basic procedure in quality engineering is Continuous Improvement. Describe involvement, method of data collection from observation and monitoring of production processes. Problem-solving skills are the key to success here and you will do well to mention your unique abilities in this area: Problems you solved, corrections you facilitated and improvements you initiated.

★ Verification is Static Testing where as Validations is Dynamic Testing.
★ Verification takes place before validation.
★ Verification evaluates plans, documents, requirements and specifications, where as Validation evaluates product.
★ Verification inputs are checklist, issues list, walk-through and inspection, where as in Validation testing of actual product.
★ Verification output is set of documents, plans, specifications and requirement documents where as in Validation actual product is output.

Destructive testing includes methods where material is broken down to evaluate the mechanical properties, such as strength, toughness and hardness.
For example, finding the quality of a weld is good enough to withstand extreme pressure and also to verify the properties of a material.

★ Verifies properties of a material
★ Ensures compliance with regulations
★ Determines quality of welds
★ Helps you to reduce failures, accidents and costs

★ The subset of software which helps in performing the testing of application.
★ Testware are required to plan, design, and execute tests. It contains documents, scripts, inputs, expected results, set-up and additional software or utilities used in testing.
★ Testware is term given to combination of all utilities and application software that required for testing a software package.

Testware is special because it has:
1) Different purpose
2) Different metrics for quality and
3) Different users

★ Retesting is done to verify defects fixes where as regression is perform to check if the defect fix have not impacted other functionality that was working fine before doing changes in the code.
★ Retesting is planned testing based on the defect fixes listed where as regression is not be always specific to any defect fix. Also regression can be executed for some modules or all modules.
★ Retesting concern with executing those test cases that are failed earlier whereas regression concern with executing test cases that was passed in earlier builds.
★ Retesting has higher priority over regression, but in some case retesting and regression testing are carried out in parallel.

★ When a tester finds a bug .The bug is assigned with NEW or OPEN status.
★ The bug is assigned to development project manager who will analyze the bug .He will check whether it is a valid defect. If it is not valid bug is rejected, now status is REJECTED.
★ If not, next the defect is checked whether it is in scope. When bug is not part of the current release .Such defects are POSTPONED
★ Now, Tester checks whether similar defect was raised earlier. If yes defect is assigned a status DUPLICATE
★ When bug is assigned to developer. During this stage bug is assigned a status IN-PROGRESS
★ Once code is fixed. Defect is assigned with FIXED status.
★ Next the tester will re-test the code. In case the test case passes the defect is CLOSED
★ If the test case fails again the bug is RE-OPENED and assigned to the developer. That's all to Bug Life Cycle.

High Priority and Low Severity:
★ Company logo is not properly displayed on their website.
High Priority and High Severity:
★ Suppose you are doing online shopping and filled payment information, but after submitting the form, you get a message like "Order has been cancelled."
Low Priority and High Severity:
★ If we have a typical scenario in which the application get crashed, but that scenario exists rarely.
Low Priority and Low Severity:
★ There is a mistake like "You have registered success" instead of successfully, success is written.

1) Purchasing the license of tool (QTP, selenium, QC, LR)
2) Lack of skilled Tester to run the tool
3) Expectation that automated tests will find a lot of new defects
4) Maintenance of automated tests
5) Technical problems of tools

★ QA team is responsible for monitoring the process to be carried out for development.
★ Responsibilities of QA team are planning testing execution process.
★ QA Lead creates the time tables and agrees on a Quality Assurance plan for the product.
★ QA team communicated QA process to the team members.
★ QA team ensures traceability of test cases to requirements.

Verification is a process of evaluating steps which is followed up to development phase to determine whether they meet the specified requirements for that stage.

Validation is a process of evaluating product during or at the end of the development process to determine whether product meets specified requirements.

Priority is to concern with application from the business point of view.

Severity is to concern with functionality of application. It deals with the impact of the bug on the application.

Build is a number given to install-able software that is given to testing team for testing by the development team. Build number assigned are incremental and sequential.

Release is a number given to install-able software that is handed over to customer by the developer or tester. The information of build, release and version are displayed in software help page. Using this build and release customer can let the customer team know which release version build that are using.