{"id":9338,"date":"2026-04-22T08:43:00","date_gmt":"2026-04-22T06:43:00","guid":{"rendered":"https:\/\/www.almtoolbox.com\/blog\/?p=9338"},"modified":"2026-06-01T08:51:31","modified_gmt":"2026-06-01T06:51:31","slug":"sonarqube-test-coverage-overview","status":"publish","type":"post","link":"https:\/\/www.almtoolbox.com\/blog\/sonarqube-test-coverage-overview\/","title":{"rendered":"How Code Coverage in SonarQube Helps Developers, QA Managers, DevOps, R&D Managers, and Security Managers"},"content":{"rendered":"\n
\"sonarqube<\/figure>\n\n\n\n
\n
<\/figure>\n<\/div>\n\n\n\n

In recent years, SonarQube<\/em> has become the de facto standard for monitoring code quality and code security in high-tech and enterprise organizations, including in Israel.<\/p>\n\n\n\n

One of the most important metrics that SonarQube displays is Code Coverage<\/em><\/strong> \u2013 code coverage,
which measures how much of your executed code is actually “touched” by your automated tests.<\/p>\n\n\n\n

In this article, we will explain to developers, team leads, and R&D managers:<\/p>\n\n\n\n

    \n
  1. What is Code Coverage, and what can SonarQube do with it?<\/li>\n\n\n\n
  2. How does SonarQube actually work with code coverage (JaCoCo, Cobertura, Coverage.py, Jest, and more)?<\/li>\n\n\n\n
  3. What are the benefits for each role \u2013 developers, team leads, R&D managers, and DevOps?<\/li>\n\n\n\n
  4. What code coverage capabilities are available in each SonarQube edition (Community \/ Developer \/ Enterprise)?<\/li>\n\n\n\n
  5. Practical tips for setting up Quality Gates and coverage thresholds, including working with GitLab \/ GitHub \/ Azure DevOps.<\/li>\n<\/ol>\n\n\n\n
     <\/div>\n\n\n\n

    What is Code Coverage anyway \u2013 and why should you care?<\/h2>\n\n\n\n

    Code Coverage measures what part of your code is actually executed by unit, integration, and End-to-End tests.<\/p>\n\n\n\n

    It doesn’t tell you if the tests are “good”, but it does tell you whether they even touch sensitive code before you promote the code further.<\/p>\n\n\n\n

    SonarQube uses code coverage as a core metric in the Quality Gate<\/em> \u2013
    a quality gate that decides whether a version or Merge Request is “healthy” enough to proceed further toward integration and release.<\/p>\n\n\n\n

    For example, you can decide not to approve a merge if the Coverage on New Code<\/strong> is below 80%.<\/p>\n\n\n\n

     <\/div>\n\n\n\n

    Important to understand: SonarQube does not run tests \u2013 it analyzes reports<\/h2>\n\n\n\n

    Critical point: SonarQube does not run the tests<\/strong> and does not calculate coverage on its own. It relies on reports that have already been generated by your standard tools:<\/p>\n\n\n\n