*Disclaimer: This Test Plan Template is based upon a unit test level test.
“A test plan is a document describing the scope, approach, resources, and schedule of intended test activities.” ISQTB, Test Plan
The Test Plan Template documents and tracks the necessary information required to effectively define the approach to be used in the testing of a software project’s product.
Here are some top tips to consider when editing this Test Plan Template Checklist:
- Ensure the plan is concise. Be strict with your plan: If a section isn’t bringing actionable value to the plan, delete it
- Be specific. A test plan template is designed to be edited to meet the specific requirements of that particular test. Be precise and detail exactly which feature you are testing (for example)
- Make sure the test plan is scannable: Avoid long paragraphs and use lists and tables when possible
- A successful test plan requires a team effort: have the test plan reviewed at least once. And, always remember to send it for approval
- Always check you are running the most up-to-date plan. Have you ever started editing something only to find you’ve already made the edits in another location? I certainly have and it wastes so much time!
If you are new to Process Street and would like a bit on an introduction to the app: Check out the video below.
Or, for help on using the awesome features to their full capacity visit our help site.
Just to re-cap the disclaimer before we begin, this Test Plan Template only covers unit testing (testing the code to make sure that it works when standing alone).
Let’s get started!