A software test plan forms the core of the software testing process. It is one of the primary things that is required before one actually proceeds with the testing or Quality Assurance. Be it functional testing or any other kind of testing.
2. Definition Of Test Plan
A test plan is nothing but a written document that
in detail describes the activities and the testing
scope.
3. Template Design for a Test Plan
The layout and content of a product test plan
differ contingent upon the standards, processes,
and test management tools being used.
In any case, the accompanying format, which
depends on IEEE standard for software test
documentation, gives a rundown of what a test
plan can/ought to contain.
4. Test Plan Identifier
Assign a unique identifier for the test plan
document.
It can simply be a unique number assigned to the
plan. It helps in identification.
5. Reference
Enlist the names of the related references
alongwith the links, if available, and include these
as well
6. Guidelines for a Test Plan
Make utilization of tables and lists wherever
feasible. Stay away from protracted sections.
Have the test plan checked various times before
baselining it or sending it for approving.
