In contrast to the Test Strategy, the Test Plan document defines the actual testing scope for a particular product or a particular phase within a product development. In other words, your company might decide that the software will be released in 3 stages and each stage will require complete testing before being released to the public. It could even be that, during each stage of release, there maybe requirement to create a test plan for each phase of the testing, e.g. Integration Testing, System Testing and User Acceptance Testing.
In other words, a Test Plan could exist either for a single release of software or single stage of testing phase. Either way, the content should remain pretty much the same for both cases.
A test plan states what features to be tested, what features not to be tested and why, at what level they will be tested, what order they are to be tested in.
The purpose of a test plan is to provide a plan of verification that the software produced meets the functional or design requirements or specification.
The following is a typical content of a Test Plan (formalised as IEEE 829-2008 standard):
The following is a typical content of a Test Plan (formalised as IEEE 829-2008 standard):
- Test plan identifier
- Introduction
- Test items
- Features to be tested
- Features not to be tested
- Approach
- Item pass/fail criteria
- Suspension criteria and resumption requirements
- Test deliverables
- Testing tasks
- Environmental needs
- Responsibilities
- Staffing and training needs
- Schedule
- Risks and contingencies
- Approvals
No comments:
Post a Comment