CodeVetter · Repo Unpack · Testing signals
facebook/react
Jest 30 is the runtime test framework, with 544 test files under `packages/**/__tests__`, and it is deliberately unusable directly — `package.json`'s `testRegex` points at `dont-run-jest-directly.js`, forcing everything through `scripts/jest/jest-cli.js`. That CLI selects one of six configs (source, source-www, source-xplat, source-persistent, build, build-devtools) and injects `__DEV__`, `__EXPERIMENTAL__` and `__VARIANT__` globals; individual tests opt in/out of behaviour with `// @gate <flag>` pragmas resolved by `scripts/jest/TestFlags.js`. The compiler uses a different harness entirely: `yarn snap` over ~1,543 fixture files with `.expect.md` snapshots, plus Playwright e2e for the playground and the flight fixture. CI runs the runtime suite as an 18-config × 5-shard matrix; the Rust port has its own workflow gating on `cargo check`, `cargo build`, two shell test scripts and `yarn snap --rust`.
- Jest is pinned at `^30.4.1` (`jest`, `jest-cli`, `jest-environment-jsdom`, `babel-jest`) with `jest-silent-reporter` and `jest-snapshot-serializer-raw` for output control.
- There are 544 test files under `packages/**/__tests__/**/*.js`, spread across the runtime, DevTools shared, scheduler and shared packages.
- `scripts/jest/jest-cli.js` is the only supported entry: it exposes `--project {default,devtools}`, `--releaseChannel {experimental,stable,www-classic,www-modern,xplat}`, `--env`, `--prod`/`--dev`, `--variant`, `--build`, `--persistent`, `--ci`, `--reactVersion` and `--sourceMaps`, then spawns Jest with the matching config file.
- Six Jest configs cover the test surfaces: `config.source.js`, `config.source-www.js`, `config.source-xplat.js`, `config.source-persistent.js`, `config.build.js` and `config.build-devtools.js` — so the same specs are exercised against source and against built bundles.
- `@gate` pragmas let a test declare its preconditions; `scripts/jest/TestFlags.js` resolves them against `shared/ReactFeatureFlags` plus environment flags `__DEV__`, `build`, `experimental`, `stable`, `variant`, `persistent`, and the deliberate escape hatches `FIXME: false` / `TODO: false` for known-broken tests.
- `scripts/jest/setupHostConfigs.js` rewires module resolution so each test file resolves `react-reconciler/src/ReactFiberConfig` to the right renderer's host config, iterating over `inlinedHostConfigs` — without it every reconciler test would hit the throwing shim.
- `packages/internal-test-utils` supplies the shared test vocabulary — `internalAct.js`, `ReactInternalTestUtils.js`, `consoleMock.js`, `shouldIgnoreConsoleError.js`/`shouldIgnoreConsoleWarn.js`, and `simulateBrowserEventDispatch.js` — and is itself tested.
- The runtime CI matrix in `runtime_build_and_test.yml` runs 18 parameter sets (stable/experimental/www-classic/www-modern/xplat × development/production × variant true/false, plus two persistent configs) crossed with 5 shards, i.e. 90 parallel `yarn test` jobs.
- CI also gates on non-test checks as separate jobs: `flow` (sharded by discovered inline configs), `check_generated_fizz_runtime`, `flags`, and `test-linter` for `eslint-plugin-react-hooks`.
- There is a dedicated fuzz workflow (`runtime_fuzz_tests.yml`) separate from the main suite, so fuzzing is not part of the per-PR signal.
- The compiler's test corpus is fixture-driven: ~1,543 `.js` fixtures under `babel-plugin-react-compiler/src/__tests__/fixtures`, each paired with a `.expect.md`, run via `yarn snap` (`-p <pattern>`, `-d` debug, `-u` update) as documented in `compiler/CLAUDE.md`.
- Fixture naming encodes expected failure modes: `error.todo-*.js` means an unsupported feature that correctly bails with a Todo error, `error.bug-*.js` means a known bug producing the wrong error — so some fixtures are assertions about known gaps, not passing behaviour.
- The Rust port has its own CI gate: `compiler_rust.yml` runs `cargo check`, `cargo build`, `bash scripts/test-babel-ast.sh`, `bash scripts/test-rust-port.sh`, then builds `snap` and runs `yarn snap --rust` — i.e. the Rust implementation is validated against the same fixture snapshots as the TS one.
- Only 14 TypeScript unit-test files exist across the whole `compiler/` tree, versus 1,543 fixtures — the compiler's coverage is almost entirely end-to-end snapshot, with very little unit-level testing of individual passes. (inferred)
- Browser-level e2e exists in exactly two places: `compiler/apps/playground/__tests__/e2e/page.spec.ts` (Playwright, `--workers=4`) and `fixtures/flight/__tests__/__e2e__/smoke.test.js`; the 25 other directories under `fixtures/` are manual-testing apps with no automated assertions.