Carries 359 template commits, tag v0.2.0 plus one documentation commit: the generator-built feature index with its app, bounded-context and feature declarations, the src/platform kernel and scale tooling, the 2026-09-24 src review fixes, and the 2026-09-25 maturity review round with its CHANGELOG [보안]/[계약] rows. 691 of the 824 template paths are applied, 85 of them merged with product changes; 127 are not carried. Product identity is unchanged: name, version 0.1.0, routes, design and the TechLog domain. Three decisions worth naming. TechLog stays composed directly, as the last two syncs recorded; its directory carries a NOT_INSTALLED marker that says so, and every installed-* composer takes the template's projection with TechLog added on top. The reference sample is no longer installed: the template now installs a feature only through feature-module.ts and context-routes.ts, which load the screens this product deleted, so its three operations, six schemas and one topic leave the registries, recorded as registry change evidence. And AppRouter mounts the platform and TechLog routes only; the template's bounded-context route gateway waits for a generator-installed feature. Required fixes: readSubject on the BFF session owner (without it every HTTP Studio session would close as integration-failed), zod through the facade in nine TechLog files, noUnusedLocals, and public/config.json written out to match the local profile. Derived baselines were recomputed after reproducing both sides' values: CI contract 101 commands / 106 references / 141 artifacts, gate shape c9adcf85; registry approval 2dc6c3a3; the runtime config schema baseline equals the schema at8210d48. Verified here: types, lint, architecture, adapter inventory, CI contract, i18n, design system, diagnostics, browser security, dev release manifest, TechLog contract and build pass; 220 component, 155 integration, 15 contract, 418 TechLog, 43 reference-feature, 18 recipe and 46 release-coherence tests pass, and 2381 of 2383 unit tests. Reproduced at8210d48first and unchanged: check:registries (byte-identical), test:runtime-schema, verify:documentation. Brought by the template and escalated rather than suppressed: check:request-fanout on TechLog's cursor pagination, check:remediation-ledger (fails upstream too), the shared-chunk hash test, and the registry-dependent sample removal and second-feature tests. Playwright suites were not run. Full record, the five open questions and the follow-ups in docs/operations/template-sync-2026-09-29.md. (cherry picked from commit b2170cf265dea45dc9cc05d3c61e627e97f31cdb)
5.5 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, test:reference-feature, test:platform (tests/platform
and tests/architecture), check:release-coherence and test:recipes
(package.json test:all). 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.