Developer
Repro Replay
Repro replay fixtures validate deterministic headless record/replay behavior.
Repro replay fixtures validate deterministic headless record/replay behavior.
Fixture Source
- replay fixtures:
packages/testkit/fixtures/repro/*.json - primary replay harness test:
packages/core/src/repro/__tests__/replay.harness.test.ts
The fixture currently exercised by the harness is:
packages/testkit/fixtures/repro/replay_resize_tab_text.json
CI Gate
Every PR runs an explicit replay gate in .github/workflows/ci.yml:
- job:
node / ubuntu-latest - step:
Repro replay fixtures (headless, explicit gate) - command:
node --test --test-concurrency=1 packages/core/dist/repro/__tests__/replay.harness.test.jsnpm run test also covers this area, but this dedicated step keeps replay coverage visible as a standalone gate.
Local Run
npm ci
npm run build
node --test --test-concurrency=1 packages/core/dist/repro/__tests__/replay.harness.test.jsOptional schema/version checks:
node --test --test-concurrency=1 packages/core/dist/repro/__tests__/schema.versioning.test.jsUpdating Replay Fixtures
Follow the golden fixture policy in packages/testkit/fixtures/README.md:
- Update fixture JSON intentionally (no auto-regeneration in committed tests).
- Re-run replay harness and related tests.
- Include fixture diff context and reasoning in the PR.