---
title: "Comment by CODmon Inc on \"How to add SonarQube to a Vue Project.\" | Hashnode"
description: "Doesn't Jest itself have a coverage tool? Why do we need to add Sonar in the first place?"
url: "https://hashnode.com/posts/how-to-add-sonarqube-to-a-vue-project/6277a6d3317fc95a74ca9bb2/comment/627a11c47f98319956cd4402"
---

[Discussion](https://hashnode.com/posts/how-to-add-sonarqube-to-a-vue-project/6277a6d3317fc95a74ca9bb2)

Comment [How to add SonarQube to a Vue Project.](https://hashnode.com/posts/how-to-add-sonarqube-to-a-vue-project/6277a6d3317fc95a74ca9bb2)

[CODmon Inc](https://hashnode.com/@Codmon)

[May 10, 2022](https://hashnode.com/posts/how-to-add-sonarqube-to-a-vue-project/6277a6d3317fc95a74ca9bb2/comment/627a11c47f98319956cd4402)

Doesn't Jest itself have a coverage tool? Why do we need to add Sonar in the first place?

[Ashim Khan](https://hashnode.com/@callbackConundrum)

[May 10, 2022](https://hashnode.com/posts/how-to-add-sonarqube-to-a-vue-project/6277a6d3317fc95a74ca9bb2/comment/627a11c47f98319956cd4402#reply-627ac04f199297a9505d4ce2)

This setup is for the case where you want to check the sonar coverage/report locally before pushing your code to a pipeline. Instead of failing the tests on pipeline, we can check things like bugs/duplication/coverage locally and then push the code, as Jest coverage mostly comes out higher than SonarQube coverage.