An acceptance test plan (ATP) lists the tests that show a statement of work (SOW) has been delivered. You and your client agree on it, then run it to decide whether the work is done.
There’s no separate ATP to create or keep up to date. Tanda generates it from the SOW whenever you ask for it, so it always matches the current tests.
What goes into it
The plan follows the structure of the SOW:
- SOW: the work being delivered.
- Task items: the pieces of that work.
- Acceptance criteria: what must be true for each item.
- Tests: the steps that prove each criterion.
Tests are what make it a plan. A criterion with no test has nothing to run, so check coverage before you share it.
Produce an ATP
| From | How | Format |
|---|---|---|
| The app | Export from the SOW | PDF or Markdown |
| The REST API | GET /api/sow/{sowId}/export?format=pdf&variant=procedure on www.testandaccept.com |
PDF or Markdown |
| MCP | get_acceptance_test_plan |
Markdown |
The REST and app exports are the formal document, and also include the rest of the SOW, such as its description and criteria. The MCP tool returns only the criteria that have tests, in a simpler layout, and lists the others separately.
From sign-up to ATP shows the full commands.
Plan or report
The export has two variants:
variant=procedureis the plan: what will be tested, and how.variant=reportadds the results of test runs, so you can share it as the test report.
Find what’s missing
Before you share a plan, make sure every criterion has a test:
- Over MCP, ask your assistant to check coverage. It calls
analyze_coverage, andget_acceptance_test_planalso lists the criteria with no test. - Over REST,
GET /sows/{sowId}/requirements-checklistshows each item with its criteria and tests.