testing-strategylisted

Use when deciding what to test, at which layer, and what runs when. The E2E charter, three layers with time budgets, the when-to-run matrix, test infrastructure tiers, mechanics and conventions, the per-test quality bar for merging, what only a human can test, auditing an existing suite, and how test configs rot. A test suite is a budget, not a trophy.
konradcinkusz/architecture-standards · ★ 0 · Testing & QA · score 70

Install: claude install-skill konradcinkusz/architecture-standards

# Testing strategy **Read [`references/TESTING-STRATEGY.md`](references/TESTING-STRATEGY.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 charter - Three layers with budgets - What runs when - Test infrastructure tiers - Mechanics and conventions - The per-test quality bar - Manual testing - Auditing an existing suite - Test configs rot ## Checklist - [ ] E2E charter written: protected flows named, non-goals named - [ ] Three layers with time budgets and triggers; smoke suite enumerated - [ ] When-to-run matrix explicit; tags mapped to runner projects mechanically - [ ] Infrastructure tier chosen per layer; PR answer = preview environments, not full infra - [ ] Test projects mirror source; constructor isolation; mock modes used as seams - [ ] Per-test bar enforced: one goal, independent, `data-testid`, no sleeps, zero flakiness tolerance - [ ] Manual scope limited to the four named situations, run with account matrix, notation, and bug rubric - [ ] Suite audited on a cadence with the four questions - [ ] Every committed test config is executed by some CI context --- Generated from [`docs/guides/TESTING-STRATEGY.md`](https://github.com/konradcinkusz/architecture-standards/blob/main/docs/guides/TESTING-STRATEGY.md) by `scripts/build-marketplace.mjs`. Do not edit this file