Code Climate vs Coveralls

Need advice about which tool to choose?Ask the StackShare community!

Code Climate

505
450
+ 1
278
Coveralls

515
259
+ 1
68
Add tool

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.

Decisions about Code Climate and Coveralls

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.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Code Climate
Pros of Coveralls
  • 71
    Auto sync with Github
  • 49
    Simple grade system that motivates to keep code clean
  • 45
    Better coding
  • 29
    Free for open source
  • 21
    Hotspots for quick refactoring candidates
  • 15
    Continued encouragement to a have better / cleaner code
  • 13
    Great UI
  • 11
    Makes you a better coder
  • 10
    Duplication Detection
  • 5
    Safe and Secure
  • 2
    Private
  • 1
    Locally Installable API
  • 1
    Uses rubocop
  • 1
    Extremely accurate in telling you the errors
  • 1
    GitHub only
  • 1
    Python inspection
  • 1
    great open community
  • 1
    GitHub integration, status inline in PRs
  • 45
    Free for public repositories
  • 13
    Code coverage
  • 7
    Ease of integration
  • 2
    More stable than Codecov
  • 1
    Combines coverage from multiple/parallel test runs

Sign up to add or upvote prosMake informed product decisions

Cons of Code Climate
Cons of Coveralls
  • 1
    Learning curve, static analysis comparable to eslint
  • 1
    Complains about small stylistic decisions
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    What is Code Climate?

    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 Coveralls?

    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.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Code Climate?
    What companies use Coveralls?
    See which teams inside your own company are using Code Climate or Coveralls.
    Sign up for Private StackShareLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Code Climate?
    What tools integrate with Coveralls?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    GitHubPythonNode.js+26
    28
    15373
    GitHubSlackMySQL+44
    109
    50194
    What are some alternatives to Code Climate and Coveralls?
    Codacy
    Codacy automates code reviews to improve and standardize code quality across large enterprises. It identifies issues through static code analysis. Integrates with GitLab, GitHub & Bitbucket.
    Codecov
    Our patrons rave about our elegant coverage reports, integrated pull request comments, interactive commit graphs, our Chrome plugin and security.
    SonarQube
    SonarQube provides an overview of the overall health of your source code and even more importantly, it highlights issues found on new code. With a Quality Gate set on your project, you will simply fix the Leak and start mechanically improving.
    GitPrime
    GitPrime uses data from GitHub, GitLab, BitBucket—or any Git based code repository—to help engineering leaders move faster, optimize work patterns, and advocate for engineering with concrete data.
    RuboCop
    RuboCop is a Ruby static code analyzer. Out of the box it will enforce many of the guidelines outlined in the community Ruby Style Guide.
    See all alternatives