refactor: 프론트 템플릿 리펙토링

2026-09-18 15:16:58 +09:00
parent c10a709f2c
commit 5cc41467ae
80 changed files with 7227 additions and 4672 deletions
@@ -3,14 +3,68 @@
 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` |
+## 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 and composed browser-runtime boundaries | `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 intentionally includes
+runtime-schema, unit, capability-contract, component, integration, reference
+feature and recipe suites, but 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:
+
+1. rejects Node versions outside the repository-supported
+   `>=24.11.0 <25.0.0` range before the suite starts,
+2. owns `NODE_ENV=test` rather than trusting the parent shell,
+3. removes host-specific `npm_config_userconfig`, `npm_config_prefix` and
+   `npm_config_globalconfig` values before Vitest starts.
+
+`vitest.config.ts` also fixes `NODE_ENV=test` so a direct Vitest invocation
+cannot accidentally select React's production behavior.
+
+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.

 End-to-end and automated accessibility scenarios run on the pinned Chromium,
 Firefox, and WebKit engines. The responsive contract explicitly exercises
@@ -30,9 +84,6 @@ Promotion is an AND graph:
 3. release gates plus rollback/runbook drills
 4. production promotion plus eligible field Web Vitals evidence

-This file describes the currently registered taxonomy. The
-[frontend platform testing strategy](./frontend-platform-testing-strategy.md)
-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.
+The [frontend platform testing strategy](./frontend-platform-testing-strategy.md)
+contains the broader testing design. This file is the executable taxonomy for
+where a test belongs and which environment is allowed to run it.