2026-03-19 18:23:04 +01:00
|
|
|
# Acceptance Test Checklist
|
2026-03-06 00:44:52 +01:00
|
|
|
|
2026-03-19 18:23:04 +01:00
|
|
|
Use this checklist for the Acceptance Tester role.
|
2026-03-06 00:44:52 +01:00
|
|
|
|
|
|
|
|
## Scope
|
|
|
|
|
- all in-scope items from `plan.json` are implemented
|
|
|
|
|
- out-of-scope items are not silently introduced
|
|
|
|
|
|
|
|
|
|
## Behavior
|
|
|
|
|
- each `SC-*` success criterion from `plan.json` is verifiably met
|
|
|
|
|
- negative and edge paths behave as defined
|
|
|
|
|
|
|
|
|
|
## Regressions
|
|
|
|
|
- existing flows still work after change
|
|
|
|
|
- no critical UX break on key user paths
|
|
|
|
|
|
|
|
|
|
## Tests
|
|
|
|
|
- every test listed in `plan.json tests[]` is implemented and passes (QG-001 green)
|
2026-03-19 18:23:04 +01:00
|
|
|
- new Service/Gateway logic has at least one test (GR-TEST-001)
|
2026-03-06 00:44:52 +01:00
|
|
|
|
|
|
|
|
## Evidence
|
|
|
|
|
- each criterion has explicit pass/fail evidence
|
|
|
|
|
- each criterion check references the exact `SC-*` ID
|
|
|
|
|
- fail findings include exact missing behavior
|
