168ac96c3a
Introduces a full shift-left QA pipeline with Story Type classification as the backbone of the Definition of Done: New skills: - /test-setup: scaffold test framework + CI/CD per engine (Godot/Unity/Unreal) - /qa-plan: generate sprint test plan classifying stories by type - /smoke-check: critical path gate (PASS/PASS WITH WARNINGS/FAIL) before QA hand-off - /team-qa: orchestrate qa-lead + qa-tester through full QA cycle Story Type classification (Logic/Integration/Visual/Feel/UI/Config/Data): - Logic and Integration: BLOCKING DoD gate — unit/integration test required - Visual/Feel and UI: ADVISORY — screenshot + sign-off evidence required - Config/Data: ADVISORY — smoke check pass sufficient Updated skills: story-done (test evidence gate), story-readiness (Story Type check), gate-check (test framework at Technical Setup, test evidence at Polish/Release), create-epics-stories (Type field + Test Evidence section) Updated agents: qa-lead (shift-left philosophy + evidence table), qa-tester (automated test patterns for Godot/Unity/Unreal) New templates: test-evidence.md (manual sign-off record), test-plan.md (sprint-oriented QA plan replacing generic feature template) Updated coding-standards.md: Testing Standards section with DoD table, test rules, what NOT to automate, and engine-specific CI/CD commands Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2.6 KiB
Test Evidence: [Story Title]
Story:
[path to story file]Story Type: [Visual/Feel | UI] Date: [date] Tester: [who performed the test] Build / Commit: [version or git hash]
What Was Tested
[One paragraph describing the feature or behaviour that was validated. Include the acceptance criteria numbers from the story that this evidence covers.]
Acceptance criteria covered: [AC-1, AC-2, AC-3]
Acceptance Criteria Results
| # | Criterion (from story) | Result | Notes |
|---|---|---|---|
| AC-1 | [exact criterion text] | PASS / FAIL | [any observations] |
| AC-2 | [exact criterion text] | PASS / FAIL | |
| AC-3 | [exact criterion text] | PASS / FAIL |
Screenshots / Video
List all captured evidence below. Store files in the same directory as this
document or in production/qa/evidence/[story-slug]/.
| # | Filename | What It Shows | Acceptance Criterion |
|---|---|---|---|
| 1 | [filename.png] |
[brief description of what is visible] | AC-1 |
| 2 | [filename.png] |
AC-2 |
If video: note the timestamp and what it demonstrates.
Test Conditions
- Game state at start: [e.g., "fresh save, player at level 1, no items"]
- Platform / hardware: [e.g., "Windows 11, GTX 1080, 1080p"]
- Framerate during test: [e.g., "stable 60fps" or "~45fps — within budget"]
- Any special setup required: [e.g., "dev menu used to trigger specific state"]
Observations
[Anything noteworthy that didn't cause a FAIL but should be recorded. Examples: minor visual jitter, frame dip under load, behaviour that technically passes but felt slightly off. These become candidates for polish work.]
- [Observation 1]
- [Observation 2]
If nothing notable: No significant observations.
Sign-Off
All three sign-offs are required before the story can be marked COMPLETE via
/story-done. Visual/Feel stories require the designer or art-lead sign-off.
UI stories require the UX lead or designer sign-off.
| Role | Name | Date | Signature |
|---|---|---|---|
| Developer (implemented) | [ ] Approved | ||
| Designer / Art Lead / UX Lead | [ ] Approved | ||
| QA Lead | [ ] Approved |
Any sign-off can be marked "Deferred — [reason]" if the person is unavailable. Deferred sign-offs must be resolved before the story advances past the sprint review.
Template: .claude/docs/templates/test-evidence.md
Used for: Visual/Feel and UI story type evidence records
Location: production/qa/evidence/[story-slug]-evidence.md