# Do Sonarqube support DevTools code coverage?

**URL:** <https://community.sonarsource.com/t/do-sonarqube-support-devtools-code-coverage/144394>\
**Category:** Rules and Languages\
**Tags:** sonarqube, javascript, coverage\
**Created:** [July 14, 2025, 8:07pm UTC](https://community.sonarsource.com/t/do-sonarqube-support-devtools-code-coverage/144394 "2025-07-14T20:07:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ikus060](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ikus060/32/70825_2.png) [@ikus060](https://community.sonarsource.com/u/ikus060)\
**Post date:** [July 14, 2025, 8:07pm UTC](https://community.sonarsource.com/t/do-sonarqube-support-devtools-code-coverage/144394/1 "2025-07-14T20:07:59Z")

</div>

Hello,

I’m exploring ways to generate a coverage report for JavaScript **without instrumenting my code using Istanbul (nyc)**. Ideally, I’d like to leverage the built-in code coverage feature in Chromium DevTools.

My main question is:  
**Does SonarQube support the coverage report format exported from Chrome DevTools for JavaScript code coverage?**

Has anyone successfully enabled code coverage via Chromium DevTools and fed that report into SonarQube? Any best practices or conversion tools/processes to accomplish this would be greatly appreciated.

For reference, I’ve attached an example of the coverage report exported from Chrome DevTools.

Thank you for your help!

[js-coverage.json](https://community.sonarsource.com/uploads/short-url/kDP91IIMry3mogufeBiXV9XTlzc.json) (723.1 KB)

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [July 16, 2025, 7:44am UTC](https://community.sonarsource.com/t/do-sonarqube-support-devtools-code-coverage/144394/2 "2025-07-16T07:44:33Z")

</div>

Hi there,

If you have a coverage report in LCOV format—such as one converted from a Chromium DevTools report—you can specify its path using the [`sonar.javascript.lcov.reportPaths`](https://docs.sonarsource.com/sonarqube-server/latest/analyzing-source-code/test-coverage/test-coverage-parameters/#javaScript-typeScript) parameter when running your SonarQube analysis.

Alternatively, you can convert your coverage data to SonarQube’s [generic coverage format](https://docs.sonarsource.com/sonarqube-server/latest/analyzing-source-code/test-coverage/generic-test-data/#generic-test-coverage), which is also supported.

Remember that SonarQube expects up-to-date coverage information on each scan. Using stale reports may lead to discrepancies if files or lines have changed since the report was generated.