Test planning services
For teams shipping to a deadline with no agreed definition of done, teams heading into a regulated audit, and teams whose testing currently ends when the sprint ends. Our team of 50+ QA engineers writes the test plan for your release: scope, entry and exit criteria, environments and risks, agreed with your team and yours to keep.
What we write
A test plan says what will be tested, how, in which environment, and what has to be true before testing can be called finished. If you would rather write it yourself, our guide to writing a test plan walks through each section with a worked example and a template.
What the plan covers
| Section | Description |
|---|---|
|
Scope
|
What is in, and what is deliberately out, so a gap is a decision rather than a surprise. |
|
Test Items
|
The builds, services and API versions under test, so every result traces to a commit. |
|
Features to Test
|
Features ranked by risk and traced to requirements. |
|
Test Approach
|
What is automated, what gets exploratory time, and what we are deliberately not doing. |
|
Entry and Exit Criteria
|
Written as numbers anyone can check, so "testing is done" is a claim with a test. |
|
Test Deliverables
|
Test cases, results per build, defect reports and a one-page closure report. |
|
Test Environment
|
Where testing runs, how it differs from production, and what those differences cannot catch. |
|
Schedule
|
Milestones tied to your sprints and release date, with named owners for each risk. |
How we work
Requirements Analysis
We read your requirements, architecture notes and user stories, and mark what is testable, what is not, and what needs a question answered.
Risk Assessment
We name the technical and business risks with your team and put the most testing where a failure would cost the most.
Alignment With Your Strategy
We fit the plan to the way your organisation already tests, and choose the test levels and types this release needs.
Resource Planning
We set out who tests what, in which environment, with which tools, and who owns each risk.
Documentation and Review
We draft the plan, review it with your dev lead and product owner, and keep it current when scope changes.
What you get
One Agreed Document
A written plan your developers, testers and product owner have agreed, covering scope, approach and timing.
A Risk Register
Every risk named with its impact, mitigation and owner, so the ones your team already suspects get written down.
Checkable Exit Criteria
Exit criteria written as numbers, so whether testing is finished is something anyone can check.
A Record for Audits
A document you can show an auditor to explain what was tested, why, and against which criteria.
Standards we work to
Talk to us about your test plan
Tell us what you are releasing and when. We will write the plan with your team, starting from the risks you already suspect and have not written down.