Need advice about which tool to choose?Ask the StackShare community!
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.
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.
Pros of Coveralls
- Free for public repositories45
- Code coverage13
- Ease of integration7
- More stable than Codecov2
- Combines coverage from multiple/parallel test runs1