Coveralls vs Scrutinizer

Overview

Coveralls

Stacks1.7K

Followers278

Votes68

Scrutinizer

Stacks94

Followers64

Votes20

Coveralls vs Scrutinizer: What are the differences?

What is Coveralls? 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.

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.

Coveralls can be classified as a tool in the "Code Coverage" category, while Scrutinizer is grouped under "Code Review".

Some of the features offered by Coveralls are:

Repository Coverage Statistics
Individual File Coverage Reports
Line By Line Coverage

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

"Free for public repositories" is the primary reason why developers consider Coveralls over the competitors, whereas "Github integration / sync" was stated as the key factor in picking Scrutinizer.

According to the StackShare community, Coveralls has a broader approval, being mentioned in 58 company stacks & 45 developers stacks; compared to Scrutinizer, which is listed in 17 company stacks and 7 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Coveralls, Scrutinizer

Felipe

May 24, 2020

Needs advice

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.

198k views198k

Comments

Detailed Comparison

Coveralls	Scrutinizer
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.	Scrutinizer is a continuous inspection platform helping you to create better software.
Repository Coverage Statistics;Individual File Coverage Reports;Line By Line Coverage;Repository Overview	Continuously measure and track your code quality;Project quality broken down;Know your problem areas;Works fine with legacy code bases
Statistics
Stacks 1.7K	Stacks 94
Followers 278	Followers 64
Votes 68	Votes 20
Pros & Cons
Pros 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	Pros 7 Github integration / sync 4 Bitbucket integration / sync 2 Gitlab integration / sync 2 Private Git repo sync 1 Free for open source Cons 1 Pricing
Integrations
Travis CI CircleCI Semaphore Jenkins Codeship	GitHub Bitbucket

What are some alternatives to Coveralls, Scrutinizer?

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.

Codacy

Codacy automates code reviews and monitors code quality on every commit and pull request on more than 40 programming languages reporting back the impact of every commit or PR, issues concerning code style, best practices and security.

Phabricator

Phabricator is a collection of open source web applications that help software companies build better software.

Codecov

Our patrons rave about our elegant coverage reports, integrated pull request comments, interactive commit graphs, our Chrome plugin and security.

PullReview

PullReview helps Ruby and Rails developers to develop new features cleanly, on-time, and with confidence by automatically reviewing their code.

Gerrit Code Review

Gerrit is a self-hosted pre-commit code review tool. It serves as a Git hosting server with option to comment incoming changes. It is highly configurable and extensible with default guarding policies, webhooks, project access control and more.

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.

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.

CodeFactor.io

CodeFactor.io automatically and continuously tracks code quality with every GitHub or BitBucket commit and pull request, helping software developers save time in code reviews and efficiently tackle technical debt.

ESLint

A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.

Related Comparisons

Some of the features offered by Coveralls are:

Repository Coverage Statistics
Individual File Coverage Reports
Line By Line Coverage

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

Coveralls vs Scrutinizer