# QA flow: <feature name>

> Fill what you know. Write **unknown** where you do not; the agent asks
> before running instead of guessing. Developers can use the same file to
> hand a feature to the agent with its acceptance criteria.

## 1. What and why

- Feature:
- Why it exists (the user problem):
- Changed in this release:

## 2. Environment

- Where to run (URL, build, device):
- Data to start from (accounts, seed, fixtures):
- Test payment / messaging mode (sandbox, fake, local webhook):
- Never touch: (production, real customers, real money)

## 3. Actors

| Actor | Account or how to get one | What they may do | What they must never do |
|---|---|---|---|
| | | | |

## 4. Happy path

| # | Actor | Step | Expected result |
|---|---|---|---|
| 1 | | | |
| 2 | | | |

## 5. Rules and limits

- Amounts, caps, rounding:
- Time windows, time zones, deadlines:
- States and what each state shows or hides:
- Permissions:

## 6. Out of scope

-

## 7. Known risks and past bugs

-

---

## Cases (the agent fills this)

| # | Type | Actor | Case | Expected | Actual | Evidence | Status |
|---|---|---|---|---|---|---|---|
| S1 | scripted | | | | | | pass / fail / blocked |
| U1 | unexpected | | | | | | |

## Bugs filed

| # | Title | Severity | Report |
|---|---|---|---|

## Not tested, and why

-