문제 taxonomy는 test:all을 일상 개발 루프라고 적는다. 그런데 test:all은 tests/features 중 참조 샘플만(test:reference-feature) 돌리고, test:coverage(FE-GATE-005)가 도는 tests/features의 나머지(설치 표면, feature-module, 예제 기능 2파일), tests/scripts, tests/scale/browser-soak.contract.test.ts를 빠뜨린다. 로컬에서 초록이고 CI에서 빨강이 될 수 있다. 고른 방법과 버린 대안 - package.json test:all의 test:reference-feature 자리를 tests/features 전체 + tests/scripts + browser-soak 계약 테스트를 한 번에 도는 Vitest 실행으로 바꾼다. 참조 샘플 테스트도 tests/features 안이라 그대로 돈다. 샘플을 지우면 그 폴더만 빠진다. - tests/unit/test-all-paths.test.ts(새 파일): package script graph로 test:all과 test:coverage의 Vitest 경로를 모아, coverage 쪽 경로가 모두 test:all 경로 안에 있는지 본다. 다시 빠지면 이 테스트가 잡는다. - 새 package script(test:features)를 만드는 안은 버렸다. 그 이름이 tests/scripts까지 도는 것을 말하지 못하고, test:all만 쓰는 스크립트가 하나 늘 뿐이다. - taxonomy에 "CI와 같은 집합은 test:coverage"라고만 적는 안은 버렸다. 완료 기준(test:all ⊇ test:coverage의 Vitest 파일)을 못 채운다. - docs/testing/taxonomy.md의 test:all 설명을 바꾼다. 위험·한계 - 제거 드릴 셋(optional recipe, realtime, browser-file-storage)은 fixture 안에서 test:all만 돈다. 이제 이 파일들도 그 fixture에서 처음 돈다. import를 보면 제거 대상에 기대지 않지만 실행으로는 확인하지 못했다. 드릴 시간이 몇 초씩 는다(1101/10-06과 반대 방향). 검증 - desktop batch에서 확인: node scripts/run-vitest.ts run tests/unit/test-all-paths.test.ts corepack pnpm test:all, corepack pnpm check:ci, FE-GATE-020 - RED: 부모 커밋의 package.json에서 "runs every Vitest path test:coverage runs"가 tests/features·tests/scripts·browser-soak 경로를 빠졌다고 실패한다. Refs: 0929/10-05
5.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.
Executable levels
| Level | Command | Ownership / prerequisite | Evidence |
|---|---|---|---|
| runtime schema | pnpm test:runtime-schema |
pure runtime schema contracts | artifacts/tests/runtime-schema.xml |
| unit | pnpm test:unit |
Node-only domain/application/pure policy/runtime units; no systemd/bwrap/cgroup prerequisite | artifacts/tests/unit.xml |
| capability contract | pnpm test:contract |
reusable capability consumer contracts | artifacts/tests/contract.xml |
| component | pnpm test:component |
React/hook/UI behavior | artifacts/tests/component.xml |
| integration | pnpm test:integration |
HTTP/MSW, IndexedDB, composed browser-runtime boundaries, child-process/filesystem/IPC integration | artifacts/tests/integration.xml |
| system / CI runner | pnpm test:system |
compatible Linux host with systemd, bubblewrap, cgroup v2 and CI-provider process controls | artifacts/tests/system.xml |
| end-to-end | pnpm test:e2e |
pinned browser engines | artifacts/tests/e2e/ |
| accessibility | pnpm test:a11y |
pinned browser engines | artifacts/tests/a11y.json |
test:all is the normal product-development loop. It runs, in order,
test:runtime-schema, test:unit, test:contract, test:component,
test:integration, the rest of what test:coverage runs (tests/features,
the reference sample's tests among them, tests/scripts and
tests/scale/browser-soak.contract.test.ts), test:platform (tests/platform
and tests/architecture), check:release-coherence and test:recipes
(package.json test:all). So every Vitest path the merge gate's coverage
run covers also runs here (tests/unit/test-all-paths.test.ts, 0929/10-05).
It does not include test:system. CI-runner and
supply-chain assurance has different host prerequisites and is invoked
explicitly in the assurance path.
Deterministic test process
All Vitest package scripts launch through scripts/run-vitest.ts.
That runner:
- rejects Node versions outside the repository-supported
>=24.11.0 <25.0.0range before the suite starts, - owns
NODE_ENV=testrather than trusting the parent shell, - removes host-specific
npm_config_userconfig,npm_config_prefixandnpm_config_globalconfigvalues before Vitest starts.
vitest.config.ts also fixes NODE_ENV=test so a direct Vitest invocation
cannot accidentally select React's production behavior.
To run one test file, use the same runner:
node scripts/run-vitest.ts run tests/component/router.test.tsx
The runner renders the gitignored src/.generated/ product index first
(scripts/run-vitest.ts), so this works in a fresh clone. A direct
pnpm exec vitest run <file> skips that step and fails there with
Failed to resolve import "../.generated/product-feature-index.ts".
pnpm test:unit -- <file> does not narrow the run, because the script already
passes the whole tests/unit directory.
vitest.config.ts collects only tests/**/*.test.{ts,tsx}; Playwright
*.spec.ts files are not Vitest tests. tests/system/ is collected only when
the command names it, as test:system does, so a bare vitest run does not
start the CI-runner suite.
The system suite additionally runs
scripts/check-system-test-prerequisites.ts and fails with one prerequisite
report when the CI-runner host does not provide its required Linux facilities.
Development paths
Product feature:
- focused feature/unit/component test
- capability contract test when a reusable boundary changes
- type/lint/architecture
test:all
Reusable capability:
- focused unit tests
- capability contract tests
- integration tests
- type/lint/architecture
CI / release assurance:
test:system- supply-chain / promotion / release gates
A host-level process/sandbox test must not be placed in tests/unit merely
because it uses Vitest. The classification follows the system boundary and
prerequisites, not the test framework:
- Tests that need systemd, bubblewrap, cgroup v2 or CI-provider process
controls belong in
tests/system. - Tests of a long-lived child-process protocol belong in
tests/integration; for example the provider guardian transaction protocol lives attests/integration/provider-guardian-transaction.test.ts. Its handshake timeout is a test watchdog, not a production protocol deadline. - A script's own tests may start that script, Node or Vitest as a short-lived
child process to check its command-line contract, and stay in
tests/unitnext to the script's other tests. Such a suite declares its own longer timeout instead of raising the global one; for exampletests/unit/risk-coverage.test.tsusesPROCESS_HEAVY_TIMEOUT_MS.
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
The frontend platform testing strategy contains the broader testing design. This file is the executable taxonomy for where a test belongs and which environment is allowed to run it.