← ClaudeAtlas

e2e-acceptance-testinglisted

Use when writing, reviewing or auditing an end-to-end acceptance suite, especially one that was bulk-generated. The one rule that a test may not pass without checking anything, locator conventions chosen before the first component ships, web-first assertions only for waiting, independence and cleanup agreeing with parallelization, CI wiring as part of done, one canonical suite per live frontend, and the tells that an inherited suite was never fact-checked. A suite that reports green while testing nothing is worse than no suite, because it is trusted.
konradcinkusz/architecture-standards · ★ 0 · Testing & QA · score 72
Install: claude install-skill konradcinkusz/architecture-standards
# Building an E2E acceptance suite worth trusting **Read [`references/E2E-ACCEPTANCE-TESTING.md`](references/E2E-ACCEPTANCE-TESTING.md) before applying any of this.** That file is the standard; everything below it is a summary to help you decide whether this skill applies and to check your work afterwards. Reference-architecture principles: P13. ## What this standard covers - The audit that motivated this guide - The one rule: a test may not pass without checking anything - Locators: pick a convention before the first component ships - Waiting: web-first assertions only, and verify your framework agrees - Independence, cleanup, and parallelization have to agree with each other - CI wiring is part of "done," not a follow-up - One canonical suite per live frontend - Auditing a suite you inherited, especially an AI-bulk-generated one ## Checklist A suite claiming to be a real regression net answers yes to all of these: - [ ] Every passing `[Fact]`/`[Test]` executes at least one unconditional assertion against real application state — no guard-then-bail before the only assertion, no swallowed assertion failures - [ ] Anything not yet implemented is `[Fact(Skip="reason")]` (or the framework equivalent), never a silently-passing placeholder - [ ] Locators prefer role/accessible-name first, `data-testid` as the deliberate fallback where no accessible name exists; the convention was agreed before the first component shipped, not retrofitted - [ ]