Blog series: "Testing the Way Users Actually Experience the Web"
Start with the introduction.
Tutorial-format posts on @afixt/usecase-runner, each demonstrating one of the
project's design philosophies through a runnable example.
| # | Post | Philosophy demonstrated |
|---|---|---|
| 1 | Why Your Test Selectors Are Lying to You | Accessibility-tree-only targeting; a failure is a finding |
| 2 | A Test Your QA Team Can Actually Read | The test plan and the test are the same artifact |
| 3 | locate, focus, activate |
Each verb encodes a question a real user must answer |
| 4 | Verify Like a Screen Reader, Not Like a Screenshot | Assert what AT perceives, not what's painted |
| 5 | Strictness Is a Feature | Reject unconsumed input; never resolve ARIA defaults silently |
| 6 | select Is Not toggle |
Verbs are contracts about outcomes |
| 7 | Testing Without a Mouse | Interaction profiles; report what actually ran |
| 8 | One Flow, Many Outcomes | Negative paths are where accessibility breaks |
| 9 | Generate for CI, Run for Right Now | Mode equivalence; maximum diagnostic information |
| 10 | Beyond the Step | Flow testing and rule scanning answer different questions |
Posts 1–2 are the on-ramp, 3–7 the philosophical core, 8–10 for existing users.
Each ends with a complete .uc.yaml the reader can run.