placing-tests

Place every test under tests/ named after the seam it covers, such as tests/home-page.test.tsx, never beside the source module. Co-located tests would inflate coverage, miss the vitest project globs, get the wrong ESLint rules, and become Next.js build input.

Selection follows what the test touches: .test.ts files with no I/O default to unit, .test.tsx files join component under jsdom by extension, and anything spawning subprocesses or using temp directories must be registered in the explicit automationTests list with a 120-second budget.

Unit and component tests have a 5-second budget because they perform no I/O, so a timeout indicates an infinite loop or unresolved promise. If the test legitimately needs filesystem or subprocess access, move it to the automation project's explicit list.

No. Coverage floors are never lowered and no file is added to coverage.exclude to move a number. When pnpm test:coverage fails on a floor, add real branch coverage for the uncovered code instead of adjusting the threshold or include list.

The v8 coverage provider only instruments Vitest worker processes, so code executing solely inside a spawned child process reports 0% regardless of test thoroughness. Keep the child-process code thin and move logic into modules the test can call in-process.

A test joins smoke only when it cannot run without pnpm build output, such as starting the built app with next start and asserting over fetch. Prefer automation whenever an in-process test could assert the same thing, since smoke is excluded from default runs.