Test Plan and Test Strategy

Test Plan:A software project test plan is a document that describes the objectives, scope, approach and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product. The completed document will help people outside the test group understand the why and how of product validation. It should be thorough enough to be useful, but not so thorough that none outside the test group will be able to read it

•Approved Test Strategy Document.

•Test tools, or automated test tools, if applicable.

•Previously developed scripts, if applicable.

•Test documentation problems uncovered as a result of testing.

•A good understanding of software complexity and module path coverage, derived from general and detailed design documents, e.g. software design document, source code and software complexity data.

Outputs for this process:

•Approved documents of test scenarios, test cases, test conditions and test data.

•Reports of software design issues, given to software developers for correction.

Test Strategy

The test strategy is a formal description of how a software product will be tested. A test strategy is developed for all levels of testing, as required. The test team analyzes the requirements, writes the test strategy and reviews the plan with the project team. The test plan may include test cases, conditions, the test environment, a list of related tasks, pass/fail criteria and risk assessment.

Inputs for this process:

•A description of the required hardware and software components, including test tools. This information comes from the test environment, including test tool data.

•A description of roles and responsibilities of the resources required for the test and schedule constraints. This information comes from man-hours and schedules.

•Testing methodology. This is based on known standards.

•Functional and technical requirements of the application. This information comes from requirements, change request, technical and functional design documents.

•Requirements that the system can not provide, e.g. system limitations.

Outputs for this process:

•An approved and signed off test strategy document, test plan, including test cases.

•Testing issues requiring resolution. Usually this requires additional negotiation at the project management level.