Code Climate vs Scrutinizer: What are the differences?
What is Code Climate? 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.
What is Scrutinizer? Continuous inspection platform - improve code quality and find bugs before they hit production. Scrutinizer is a continuous inspection platform helping you to create better software.
Code Climate and Scrutinizer belong to "Code Review" category of the tech stack.
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, Scrutinizer provides the following key features:
- Continuously measure and track your code quality
- Project quality broken down
- Know your problem areas
"Auto sync with Github" is the primary reason why developers consider Code Climate over the competitors, whereas "Github integration / sync" was stated as the key factor in picking Scrutinizer.
According to the StackShare community, Code Climate has a broader approval, being mentioned in 134 company stacks & 45 developers stacks; compared to Scrutinizer, which is listed in 17 company stacks and 7 developer stacks.
What is Code Climate?
What is Scrutinizer?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
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
This is one of the key tools I can't leave out when I'm working on a project, basically it is mandatory for me to use it on my Ruby on Rails projects. I think the price is a little expensive for a "Solo plan" but if you can get your client to pay, it's definitely worth it. You or the future developers that will continue with the project will thank you!
We use it as part of CI process to check code quality, to ensure that we're not inadvertently making common mistakes and can keep the smells and scope of code changes in line and clean. Having this step here should make future support and additions much more efficient and easy to understand.
Check duplicate code, complexity and common pitfalls. Code coverage indicator for Github README file.
checking our repo code quality.