Software testing verifies that the software meets its requirements and that it is complete and ready for delivery.

Objectives of QA Testing

1. Assure the quality of client deliverables.
2. Design, assemble, and execute a full testing lifecycle.
3. Confirm the full functional capabilities of the final product.
4. Confirm stability and performance (response time, etc.) of the final product.
5. Confirm that deliverables meet client expectations/requirements.
6. Report, document and verify code and design defects.

Preparing for QA Testing

Prior to conducting formal software testing, QA develops testing documentation (including test plans, test specifications, and test procedures) and reviews the documentation for completeness and adherence to standards. QA confirms that:

1. The test cases are testing the software requirements in accordance with test plans.
2. The test cases are verifiable.
3. The correct or "advertised" version of the software is being tested (by QA monitoring of the Configuration Management activity).

QA then conducts the testing in accordance with procedure, documents and reports defects, and reviews the test reports.

The Key to Productive QA Testing

It is crucial to recognize that all testing will be conducted by comparing the final product to the product’s set requirements; therefore, product requirements must state all functionality of the software and must be updated as changes are made. Any functionality that does not meet the requirements will be recorded as a defect until resolution is delivered.

RELATED POST

QUALITY ACTIVITIES IN SOFTWARE TESTING
QUALITY TESTING COMPLETE