Guides
Testing plan
The Testing Plan page shows E2E test scenarios generated from the knowledge base, organized by feature and priority.
How scenarios are generated
During guide composition, the composer analyzes every flow, edge case, state transition, and vendor dependency in the feature's chapters and generates test scenarios. Each scenario includes:
- Name — what the test verifies ("Apply for a charge card as a new member")
- Priority — critical (money/auth flows), high (core journeys), normal (secondary), low (edge cases)
- Category — happy_path, error_path, edge_case, regression, security, performance
- Persona — who executes the test (member, admin, system/cron)
- Preconditions — what must be true before starting
- Steps — numbered actions and expected results
- Postconditions — what to verify after all steps
- Automated — whether an existing test file covers this scenario
Priority levels
| Priority | When to use | Examples |
|---|---|---|
| Critical | Revenue or data at risk if broken | Payment processing, fund transfers, account creation |
| High | Core user flow | Login, main feature happy path, search |
| Normal | Secondary flow | Settings changes, notification preferences |
| Low | Edge case or rare path | Empty states, timezone edge cases |
Test gaps
The plan also identifies testing gaps — flows described in the knowledge base that have no automated test coverage. Each gap explains what's untested and why it matters.
Using the plan
The testing plan is a living document updated on each scan. Use it to:
- Prioritize QA effort — work through critical scenarios first
- Identify automation opportunities — manual scenarios that should become automated tests
- Onboard QA team members — the preconditions and steps are detailed enough to execute
- Audit coverage — compare automated vs manual counts to track progress