CodeVetter · Repo Unpack · Testing signals
remix-run/react-router
Tests and CI were inspected, not executed; test existence is not a passing result. The inspected unit configuration uses Jest, with jsdom for the core React package and Node overrides for filesystem sessions. Playwright integration tests exercise application fixtures and browser behavior. This is a bounded inspection, so coverage outside the cited tests remains unassessed.
- The root test script invokes Jest with experimental VM modules, and Jest enumerates package projects.
- Shared Jest configuration maps workspace imports to source, transforms JS/TS, and matches *-test files.
- The core package uses jest-environment-jsdom, a package setup file, and jest-dom matchers.
- Navigation tests assert committed loaderData, valid null results, and JSON Response unwrapping.
- Fetcher action tests assert submitting → loading → idle and distinguish fetcher action data from revalidated page loaderData.
- Node session tests cover persistence across requests, cookie tampering, invalid IDs, and destroying an empty session.
- Middleware integration tests use PlaywrightFixture and assert client middleware effects before/after loaders and actions.
- Playwright runs tests in parallel, marks package modules external, forbids focused tests in CI, and retries three times in CI.
- Unit CI configures Node 22.22 and 24, then installs, builds, typechecks, lints, and invokes pnpm test; these configured steps were not executed in this investigation.
- Integration CI installs a selected Playwright browser and invokes pnpm test:integration with that browser; root scripts add a pre-build and post-run cleanup.