New Research Report - Exploring the 2024 State of Software Quality

Group 370

SAST, DAST, IAST, and RASP: Key Differences and How to Choose

Group 370

Spotlight Whitepaper by IDC on Importance of Automated Code Review Technologies

Group 370

Diff coverage: we have a new metric and quality gate rule for PRs

In this article:
Subscribe to our blog:

We’re excited to announce a new metric and a new quality gate rule for PRs in Codacy 🎉 It’s called diff coverage, and with this new feature, you can now define gates for code coverage and see the diff coverage on your Git provider.

What does diff coverage do

  • It tracks the number of code changes in PRs that are covered by tests;
  • It gives information about your code coverage but scoped to changes in the PR, independently of the overall repository coverage;
  • It is used for grading PRs and can be controlled by quality gates.
Diff coverage metric

Keep on reading to learn more about setting up the quality gates!

Set up a quality gate rule for diff coverage

We know that Codacy lacked good quality settings for coverage. By analyzing PRs with Codacy we could make sure your repo increased or at least maintained the same level of coverage. But what about blocking PRs if they missed your standards for coverage?

Well, we listened to you! We added the ability to define a minimum coverage threshold for pull requests.

Diff coverage quality gate

What diff coverage means for you

  • You can define gates for code coverage (for example, 70% coverage);
  • You can block PRs automatically if the diff coverage of the pull request is lower than the set value;
  • You can see the new diff coverage check on your Git provider.
Git provider blocking PR

Best practice: This feature is particularly useful when your team wants to focus on the coverage of new code or code changes. Do you have a legacy system with low coverage and improving it is a major effort for your team? Use diff coverage to guarantee that new PRs are covered by tests. This will also gradually improve the overall coverage of your repo.

Check out our diff coverage tutorial

To help you get started, we’re sharing a short video tutorial showing how you can set up a quality gate rule for diff coverage. You can also follow the guide on our docs page.

If you have any questions about this feature or need further guidance on setting it up, please let us know. We’d be more than happy to help you!

We’re excited about this release, but your feedback is essential to us! So please give us your thoughts on how we can further improve this feature. Feel free to check our roadmap and submit an idea or contact the support team directly in the in-app chat.


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...
New Pull Request Coverage Diff View Is Live
Developers often struggle to find and keep track of uncovered lines in their pull requests (PRs). Our latest feature, the Pull Request Coverage Diff...
Now live: introducing Coverage summary on your Git provider!
You spoke; we listened! We’re very excited to announce you can now see the Coverage summary directly on GitHub as a Pull Request comment!

Automate code
reviews on your commits and pull request

Group 13