Checklist of Quality Assurance Activities for a New Release
This document lists the quality assurance activities that should be performed in a software project when developing a new realease of a software product.
- Technical review of product release objectives.
- Analyzing target environments.
A key factor to planning a software project is understanding where the product will be operating. The quality assurance group should develop representative environments.
- Development of the Project Plan (including the Quality Plan).
The plan should for example define
- the project objectives and requirements;
- describe the hardware and software environments;
- estimate the staffing requirement, schedule and budget;
- detail test plan/procedures and
- determine evaluation and measurement criteria to be used as standards.
- Test case development for new enhancements.
When a product needs a regression test to a previous release, only write test cases for extensions of the product.
- Analyze the existing battery of test cases.
It is important to analyze our battery of test cases designed for previous product releases to verify there is no redundancy of coverage. Test cases should be purged, if necessary, or a gapping hole filled by the expansion of a test case.
- Install the product.
- Regression test new release to current release.
Using the new release, the battery of test cases is executed. The results are compared to the standards established for the previous release. Regression testing validates that enhancements have not perturbed existing functions.
- Test new functions and evaluate.
The test cases that were developed in step 4 are now exercised.
- Apply system modifications.
Problems encountered during system testing have to be resolved by correcting the erroneous part of the software.
- Test system modifications:
- Install the modified system
- Execute the test case which originally uncovered the need for the modification
- Execute all other test cases to ensure that the modifications have not perturbed existing functions
- Reject the modification, if it does not fix the problem or if it caused another problem
- Review user documentation.
After testing, the user documentation should be reviewed to verify that all results and messages given in the documentation are correct.
Pfau, P.R.: Applied Quality Assurance Methodology. SOFTWARE ENGINEERING NOTES - Performance Evaluation Review, Vol. 3, No.5, Proceedings of the SOFTWARE QUALITY AND ASSURANCE WORKSHOP, pp. 1-8, ACM, New York, 1978.