TEST PLAN is a document describing software testing scope and activities.
This is a sample Standard Test Plan template
It is a document detailing the objectives, resources, and processes for a specific test for a software or hardware product. It includes the following:
- Test Plan Identifier
- References
- Introduction
- Test Items
- Software Risk Issues
- Features to be Tested
- Features not to be Tested
- Approach
- Item Pass/Fail Criteria
- Suspension Criteria and Resumption Requirements
- Test Deliverables
- Remaining Test Tasks
- Environmental Needs
- Staffing and Training Needs
- Responsibilities
- Schedule
- Planning Risks and Contingencies
- Approvals
- Glossary
note: The above list is as per the IEEE 829 standard format. See the below template
Above is an exhaustive list. Every organization can decide the contents of the Test Plan based on its needs.
Test Plan Guidelines
- Keep it concise – Avoid repetition and unnecessary items or information. If any of the above sections are not needed, remove from your test plan
- Provide References – add links and references wherever required to other documents or ids
- Be specific. For example, when you specify an operating system as a property of a test environment, mention the OS Edition/Version as well, not just the OS Name.
- Make use of lists and tables wherever possible. Avoid lengthy paragraphs.
- Have the test plan reviewed a number of times prior to baselining it or sending it for approval. The quality of your test plan speaks volumes about the quality of the testing you or your team is going to perform.
- Update the plan as and when necessary. An out-dated and unused document stinks and is worse than not having the document in the first place.
Sample Test Plan Template
References
https://en.wikipedia.org/wiki/Test_plan
https://www.tutorialspoint.com/software_testing_dictionary/test_plan.htm
http://softwaretestingfundamentals.com/test-plan/
