Quality Measures

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.

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

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.

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

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

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

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.

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

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.

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.

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?