Changelog

We now show path coverage for reports from Pebble with --path-coverage. A path is one route through a method, so path coverage tells you whether each combination of branches ran. It is low by nature, often about 5%, so it is shown next to Code Coverage and Branch Coverage and does not change them or your status checks. Read the path coverage docs.

You can find path coverage in these places, when your reports include it: a Path Coverage tile on the repository, commit and pull request pages, a path coverage line in the coverage chart (click the tile), a Paths column in the file list, a Paths row in the pull request comment, and the paths taken on each method in the file viewer, for example Paths 1/2. The method badge now sits on the line that declares the method.

With --path-coverage, Pebble also writes how many outcomes of each decision ran. The file viewer marks the lines where only some outcomes ran as partly covered, so you can see where the missing paths are.

LCOV reports now give branch coverage too, per file and per line, from their BRDA records. Istanbul-based tools (Jest, Vitest, nyc, c8) write these by default. For LCOV, clover_coverage in the API and analytics was always 100%, because LCOV has no statements. It now counts each line as a statement, so it is the share of lines and branches covered, as for Clover.

The API now returns path coverage: path_coverage, paths_total and paths_covered on commits, path in the repository coverage overview, and methods (branch rate and paths per method) in the file coverage endpoints.

We now show branch coverage next to line coverage. Line coverage tells you whether a line ran. Branch coverage tells you whether every outcome of a decision ran, for example both sides of an if. There is nothing to turn on in OtterWise: if your Clover or Cobertura report has branch data, we read it on every upload. Line coverage stays the main Code Coverage number, and status checks still use it. Read the branch coverage docs to see which tools write branch data and how to enable it.

You can find branch coverage in these places, when your reports include it: a Branches column in the file list, a Branch Coverage tile on the repository, commit and pull request pages, a branch coverage line in the coverage chart (click the tile), a Branches row in the pull request comment, and a Branch Coverage option for the dashboard statistics. Where we can compare with a base, we also show the change.

The file viewer now marks lines that ran but did not take all of their branches as partly covered, in amber. Hover over the line number to see, for example, "1 of 2 branches covered". Partly covered lines have their own counter and jump buttons at the top of the file, and their own color in the minimap. For Cobertura reports with method data, each method also shows its branch coverage.

Per-line branch data needs a report that writes it: Cobertura from coverage.py, Istanbul (Jest, Vitest, nyc, c8), gcovr and Coverlet, or Clover from Istanbul. PHPUnit and Pest write branch data per file (Clover) or as rates per file and method (Cobertura), but not per line. Files without branch data show "—", not 0% or 100%.

The API now returns branch coverage too: branch_coverage, branches_total and branches_covered on commits, branch in the repository coverage overview, branch_coverage in analytics trends, and per-line branches in the file coverage endpoints.

The repository page has a new Avg Patch Coverage tile. It shows the covered changed lines out of all changed lines for the full period of the coverage chart. Click it to show patch coverage over time in the chart. Each point in the chart shows the covered changed lines out of all changed lines in the 14 days up to that commit, so one small commit cannot move the line much. Commits that change no lines are skipped. Use it to see whether new code arrives with tests, for example after your team starts to use AI coding agents. The metric tiles beside the chart are also more compact now.

The leaderboard has been redesigned, giving it new life; a clearer hierachy, new filtering (show top 3 or everyone), added statistics as well as tidied up the visuals. This is part of an ongoing effort to improve the user experience of the OtterWise dashboard. As with everything, feel free to reach out to us on the support chat, or email, with suggestions or issues.

Repository Analytics has a new Codebase Growth chart. It plots the tracked lines of code on your default branch over time, on the same date range and interval as the coverage chart on the repository page, so you can put a coverage trend next to the size of the codebase behind it. Only the lines your coverage reports include are counted, and each point tells you the file count and the commit it comes from.

The file viewer now marks which lines gained or lost coverage since the base commit, not only which lines have coverage now. Each gets a counter and jump buttons at the top of the file. This also covers the files under "Unchanged files with coverage changes", where a test change flips coverage without the file itself changing.

The coverage comment we post on your pull requests now has a Covered Lines row. It shows how many lines your tests cover, so the table adds up to: Lines = Covered Lines + Misses. This is the number the Coverage percentage is calculated from.

The Complexity vs Coverage quadrant in Repository Analytics no longer flags very small files as hard to test. A two-line model at 0% coverage is cheap to cover and tells you little, so it no longer pushes real candidates down the list. The "Hard-to-Test Files" table is now ranked by payoff — how much untested, risky code each file holds — and shows an "Uncovered" column so you can see the ranking.

The Churn-Weighted Coverage Risk report now scales scores down for files that are almost fully covered, and for files too small to hold much risk. A large, busy file tested to 99% is not a testing priority, and it no longer reads as high risk. Your top rows now point at the files where tests will actually remove risk.

The Contributors report now measures "Covered / Lines added" from the actual changes in each pull request (the diff) instead of subtracting whole-commit coverage totals. This makes the numbers reflect the lines a person really added or modified, and fixes wildly inflated figures for organizations using carry-forward flags/components (where a commit only uploads part of the coverage).

Added a new "Uncovered lines added" column to the Contributors report, showing how many of the lines each contributor added or modified are not covered by tests. It is measured from each pull request's diff, so it stays reliable even when carry-forward is enabled.

Our whole app has gotten a visual refresh, including support for Dark Mode. This is a purely visual update — no functionality has changed, everything works exactly as it did before.

Dark Mode automatically follows your system/browser preference, so there is nothing to toggle.

This is still being tested, so if you run into anything that looks off or have any feedback, please let us know. We appreciate any and all findings.

Added search to the branch selector on the repository page, making it much easier to find the right branch on repositories with many branches.

Added a quick search you can open anywhere in the app with ⌘K (Mac) or Ctrl+K (Windows/Linux). Start typing to instantly jump to any of your organizations, any repository across all your organizations, or common pages like Reporting, Billing, Settings and Team — only showing what you have access to.

Improved the reliability and speed of how we talk to GitHub behind the scenes. Sign-ins and data syncing are now smoother and less likely to be interrupted during busy periods.

Added a "Commits" tab to the pull request view, listing all commits added to the head branch since the PR was opened, sorted most recent first. Each row shows author, short SHA, message, tracked/covered lines, coverage and patch coverage.

Added a "Show coverage at this commit" button next to each commit in the new tab. Selecting it loads the file tree, coverage stats and file viewer for that commit instead of the PR head, making it easier to compare how coverage evolved across review iterations. A dismissible banner makes the active commit clear and a single click resets back to the PR head.

Added more information to the pull request view. This should hopefully make "View full report" more viable for usage during review time. Now includes tracked and covered lines, clearer coverage data, patch coverage, type coverage (when enabled), and deltas where relevant. You can now also see head and base branch as well as PR state (open, closed, ...).

Tightened spacing, cleaned up visuals for a better experience with large pull requests.

Added quick navigation arrows for uncovered lines of code, called "Sections". A section is when a group of lines are all not covered by tests, without any covered lines in-between them.

Added quick navigation arrows for changed lines when viewing files inside Pull Requests, to quickly hop between changed lines of code.