Code Climate vs Codecov: 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, Codecov is detailed as "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.
Code Climate and Codecov are primarily classified as "Code Review" and "Code Coverage" tools respectively.
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, Codecov provides the following key features:
- Beautiful Reports
- Pull Request Comments
- Interactive Commit Graphs
"Auto sync with Github" is the top reason why over 68 developers like Code Climate, while over 14 developers mention "More stable than coveralls" as the leading cause for choosing Codecov.
StackShare, Typeform, and thoughtbot are some of the popular companies that use Code Climate, whereas Codecov is used by Repro, ContentSquare, and Talkable. Code Climate has a broader approval, being mentioned in 144 company stacks & 48 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.