replica-test

1# replica-test
2 
3Reads the flows in `replica/recon.md`. Writes `replica/test-plan.md`,
4`replica/bugs.md`, and end-to-end tests in the project (`e2e/`). Templates in
5this folder: `test-plan.md`, `bug-report.md`, `e2e.example.spec.ts`.
6 
7## The rule
8 
9**Test your clone, not the original.** Never load test, fuzz, script or
10hammer the original app's servers. Using the original by hand, as a normal
11user, to see how it behaves is fine.
12 
13## Step 1: the plan
14 
15For every flow F01, F02... in the recon map, write:
16 
17- **Happy path**: the steps, and what the user should see at the end.
18- **Edge cases** that apply. Go down this list for every flow:
19  empty input, very long input, emoji and accents, two tabs at once,
20  double click on submit, back button mid-flow, refresh mid-flow, slow
21  network, offline, expired session, second user's data (must be invisible),
22  time zones and daylight saving, mobile width, keyboard only, screen reader
23  labels.
24- **Negative cases**: wrong password, card declined (Stripe test card
25  `4000 0000 0000 0002`), permission denied, deleted record.
26 
27Number every case: F01-H1, F01-E3, F01-N2.
28 
29## Step 2: automate what you can
30 
31Playwright, one spec per flow, against the local dev server with seed data.
32Use roles and labels for selectors (`getByRole('button', { name: 'Book' })`),
33never CSS classes. See `e2e.example.spec.ts`.
34 
35```bash
36npm i -D @playwright/test && npx playwright install chromium
37npx playwright test
38```
39…