Test planning is the activity producing a definition of how, when where and by whom a software product will be tested within a project. In other words how all aspects of testing will be managed in order to deliver a software product that satisfies agreed acceptance criteria.
The main document produced by this activity is the test plan which is also known as
- project test plan
- test management plan
The contents of a test plan should include an overview of
- scope of testing
- test environment
- schedule
- resources
- tools
A test strategy document should ideally exist as a generic guide to how all test projects within your organisation should be managed. The test plan therefore need only refer to relevant sections of the test strategy unless the project requires deviation from the strategy. An example of deviation could be where the test strategy calls out for regression tests to be created after manual test execution. The project however may require that regression test scripts are to be produced in parallel with system test script creation due to time constraints.
Log in using your favourite account and write your comments here