Keiss Media · Practical resources
Development and testing
Record the build, checks, issues and decision about launch readiness.
- When to use it
- When a build is ready to check against the agreed requirements, and after fixes.
- What you will have
- A test record with evidence, unresolved issues and a named readiness decision.
- What to check
- A planned check is not a passed check. Record actual results before making a readiness decision.
View the worked example
The example is fictional. It shows how to record questions and untested work.
Development and testing: the example drink learning example
All information is fictional. This is not a commission, an acceptance record, a verified result or a required service package.
Status
An illustrative test-record draft. No game checks have been performed.
Version and environment
No working game URL is available. Devices and reviewer have not been assigned.
T01: flavour selection
Expected: the selected flavour and product card remain consistent across screens. Actual result: not tested.
T02: match
Expected: a valid move updates the board, score and meter according to the rules. Actual result: not tested.
T03: completion
Expected: when moves run out, the result, replay and product return are available. Actual result: not tested.
T04: controls
Expected: hints, focus, keyboard controls and flavour distinctions do not depend on colour alone. Actual result: not tested.
Decision
Launch readiness is not established until a working release and test record are available.
Full workflow: https://keissmedia.com/resources/project-workflow/#qa
Download example (.md)Fill in the template
If an answer is unknown, say so. You can leave fields open and record what needs clarification.
Fields work in your browser. Your text is not sent to us or saved after the page closes. Download the document to continue later.
Sources and adaptation
Keiss Media working guidance and learning examples. This route reuses the library’s existing brief, concept, requirements, scope-change, handover and hosting resources. Their sources and reuse terms are given on the respective pages. The new journey, planning and test-record templates connect those resources; they are not an official standard or a contract. User stories and acceptance criteria were checked against the GOV.UK Service Manual; the distinction between objectives and hypotheses follows 18F Methods. The examples were written for the fictional the example drink project.
Version 1.0 · 5 November 2026