Both formats: the Word file is the one you edit, the PDF is for reading, printing and circulating. Adapt them freely — once you download them they are yours, and there is nothing to attribute.
Download Word (.docx) · 67 KBDownload PDF · 191 KB
This document states what your organization tests, why, who does it, and how you will know whether it is working. It is the parent document: the integration, regression and acceptance strategies each refine one part of it and should not contradict it.
What is inside
- 1. Purpose and scope
- 2. What we test today
- 3. Tracing tests to requirements
- 4. Critical journeys
- 5. What we automate, and what we do not
- 6. Test levels and who owns them
- 7. Environments and test data
- 8. Entry and exit criteria
- 9. Defect management
- 10. How we will know this is working
- 11. Roles
- 12. Sign-off
How to use it
- Everything in italics is guidance for you and should be deleted once you have replaced it. Square brackets mark a value to fill in.
- Work top to bottom the first time; after that, treat sections 3 and 4 as living documents and revisit them every quarter.
- Keep it short. A strategy nobody reads governs nothing.
How it ties back to Studio
Each template includes an automation candidate table: a short scoring pass over the flows you have just listed, asking how often each runs, whether its outcome is deterministic, and whether you control its data. That table is the bridge between a strategy document and an actual suite — it is what turns "we should automate more" into a list of named flows in priority order.
The rest of the set
These four are designed to be used together. The master strategy sets the rules; the other three refine one level each and should not contradict it.
- Master Test Strategy
- Integration Test Strategy
- Regression Test Strategy
- User Acceptance Test Strategy