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) · 66 KBDownload PDF · 128 KB
Integration testing proves that components agree at their seams. It is the level most often assumed to be covered by somebody else, which is why the seam between two well-tested systems is such a reliable place for defects to live.
What is inside
- 1. Scope
- 2. What each integration test proves
- 3. Contracts and expectations
- 4. Environments, stubs and the systems you do not control
- 5. Timing across systems
- 6. Carrying a value between systems
- 7. Automation candidates
- 8. Entry and exit criteria
- 9. Ownership
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