⠀⠀⠀⠀⠀⠀⣿
⠀⠀⠀⠀⠀⣼⣿⣧⠀⠀⠀⠀⠀ ⠀⠀ ⣠⣶⣾⣿⡇⢀⣴⣾⣿⣷⣆ ⣿⣿⠀⣰⣿⡟⢸⣿⣿⣿⡇ ⣿⣿⣿⣷⣦⠀⠀⢠⣿⣿⣿⠀⠀⣿⣿⠁⠀⣼⣿⡇⠀⢀⣴⣾⣿⡷
⠶⣶⣶⣶⣾⣿⣿⣿⣷⣶⣶⣶⠶ ⣸⣿⡟ ⠀⢠⣿⣿⠃⠈⣿⣿⠀⣿⣿⢠⣿⡿⠀⣿⣿⣧⣤⠀⢸⣿⡇⣠⣿⡿⠀⢠⣿⡟⣿⣿⠀⢸⣿⡿⠀⠀⣿⣿⠃⠀⢸⣿⣧⣄
⠀⠀⠙⢻⣿⣿⣿⣿⣿⡟⠋⠁⠀⠀ ⣿⣿⡇⠀ ⢸⣿⣿⠀⣸⣿⡟⠀⣿⣿⣾⡿⠁ ⣿⣿⠛⠛⠀⣿⣿⢿⣿⣏⠀⢀⣿⣿⣁⣿⣿⠀⣾⣿⡇⠀⢸⣿⡿⠀⠀⡀⠙⣿⣿⡆
⠀⠀⢠⣿⣿⣿⠿⣿⣿⣿⡄⠀⠀⠀ ⠙⢿⣿⣿⠇⠈⠿⣿⣿⡿⠋⠀⠀⢿⣿⡿⠁⠀⢸⣿⣿⣿⡇⢸⣿⣿⠀⣿⣿⣄⣾⣿⠛⠛⣿⣿⢠⣿⣿⣿ ⣼⣿⣿⣿ ⣿⣿⡿⠋⠀
⠀⢀⣾⠟⠋⠀⠀⠀⠙⠻⣷⡀⠀⠀
Auto-detects your coverage artifact files and CI environment to post to Coveralls.io.
You can omit -C /usr/local/bin
argument to keep it in current directory.
curl -L https://coveralls.io/coveralls-linux.tar.gz | tar -xz -C /usr/local/bin
brew tap coverallsapp/coveralls
brew install coveralls
Bash
curl -L https://github.com/coverallsapp/coverage-reporter/releases/latest/download/coveralls-windows.exe -o coveralls.exe
PowerShell
Invoke-WebRequest -Uri "https://github.com/coverallsapp/coverage-reporter/releases/latest/download/coveralls-windows.exe" -OutFile "coveralls.exe"
See also environment variables list and YAML config that control the utility behavior.
# Automatic lookup for supported reports and sending them to https://coveralls.io
coveralls report
# Provide explicit repo token
coveralls report --repo-token=rg8ZznwNq05g3HDfknodmueeRciuiiPDE
# Use concrete report file
coveralls report coverage/lcov.info
# Use parallel reports (must reference the same build number)
coveralls report project1/coverage/lcov.info --parallel --build-number 1
coveralls report project2/coverage/lcov.info --parallel --build-number 1
# ...
coveralls done --build-number 1
# Provide a job flag and use carry-forwarding
coveralls report --job-flag "unit-tests" --parallel --build-number 2
coveralls report --job-flag "integration-tests" --parallel --build-number 2
coveralls done --carryforward "unit-tests,integration-tests" --build-number 2
# Testing options: no real reporting, print payload
coveralls report --debug --dry-run
coveralls --help
With values used for --format
option:
lcov
simplecov
cobertura
jacoco
gcov
golang
coveralls
python
clover
You can add a report parser to this project by following these instructions.
Bounty: One or more months of free service at Coveralls.io. Contact us to learn more.
Docs on environment variables for other CI support.
How to use the Reporter with an officially-unsupported CI service. See instructions.
See development instructions to add support for a new CI service.
If your coverage report format is not one of the ones above (in Supported Coverage Report Formats), you could try finding a library to convert your format into one of the supported formats.
Otherwise, if you want to use the Reporter, you could add support for your coverage report format.
See development instructions to add support for a new coverage report format.
Set this environment variable to your instance's host:
COVERALLS_ENDPOINT=https://coveralls-enterprise.example.com
SSL check will be automatically disabled to allow self-signed certificates.
More info: https://enterprise.coveralls.io
To get started you will need crystal installed on your machine and then you can run:
shards install
make # bin/coveralls will be created
Run specs:
make test
vagrant up
# to re-run provision script
vagrant provision
# to access Windows VM
vagrant ssh
# type powershell<enter>
Cutting new releases.
$ make new_version
New version: 1.2.3
Brief description: new coverage report support
$ git push origin master --follow-tags
After the release is available, see Homebrew release instructions.
src/coverage_reporter.cr
and shard.yml
git commit --message "X.X.X: <short changes description>"
git tag --annotate vX.X.X
with the same annotation as commit messagegit push origin master --follow-tags
GitHub release will be created automatically. After the release is available, see Homebrew release instructions.
In the homebrew-coveralls repo, a new PR will automatically get
created. Once the brew test-bot
checks have passed, label the PR with the
pr-pull
tag in order to make the release available through Homebrew.