SonarQube是否必须借助外部代码覆盖率工具（如Jacoco等）展示覆盖率？

Great question! Let me cut to the chase first: Yes, SonarQube always requires an external code coverage tool to display coverage data on its server. Here's why and how it works:

SonarQube itself doesn't have built-in capabilities to generate code coverage metrics. Its job is to parse, aggregate, and visualize the coverage reports produced by language-specific third-party tools. Without these external tools, SonarQube has no data to show in its coverage dashboard—you'll just see 0% coverage or empty metrics.

Here are the common pairings for popular languages:

• Java/Kotlin: The standard tool is Jacoco (though older setups might use Cobertura). You'll generate a coverage report (usually in .exec or .xml format) during your build, then configure SonarQube to pick this up during analysis.
• Python: coverage.py is the go-to choice. Run it to generate a coverage report (often .xml or plain text), then pass the report path to SonarQube via analysis parameters like sonar.python.coverage.reportPaths.
• C/C++: You'll typically use gcov to generate raw coverage data, then lcov to convert it into an .info report that SonarQube can parse.
• JavaScript/TypeScript: Tools like Jest, Istanbul, or Cypress generate coverage reports (often in lcov.info format) that SonarQube integrates with seamlessly.

In short: SonarQube is the "dashboard" for your coverage data, but you need external tools to collect that data in the first place. No external tool = no coverage data to display.

内容的提问来源于stack exchange，提问作者mandar munagekar