Need advice about which tool to choose?Ask the StackShare community!
Codecov vs SonarQube: What are the differences?
Codecov: Hosted coverage reports with awesome features to enhance your CI workflow. Our patrons rave about our elegant coverage reports, integrated pull request comments, interactive commit graphs, our Chrome plugin and security; SonarQube: Continuous Code Quality. SonarQube provides an overview of the overall health of your source code and even more importantly, it highlights issues found on new code. With a Quality Gate set on your project, you will simply fix the Leak and start mechanically improving.
Codecov belongs to "Code Coverage" category of the tech stack, while SonarQube can be primarily classified under "Code Review".
"More stable than coveralls" is the primary reason why developers consider Codecov over the competitors, whereas "Tracks code complexity and smell trends" was stated as the key factor in picking SonarQube.
SonarQube is an open source tool with 3.79K GitHub stars and 1.06K GitHub forks. Here's a link to SonarQube's open source repository on GitHub.
According to the StackShare community, SonarQube has a broader approval, being mentioned in 105 company stacks & 61 developers stacks; compared to Codecov, which is listed in 49 company stacks and 29 developer stacks.
My website is brand new and one of the few requirements of testings I had to implement was code coverage. Never though it was so hard to implement using a #docker container.
Given my lack of experience, every attempt I tried on making a simple code coverage test using the 4 combinations of #TravisCI, #CircleCi with #Coveralls, #Codecov I failed. The main problem was I was generating the .coverage file within the docker container and couldn't access it with #TravisCi or #CircleCi, every attempt to solve this problem seems to be very hacky and this was not the kind of complexity I want to introduce to my newborn website.
This problem was solved using a specific action for #GitHubActions, it was a 3 line solution I had to put in my github workflow file and I was able to access the .coverage file from my docker container and get the coverage report with #Codecov.
Pros of Codecov
- More stable than coveralls17
- Easy setup16
- GitHub integration13
- They reply their users11
- Easy setup,great ui9
- Easily see per-commit coverage in GitHub5
- Steve is the man5
- Golang support4
- Merges coverage from multiple CI jobs4
- Code coverage3
- Newest Android SDK preinstalled3
- JSON in web hook3
- Cool diagrams2
- Free for public repositories2
- Bitbucket Integration1
Pros of SonarQube
- Tracks code complexity and smell trends26
- IDE Integration16
- Complete code Review9
- Difficult to deploy1
Sign up to add or upvote prosMake informed product decisions
Cons of Codecov
- GitHub org / team integration is a little too tight1
- Delayed results by hours since recent outage0
- Support does not respond to email0
Cons of SonarQube
- Sales process is long and unfriendly7
- Paid support is poor, techs arrogant and unhelpful7
- Does not integrate with Snyk1
Sign up to add or upvote consMake informed product decisions
What is Codecov?
What is SonarQube?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Codecov?
What companies use SonarQube?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+17