11
User
Recs.
Recs.
49
Updates
Last
Updated
Updated
Activity
7 Options
Specs
Specs are quantitative aspects of the option such as the price
Pros
Pro Maturity
Coveralls is older than Code Climate and already supports 21 languages. It also seems like it's the most popular given how new some of the other services are, which is great for support.
Know any positive aspects of this option?
Cons
Know any negative aspects of this option?
Recommendations
Coveralls
Recommended 5 years ago
Coveralls seems to be more thorough than Codecov, e.g. here missed branch is spotted by coveralls: https://coveralls.io/builds/23880418/source?filename=index.js#L259 while nothing is found by codecov: https://codecov.io/gh/dmitriz/cpsfy/branch/ap1
Pro
Free for open sourcePro
MaturityCoveralls
4 years ago
A pain to set up when you want to merge multiple test reports. Docs for CI integration are badly out of date. They rely on community contributed libraries for some languages. They take their own custom format over an HTTP POST request for coverage reporting rather than accepting some of the more standard for...
Con
The user interface is hard to understandCon
Terrible supportCon
It's defective and integration doesn't work properlyCon
Poor toolingCon
No support for common coverage report stadardsComments
Flagged Pros + Cons
Con Repo must be on github or bitbucket
Coveralls only supports repositories that are hosted on GitHub or Bitbucket.
Out of Date Pros + Cons
Pro Integration with Travis CI
Coveralls works really well with Travis and it's very easy to integrate the two. The code coverage is run in the Travis build, along with the tests. The data is then sent to Coveralls for tracking.
To add support for Coveralls to the travis.yml
file, we set the COVERALLS
environment variable to true. For example, for Lisp you would do:
env:
matrix:
- LISP=sbcl COVERALLS=true
- LISP=ccl