Coveralls vs uberalls

Overview

Coveralls

Stacks1.7K

Followers278

Votes68

uberalls

Stacks36

Followers62

Votes0

GitHub Stars186

Forks14

Coveralls vs uberalls: What are the differences?

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; uberalls: *Track code coverage metrics with Jenkins and Phabricator *. Code coverage metric storage service. Provide coverage metrics on differentials with Phabricator and Jenkins, just like Coveralls does for GitHub and TravisCI.

Coveralls and uberalls can be primarily classified as "Code Coverage" tools.

uberalls is an open source tool with 160 GitHub stars and 11 GitHub forks. Here's a link to uberalls's open source repository on GitHub.

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, uberalls

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	uberalls
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 coverage metric storage service. Provide coverage metrics on differentials with Phabricator and Jenkins, just like Coveralls does for GitHub and TravisCI.
Repository Coverage Statistics;Individual File Coverage Reports;Line By Line Coverage;Repository Overview	-
Statistics
GitHub Stars -	GitHub Stars 186
GitHub Forks -	GitHub Forks 14
Stacks 1.7K	Stacks 36
Followers 278	Followers 62
Votes 68	Votes 0
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	No community feedback yet
Integrations
Travis CI CircleCI Semaphore Jenkins Codeship	Jenkins Phabricator

What are some alternatives to Coveralls, uberalls?

Codecov

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

Istanbul

It is a JS code coverage tool that computes statement, line, function and branch coverage with module loader hooks to transparently add coverage when running tests. Supports all JS coverage use cases including unit tests, server side functional tests and browser tests. Built for scale.

Related Comparisons