# Development and testing

Status: draft
Project: 
Version: 
Author and date: 
Reviewer: 

## Version and environment

URL, build, date, devices and reviewer.

Not completed.

## Checks

Requirement ID, steps, expected result, actual result and evidence.

Not completed.

## Issues

Reproduction steps, impact, priority, owner and fix status.

Not completed.

## Retesting

Version, fixes, related behaviour checked and areas still untested.

Not completed.

## Readiness decision

Who accepts the work, what blocks launch and which limitations are explicitly accepted.

Not completed.

## Related documents

- [Change and issue record template](https://keissmedia.com/resources/change/template.md)

## 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 CHARGE project.

- [GOV.UK: user stories and acceptance criteria](https://www.gov.uk/service-manual/agile-delivery/writing-user-stories)
- [18F: design hypothesis](https://raw.githubusercontent.com/18F/methods/main/_methods/design-hypothesis.md)