Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Code Climate vs Codacy, the Slant community recommends Code Climate for most people. In the question“What are the best code coverage services?” Code Climate is ranked 4th while Codacy is ranked 5th. The most important reason people chose Code Climate is:
Code Climate gives you suggestions on how to improve the code which you can catalog on Jira.
Specs
Question Ranking
Pros
Pro Gives code improvement suggestions
Code Climate gives you suggestions on how to improve the code which you can catalog on Jira.
Pro Integration with team chat software
Code Climate directly integrates with team chat tools like Slack or HipChat.
Pro Shows test code coverage
Code Climate is fully integrated with test coverage statistics and metrics, giving you a complete view and understanding of them.
Pro Free for open source
Code Climate is completely free for open source projects.
Pro Free for open-source projects
Pro Tons of features, plugins to check code
The list is never ending: they use a lot of open sourced linters for many different languages, allowing to configure them one by one, add custom rules... It checks duplicates, issues, security AND is customizable.
Cons
Con Mostly for web development languages
Code Climate only supports web development projects at the moment. Or at least languages that are widely used in web development (JavaScript, Ruby, Python and PHP). It has no support for largely used languages like Java or C++.
Con Repository token must be set manually for open source projects
The other services tend to automatically integrate with CI services like Travis, but Code Climate requires you to copy your repo's token into your CI service's environment.
Con Web interface doesn't show hits per line
Most code coverage services show both what lines of code were run and how many times each line was run, but Code Climate only shows the former.
Con Reports tons of noisy, irrelevant "quality" metrics
You want code coverage, not someone to tell you where to put semicolons in your markdown documents. It spots dozens of "issues" in your code and Markdown sources, none of which are in any way valid, most of which were random opinions from people with no justification and not accepted best practices. (In fairness, on the Python side, this was due largely to Pylint itself being way too prescriptive.)
Con Can't handle combined coverage
When there are multiple environments that contribute coverage to different branches it just picks one at random and says that the rest of the code isn't covered at all.
Con Dashboard causes Safari to freeze, crash
Con API Tokens need to be hard coded
Most CIs have options for that in safe environment variables, but that makes it unavailable in PRs anyways. The support says they're working on it.
