bd495be965
All checks were successful
Deploy to Production / Build and Deploy (push) Successful in 12s
- Sidebar: dynamic brand-accent colors, brainstorm section restyled - AI chat general: popup panel with expand/collapse, hides when contextual AI open - AI chat contextual: tabs reordered (Actions first), X close button, height fix - Settings: all tabs restyled, 6 new color presets (sage, terracotta, iron, etc.) - Global color cleanup: emerald/orange hardcoded → brand-accent dynamic - Brainstorm page: orange → brand-accent throughout - PageEntry animation component added to key pages - Floating AI button: bg-brand-accent instead of hardcoded black - i18n: all 15 locales updated with new AI/billing keys - Billing: freemium quota tracking, BYOK, stripe subscription scaffolding - Admin: integrated into new design - AGENTS.md + CLAUDE.md project rules added
73 lines
1.8 KiB
Markdown
73 lines
1.8 KiB
Markdown
---
|
|
name: acceptance-testing
|
|
description: Design and run acceptance tests from specification criteria
|
|
---
|
|
|
|
# [T] Acceptance Testing — Design & Run Tests from Spec Criteria
|
|
|
|
**Goal:** Validate that implementation matches design specifications through structured testing.
|
|
|
|
**When to use:** Implementation is complete (prototype or production), ready for validation against specs.
|
|
|
|
---
|
|
|
|
## INITIALIZATION
|
|
|
|
### Design Log
|
|
Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
|
|
|
|
---
|
|
|
|
## STEPS
|
|
|
|
Execute steps in `./steps-t/`:
|
|
|
|
| Step | File | Purpose |
|
|
|------|------|---------|
|
|
| 01 | step-01-prepare.md | Gather materials, set up environment |
|
|
| 02 | step-02-execute.md | Run all test categories |
|
|
| 03 | step-03-document-issues.md | Create issue tickets |
|
|
| 04 | step-04-report.md | Compile test report |
|
|
| 05 | step-05-iterate.md | Iterate fixes or approve |
|
|
|
|
**Reference data:**
|
|
- `./data/testing-guide.md`
|
|
- `./data/test-result-templates.md`
|
|
- `./data/issue-templates.md`
|
|
|
|
---
|
|
|
|
## DESIGN LOG REPORTING POINT
|
|
|
|
When all tests pass and the user approves, append to the Design Loop Status table in `{output_folder}/_progress/00-design-log.md`:
|
|
|
|
```
|
|
| [Scenario slug] | [NN.X] | [Page name] | approved | [YYYY-MM-DD] |
|
|
```
|
|
|
|
Do NOT skip this. The design log drives Phase 4's adaptive dashboard.
|
|
|
|
## AFTER COMPLETION
|
|
|
|
**If all tests pass:**
|
|
|
|
Design log updated with `approved` status (see above). Present the transition:
|
|
|
|
<output>
|
|
**"[page name]" is approved!**
|
|
|
|
1. **Explore the next scenario step** — [next page name]
|
|
2. **Design delivery** — package for development handoff (Phase 4 [H])
|
|
</output>
|
|
|
|
**If issues found:**
|
|
|
|
Status stays `built`. Present:
|
|
|
|
<output>
|
|
**"[page name]" has [N] issues to fix.**
|
|
|
|
1. **Fix the issues** — route to bugfixing
|
|
2. **Explore the next scenario step** — fix later, continue designing
|
|
</output>
|