Vital Product Quality Measures Interview Preparation Guide

Download PDF

✰ 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.

Severity:
Concern with functionality of application. It deals with the impact of the bug on the application.
Priority:
Concern with application from the business point of view.
It answers: How quickly we need to fix the bug? Or How soon the bug should get fixed?

✰ 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.

Bug release is when a build is handed to testing team with knowing that defect is present in the release. The priority and severity of bug is low. It is done when customer want the application on the time. Customer can tolerate the bug in the released then the delay in getting the application and the cost involved in removing that bug. These bugs are mentioned in the Release Notes handed to client for the future improvement chances.

Regression Testing: When changes in the code of the software are made to fix the previous bug. Then testing needs to be perform to ensure that it will not generate a new bug in the application and it works as specified and that it has not negatively impacted any functionality that it offered previously.
Regression Testing is important because of following reason:
✰ That the application works even after the alteration in the code were made.
✰ The original functionality continues to work as specified even after doing changes in the software application.
✰ The alteration to the software application has not introduced any new bugs.

✰ Frequency of use of test case.
✰ Time Comparison (automated script run much faster than manual execution).
✰ Re-usability of Automation Script.
✰ Adaptability of test case for automation.
✰ Exploitation of automation tool.

✰ Application should be stable enough to be tested.
✰ Testing always under time constraint.
✰ Understanding requirements, Domain knowledge and business user perspective understanding.
✰ Which tests to execute first?
✰ Testing the Complete Application.
✰ Regression testing.
✰ Lack of skilled testers.
✰ Changing requirements.
✰ Lack of resources, tools and training.

RELEASE:
It 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 thet are using.
BUILD:
It is a number given to installable software that is given to testing team for testing by the development team. Build number assigned are incremental and sequential.

✰ 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.

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

✰ Sanity testing is performed when new build is released after fixing bugs where as smoke testing is performed to check the major functionalities of the application.
✰ Sanity is performed by the tester or the developer but smoke testing can be performed by the tester or developer.
✰ Smoke testing is performed earlier where as sanity is performed after the smoke testing.
✰ Sanity testing is narrow and deep approach of testing and smoke testing is focused testing based on major functionalities.

✰ 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.

✰ 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.

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

✰ The subset of software which helps in performing the testing of application.
✰ Testware is term given to combination of all utilities and application software that required for testing a software package.
✰ 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.

Benefits of Destructive Testing (DT):
✰ Verifies properties of a material
✰ Determines quality of welds
✰ Helps you to reduce failures, accidents and costs
✰ Ensures compliance with regulations

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.

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.

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.

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.

QA 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.

Availability (percentage of time a system is available, versus the time the system is needed to be available)
Mean time between failure (MTBF)
Mean time to repair (MTTR)
Reliability ratio (MTBF / MTTR)
Number of product recalls or fix releases
Number of production re-runs as a ratio of production runs

Costs of reviews, inspections and preventive measures
Costs of test planning and preparation
Costs of test execution, defect tracking, version and change control
Costs of diagnostics, debugging and fixing
Costs of tools and tool support
Costs of test case library maintenance
Costs of testing & QA education associated with the product
Costs of monitoring and oversight by the QA organization (if separate from the development and test organizations)

Breadth of functional coverage
Percentage of paths, branches or conditions that were actually tested
Percentage by criticality level: perceived level of risk of paths
The ratio of the number of detected faults to the number of predicted faults.

Number of post-release defects (found by clients in field operation), categorized by level of severity
Ratio of defects found internally prior to release (via inspections and testing), as a percentage of all defects
All defects include defects found internally plus externally (by customers) in the first year after product delivery