Test Plan, What & its importance?

Software Test Plan is a rule book for testing process and is vital to keep testing process on the right track.

It is the record depicting the scope, approach, plan and required assets for proposed testing action. In subtleties, it additionally recognizes the things to be tested, things not be tested, entry criteria, exit criteria, risk and mitigation plan.

ISTQB Definition

A report portraying the scope, approach, resources and timetable of planned test exercises.

It identifies others test items, the features to be tested, the testing tasks, who will do each task, the degree of tester independence, the test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice, and any risks requiring contingency planning.

In addition, it acts as a record of the test arranging measure.

Importance of Test Plan

• It serves as a blueprint for testing activity in a defined process, as a result helps the test manager / lead to minutely manage and control testing activities.
• Also helps people outside testing team like Project manager, Business and other stakeholders to understand the testing activities.
• This is also a guidebook for testing process and is vital to keep testing process on the right track.
• Above all, Followed across various tasks in an association by making a standard ace test plan.

Types of Test Plan

Depending upon the scope of testing, Test plans can be of different levels and types,.

• Master – Defined at organization / product level. Usually a high-level document setting standards for multiple levels.

• Phase – For specific feature / interim release / phase. Specifically adheres to guidelines set by the master test plan.
  Also with the Phase test plan, there can be test plans for specific types of testing as applicable. E.g. 
  • Functional – Covers functional testing of a software / phase
  • Security – Covers, Security testing of a software / phase
  • Performance – Covers performance testing of a software / phase

Who writes?

• In majority of projects Test Lead, but sometimes Test manager.

Who Approves?

• Test Manager and all Stakeholders like Project Manager and Business.

Table of content

1. 1. Identifier
   2. Introduction
   3. Test Items
   4. Features to be tested
   5. Features not to be tested
   6. Test Approach
   7. Entry / Exit criteria
   8. Test Schedule
   9. Testing Tasks
   10. Test deliverables
   11. Item pass/fail criteria
   12. Suspension / Redemption criteria
   13. Environmental needs
   14. Tools needed
   15. Resources and Responsibilities
   16. Staffing and training needs
   17. Risks and contingencies
   18. Documents / References
   19. Approvals
   20. Glossary

In addition, There can be a difference of opinion over what to include in a plan so we can follow the IEEE 829 standard to avoid any differences.

Therefore, according to this standard, the essential elements of a test plan include:

• Plan Identifier
• Introduction
• Test items
• Features to be tested
• Features not to be tested
• Approach
• Item pass/fail Criteria
• Suspension and Resumption criteria
• Test deliverable’s
• Testing tasks
• Environmental needs
• Responsibilities
• Staffing and training needs
• Schedule
• Risks and contingencies
• Approvals
• Glossary

Since we read what is test plan and why you need it, in the next article we can know in more detail of each and every element of the test plan.

Finally, Please share your thoughts by commenting.