test: jsdom + Testing Library component smoke tests

[abk1969]

Summary

Closes the highest-impact gap from the TDD audit retrospective: the project had zero component-level tests. The C2 `roleNotes` scope error in PR #3 (caught only by spec review) is the canonical example — green unit tests + green build, yet a runtime `ReferenceError` when reaching the verdict screen.

Stacks on PR #6.

What's set up

New devDeps: `@testing-library/react`, `@testing-library/jest-dom`, `@testing-library/user-event`, `jsdom`.

vitest.config.js: per-file environment via `environmentMatchGlobs`. Only `*.dom.test.jsx` files spin up jsdom — the existing 109 node-env tests stay fast. Adds `@vitejs/plugin-react` for JSX transform.

src/test-setup.js: jest-dom matchers (`toBeInTheDocument`, `toBeEnabled`, …) + a stub for `window.scrollTo` (jsdom doesn't implement it; the App calls it on step change → otherwise produces noisy stderr).

Tests added (`src/app.dom.test.jsx`)

4 component smoke tests:

1. App mounts welcome screen without throwing — the minimum runtime safety net. If the React tree ever fails to construct (missing import, syntax error in JSX, scope mistake at component boundary), this test fails.
2. Welcome → Step 1 navigation — verifies the Start button is clickable and Step 1 renders.
3. Continue button enables after role selection — exercises state-driven UI gating.
4. deployerKind sub-question conditional visibility — directly tests the pattern that broke in C2: a state field (`answers.role === 'deployeur'`) gating a downstream UI element. If the gating logic regressed, this would fail.

Tests

• 113 passing (109 → 113)
• Build green, no bundle change (test infra only)
• Suite runtime: ~5 s (node tests ~1.5 s, jsdom tests ~3.5 s)
• jsdom stderr suppressed via `window.scrollTo` stub

What's deferred

Deep Result-screen walk-throughs (advancing all 7 steps to verify the verdict renders) are NOT in this PR. Getting there in jsdom with the current UI requires selector engineering that's high-effort for limited additional safety. The correct path forward is Playwright E2E (Playwright is already a devDep, used by `make-demo.cjs` to record the demo video).

A natural follow-up would be a single `tests/e2e/result.spec.js` that walks each verdict path end-to-end with screenshot assertions.

Test plan

• `npx vitest run` shows 113/113 passing
• `npm run build` succeeds, no bundle regression
• Manually break the App (e.g., delete an import) and confirm test feat(test): Vitest + extract computeCategory to src/lib/ #1 fails with a clear error
• Manually break the deployerKind gating (e.g., change `answers.role === 'deployeur'` to `'deployer'`) and confirm test Refine art. 27(1)(b) FRIA gating to Annex III §5(b)/§5(c) #4 fails

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
ai_act_compass	Ready	Preview, Comment	May 15, 2026 2:40pm

[abk1969]

Merged into main via rebase fast-forward (commits applied via stack rebase, see main's history). Branch deleted.