Steps to prepare test plan:
Like any project, the testing also should be driven by a plan. The test plan acts as the anchor
for the execution, tracking and reporting of the entire testing project. Activities of test plan:
- Scope Management: Deciding what features to be tested and not to be tested.
- Deciding Test approach /strategy: Which type of testing shall be done like configuration,
integration, localization etc.
- Setting up criteria for testing: There must be clear entry and exit criteria for different
phases of testing. The test strategies for the various features and combinations determined
how these features and combinations would be tested.
- Identifying responsibilities, staffing and training needs.
- Identifying resource requirements
- Identifying test deliverables.
- Testing tasks: size and effort estimation.
OR
- Test Plan is a document that is the point of reference based on which testing is carried
out within the QA team.
- Test plan is not static and is updated on an on demand basis.
- The more detailed and comprehensive the Test plan, the more successful the testing
activity.
- The test plan keeps track of possible tests that will be run on the system after coding.
- The test plan is a document that develops as the project is being developed.
- Record tests as they come up
- Test error prone parts of software development.
- The initial test plan is abstract and the final test plan is concrete.
- The initial test plan contains high level ideas about testing the system without getting
into the details of exact test cases.
- The most important test cases come from the requirements of the system.
- When the system is in the design stage, the initial tests can be refined a little.
- During the detailed design or coding phase, exact test cases start to materialize.
- After coding, the test points are all identified and the entire test plan is exercised on the
software.