Need advice about which tool to choose?Ask the StackShare community!
Code Climate vs Coveralls: What are the differences?
Developers describe Code Climate as "Automated Ruby Code Review". After each Git push, Code Climate analyzes your code for complexity, duplication, and common smells to determine changes in quality and surface technical debt hotspots. On the other hand, Coveralls is detailed as "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.
Code Climate belongs to "Code Review" category of the tech stack, while Coveralls can be primarily classified under "Code Coverage".
Some of the features offered by Code Climate are:
- Automated Git Updates- Nothing to install. Code Climate runs everytime you push a new commit.
- Activity Feeds- Up-to-the-minute information so you can see when and how code changes.
- Instant Notifications- Major security and quality changes pushed to where you work: email, Campfire, HipChat, and RSS feeds.
On the other hand, Coveralls provides the following key features:
- Repository Coverage Statistics
- Individual File Coverage Reports
- Line By Line Coverage
"Auto sync with Github" is the top reason why over 68 developers like Code Climate, while over 44 developers mention "Free for public repositories" as the leading cause for choosing Coveralls.
StackShare, Typeform, and thoughtbot are some of the popular companies that use Code Climate, whereas Coveralls is used by Mapbox, Practo, and Kong. Code Climate has a broader approval, being mentioned in 144 company stacks & 48 developers stacks; compared to Coveralls, which is listed in 58 company stacks and 45 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 Code Climate
- Auto sync with Github71
- Simple grade system that motivates to keep code clean49
- Better coding45
- Free for open source30
- Hotspots for quick refactoring candidates21
- Continued encouragement to a have better / cleaner code15
- Great UI13
- Makes you a better coder11
- Duplication Detection10
- Safe and Secure5
- GitHub only2
- Python inspection2
- Great open community2
- GitHub integration, status inline in PRs2
- Extremely accurate in telling you the errors2
- Uses rubocop2
- Private2
- Locally Installable API1
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 Code Climate
- Learning curve, static analysis comparable to eslint2
- Complains about small stylistic decisions1
Cons of Coveralls
Sign up to add or upvote consMake informed product decisions
What is Code Climate?
What is Coveralls?
Need advice about which tool to choose?Ask the StackShare community!
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
+26
+44