Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariSonarCloud vs Codacy
When comparing SonarCloud vs Codacy, the Slant community recommends Codacy for most people. In the question“What are the best code coverage services?” Codacy is ranked 5th while SonarCloud is ranked 6th.
Specs
Question Ranking
Pros
Pro Multi language
Support for more than 20 programming languages.
Pro Branch analysis
SonarCloud features automatic analysis of project branches and pull requests as soon as they get created.
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 Seems extremely Java-focused, despite advertising support for many languages
Con Setup instructions don't work
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.
