Agents open more pull requests than your team can read line by line. OtterWise checks that each change has tests before it merges, with patch coverage, status checks, and line annotations on every PR. We never need access to your source code.
No credit card required for public repos.
Why it matters now
Code review used to catch most problems. With agents writing code, there is now too much of it to review closely. Tests run on every change, however many there are.
Each developer ships more code with an agent, but review time stays the same. When nobody reads every line, tests have to catch what review misses.
One prompt can touch twenty files. Regressions land in the files nobody opened, and a failing test finds them even when the reviewer skims.
An agent runs the tests to see if its change broke something. Where there are no tests, it has nothing to check against.
Generated code is tidy and well named, so bugs are harder to see by eye. A test runs the code instead of trusting how it looks.
Agents extend the code that is already there. One untested module becomes the base for the next ten changes.
When an agent writes most of a module, nobody on the team knows it by heart. The tests are the record of what it should do.
The blind spot
Ask an agent to raise coverage and it will. It writes tests that run every line and check nothing useful. The percentage goes up, and the number means less. OtterWise also reports the metrics that are harder to fake.
Branch coverage shows which conditions only ever went one way, even when every line ran.
Measures only the lines a PR changed. Years of well-tested code cannot hide one new untested change.
Combines complexity with coverage to flag complex code that the tests barely touch.
Changed lines with no tests get marked in the PR diff, so reviewers know where to look first.
You still need to read the tests. These metrics tell you which ones to read first.
Patch coverage
When agents merge many PRs a day, project coverage hardly moves on any one of them. Patch coverage measures only the lines each pull request adds or changes, so a PR with no tests cannot hide behind a high project number.
Included on every plan, with project, line, and branch coverage.
Guardrails for agents
Set a minimum patch coverage and make the status check required in GitHub. Every agent then follows the same rule: it can merge only when its changes have tests. Line annotations list the exact lines without tests, so the agent knows what to fix next.
Trend tracking
One snapshot will not show a slow decline. OtterWise records project and patch coverage on every branch over time and sends a weekly digest. You can see if agent-written code arrives with tests or without them.
Patch coverage, status checks, and line annotations on every pull request, from people or agents. No access to your source code. Free for public repos.
