CodeVetter · Repo Unpack · Testing signals
jestjs/jest
Tests and CI definitions were inspected, not executed; no passing result or measured coverage is asserted. The repository tests itself with Jest, using package-level tests, subprocess-based e2e drivers, and separate type checks. Inspected tests exercise collection semantics, CJS dispatch, and snapshot retry persistence, with explicit runner-specific conditions. This is a bounded inventory of evidence, not exhaustive coverage.
- The main suite transforms JS/TS with babel-jest, includes root and example projects, and excludes fixture directories from direct discovery; root scripts expose focused Jest, coverage, Jasmine, VM-module, and type-test commands.
- Package unit tests live under __tests__, while e2e/__tests__ drivers execute fixture projects; e2e/runJest.ts launches the repository CLI with process.execPath and asserts captured subprocess results.
- CjsLoader unit tests stub resolution, registries, and execution, checking core-module routing, cached exports without re-execution, manual mock selection, and recursion avoidance; these tests alone do not establish real VM integration.
- Collection e2e tests assert tree/JSON output, wouldRun flags, load-error reporting, no test-body execution, and parity with focused execution; test.failing parity cases explicitly skip Jasmine.
- SnapshotState tests use temporary files to check retry rollback, preservation of other tests' inline/file writes, and no write after complete rollback; another test records the hint-separator ownership ambiguity.
- Retry e2e tests inspect beforeAll describe recovery, snapshot restoration, and concurrent describe retries, but the entire inspected retry suite calls skipSuiteOnJasmine.
- Node CI invokes sharded Ubuntu, macOS, and Windows jobs across Node 18/20/22/24/25/26; test jobs build JavaScript and use retries with three attempts and ten-minute timeouts, while separate jobs cover declarations, lint, VM modules, Watchman, and coverage.
- Coverage collection excludes bin, cli, e2e, tests, builds, and vendor paths; TypeScript integration uses a separate configuration, and CI reporting emits JSON coverage plus GitHub Actions, JUnit, silent, and summary reports. These inspected definitions do not prove execution or comprehensive behavioral coverage.