1.8 KiB
Test and evidence taxonomy
Each gate is blocking in its declared scope. Failures are not downgraded with
continue-on-error or warning-only scripts.
| Level | Command | Evidence |
|---|---|---|
| runtime schema | pnpm test:runtime-schema |
artifacts/tests/runtime-schema.xml |
| unit | pnpm test:unit |
artifacts/tests/unit.xml |
| component | pnpm test:component |
artifacts/tests/component.xml |
| integration | pnpm test:integration |
artifacts/tests/integration.xml |
| end-to-end | pnpm test:e2e |
artifacts/tests/e2e/ |
| accessibility | pnpm test:a11y |
artifacts/tests/a11y.json |
End-to-end and automated accessibility scenarios run on the pinned Chromium, Firefox, and WebKit engines. The responsive contract explicitly exercises 320px reflow, a mobile navigation drawer, and a wide two-column gallery. Theme scenarios verify persistence, operating-system changes, and dark-surface axe results. Native modal focus and validation association are exercised in both component and browser tests.
A control is verified only when a positive fixture passes and its deliberately failing negative fixture is rejected. Generated evidence is retained by CI; the repository tracks only the evidence directory structure.
Promotion is an AND graph:
- merge gates
- merge gates plus release gates
- release gates plus rollback/runbook drills
- production promotion plus eligible field Web Vitals evidence
This file describes the currently registered taxonomy. The frontend platform testing strategy documents the target additions: test TypeScript projects, real bootstrap composition tests, shared MSW scenarios, query/mutation/form/router coverage, Storybook interaction and accessibility checks, visual regression, and a built-output Playwright profile.