Platform Update: Introducing Our New Coverage Page 

In this article:
Subscribe to our blog:

Code coverage is essential because it measures how much of your code is executed during testing, helping you to ensure that critical paths and potential bugs are not overlooked.

That’s why we set out to make this information more accessible to find within Codacy. Say “hello” to our new Coverage page!

How It Works 

The new Coverage page is located between the Issues and Pull requests tabs in the main menu. It shows critical metrics and insights related to coverage. These insights are now more actionable than ever, with calls to action displayed when goals or gates are not set for coverage. The Coverage page also provides direct access to files with other quality problems that could benefit from more tests. 

We also made it so Coverage setup assistants will be shown for repositories that don't have coverage yet.

We’ve also added two tables to help users find files that could benefit from better coverage: “Files with issues and low coverage” and “Files with high complexity and low coverage.” 

With this knowledge, developers can immediately identify areas to focus their testing efforts. Try the new Coverage Page and let us know what you think!

RELATED
BLOG POSTS

Code coverage best practices (Part I)
Let’s go over code coverage best practices. After all, it’s not easy being a software engineer — even though you’re trying to do your best, chances are...
Introducing Codacy Coverage: avoid breaking code by expanding unit tests
We are thrilled to launch our revamped product, Codacy Coverage. Taken from a product feature to a standalone solution, Codacy Coverage aims to help...
Try Out Our New Coverage Pipeline Featuring Diff Coverage
Timely and constructive feedback in the pull request (PR) flow is essential to maintaining code quality and fostering a culture of continuous...

Automate code
reviews on your commits and pull request

Group 13