Need advice about which tool to choose?Ask the StackShare community!
Codecov vs Coveralls: 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; Coveralls: Track your project's code coverage over time, changes to files, and badge your GitHub repo. Coveralls works with your CI server and sifts through your coverage data to find issues you didn't even know you had before they become a problem. Free for open source, pro accounts for private repos, instant sign up with GitHub OAuth.
Codecov and Coveralls belong to "Code Coverage" category of the tech stack.
Some of the features offered by Codecov are:
- Beautiful Reports
- Pull Request Comments
- Interactive Commit Graphs
On the other hand, Coveralls provides the following key features:
- Repository Coverage Statistics
- Individual File Coverage Reports
- Line By Line Coverage
"More stable than coveralls" is the top reason why over 14 developers like Codecov, while over 44 developers mention "Free for public repositories" as the leading cause for choosing Coveralls.
According to the StackShare community, Coveralls has a broader approval, being mentioned in 58 company stacks & 45 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 Coveralls
- Free for public repositories45
- Code coverage13
- Ease of integration7
- More stable than Codecov2
- Combines coverage from multiple/parallel test runs1
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 Coveralls
Sign up to add or upvote consMake informed product decisions
What is Codecov?
What is Coveralls?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Codecov?
What companies use Coveralls?
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