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.
We regularly update our changelog in an effort to improve transparency into the development process. If you have any questions or feedback, please don't hesitate to contact us.
If you are a user of OtterWise already, or have been reading our blog, you might already know that we take privacy extremely serious, even when it comes to protecting your code as if it was sensitive personal information, this goes for everything we do, which is why we publish changelogs for even smaller updates, rather than just major releases.
Our weekly digest for OtterWise users also includes our changelog in the bottom (see related changelog), to keep you up-to-date with the latest changes.
PR comments, status checks, line annotations, and trends, all without code access. Free for public repos; per-repo pricing for private repos.
