Phase 5 — Quality & Planning
Test Case Specification
The exact scenarios that prove your multi-space product actually works together
2 min read · Document 21 of 30
What is this document?
The Test Case Specification lists concrete scenarios with preconditions, steps and expected results — especially the cross-space flows most likely to break.
Each test case traces back to a requirement, so coverage gaps are visible.
Why does it matter?
- Unit tests prove parts work alone; test cases prove the whole system works.
- Cross-space flows are tested as users experience them.
- Expected results are specific enough to automate.
What's inside?
- Scenarios — Preconditions, steps, expected results.
- Cross-space flows — End-to-end scenarios across spaces.
- Traceability — Requirement → test case mapping.
Customer ordersPartner acceptsStatus updatesCustomer notified
How CREAH generates it
CREAH builds this document from your Stage 0 answers and interview. Questions that shape it include:
- Which flows cross more than one space?
- What must happen when two users act at once?
- Which errors must be shown to the user?
Example excerpt
## TC-112: Order accepted notifies the customer
Given: a placed order in status "pending"
When: the partner accepts it in the partner app
Then: order status = "accepted" within 2s
and: the customer receives a notification
and: the admin timeline shows both events