Observed arrival · 2026-11-05
Reapr puts mutation tests on the pull-request diff
Reapr runs a project's StrykerJS or cargo-mutants configuration against changed lines and reports mutations that its tests fail to catch.
- For
- Teams reviewing AI- or human-written code in pull requests
- Worth noticing
- The benchmark attributes its 3× faster run to excluding a local Turborepo cache, not to Reapr.
Field notes
The workflow starts with Git's base-to-branch diff, passes the changed ranges to the configured mutation-testing engine, and filters the resulting mutants to those ranges. The page says existing test-runner settings, thresholds, timeouts, checkers, and plugins stay intact. Its reference measurement reports medians of five runs and explicitly attributes the 3× change to excluding a local Turborepo cache; it also notes that the comparison includes incremental results outside the diff.
Observed signals
Read the marks
Editorial observations of this landing page, not a rating.
One card from the complete issue