Need advice about which tool to choose?Ask the StackShare community!
Codacy vs Coveralls: What are the differences?
What is Codacy? Automated Code Review. Codacy is an automated code review tool for Scala, Java, Ruby, JavaScript, PHP, Python, CoffeeScript and CSS. It's continuous static analysis without the hassle. Save time in Code Reviews. Tackle your technical debt.
What is 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.
Codacy can be classified as a tool in the "Code Review" category, while Coveralls is grouped under "Code Coverage".
Some of the features offered by Codacy are:
- Monitoring of Technical Debt
- Automated Code Review
- New and Fixed Issues per commit
On the other hand, Coveralls provides the following key features:
- Repository Coverage Statistics
- Individual File Coverage Reports
- Line By Line Coverage
"Automated code review" is the top reason why over 32 developers like Codacy, 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 Codacy, which is listed in 44 company stacks and 23 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 Codacy
- Automated code review44
- Easy setup35
- Free for open source29
- Customizable20
- Helps reduce technical debt18
- Better coding14
- Best scala support13
- Faster Employee Onboarding11
- Duplication detector10
- Great UI10
- PHP integration9
- Python inspection6
- Tools for JVM analysis5
- Many integrations5
- Github Integration4
- Must-have for Java3
- Easy Travis integration3
- Items can be ignored in the UI3
- Asdasdas3
- Gitlab2
- Asdas0
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 Codacy
- No support for private Git or Azure DevOps git6
Cons of Coveralls
Sign up to add or upvote consMake informed product decisions
What is Codacy?
What is Coveralls?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Codacy?
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
+8