overalls alternatives and similar packages
Based on the "Continuous Integration" category.
Alternatively, view overalls alternatives based on common mentions on social networks and blogs.
drone9.9 5.4 overalls VS droneDrone is a Container-Native, Continuous Delivery Platform
CDS9.0 7.4 overalls VS CDSEnterprise-Grade Continuous Delivery & DevOps Automation Open Source Platform
woodpecker8.5 9.5 overalls VS woodpeckerWoodpecker is a community fork of the Drone CI system.
Buildkite7.6 8.3 overalls VS BuildkiteThe Buildkite Agent is an open-source toolkit written in Go for securely running build jobs on any device or network
goveralls7.2 2.1 overalls VS goverallsGo integration for Coveralls.io continuous code coverage tracking system.
duci3.6 4.5 overalls VS duciThe simple ci server
Template for GitHub Apps built with GolangTemplate for building GitHub Apps in Go.
gomason3.2 0.0 overalls VS gomasonA tool for testing, building, signing, and publishing binaries.
Flutter2.4 0.0 overalls VS FlutterBitrise step for Flutter
roveralls1.9 0.0 overalls VS roverallsA Go recursive coverage testing tool
go-fuzz-action1.2 3.2 overalls VS go-fuzz-actionGitHub Action for Go 1.18 fuzz testing
go-test-coverage0.9 10.0 overalls VS go-test-coveragego-test-coverage is tool and github action which reports issues when test coverage is below set threshold
gotestfmt0.2 5.7 overalls VS gotestfmtgo test output for humans
ONLYOFFICE Docs — document collaboration in your environment
Do you think we are missing an alternative of overalls or a related project?
Package overalls takes multi-package go projects, runs test coverage tests on all packages in each directory and finally concatenates into a single file for tools like goveralls and codecov.io.
Usage and documentation
overalls -project=github.com/go-playground/overalls -covermode=count -debug
then with other tools such as goveralls
goveralls -coverprofile=overalls.coverprofile -service semaphore -repotoken $COVERALLS_TOKEN
mv overalls.coverprofile coverage.txt export CODECOV_TOKEN=### bash <(curl -s https://codecov.io/bash)
goveralls and codecover currently do not calculate coverage the same way as
go tool coversee here and here.
overalls (and go test) by default will not calculate coverage "across" packages. E.g. if a test in package A covers code in package B overalls will not count it. You may or may not want this depending on whether you're more concerned about unit test coverage or integration test coverage. To enable add the coverpkg flag.
overalls -project=github.com/go-playground/overalls -covermode=count -debug -- -coverpkg=./...
$ overalls -help usage: overalls -project=[path] -covermode[mode] OPTIONS -- TESTOPTIONS overalls recursively traverses your projects directory structure running 'go test -covermode=count -coverprofile=profile.coverprofile' in each directory with go test files, concatenates them into one coverprofile in your root directory named 'overalls.coverprofile' OPTIONS -project Your project path as an absolute path or relative to the '$GOPATH/src' directory example: -project=github.com/go-playground/overalls -covermode Mode to run when testing files. default:count OPTIONAL -ignore A comma separated list of directory names to ignore, relative to project path. example: -ignore=[.git,.hiddentdir...] default: '.git' -debug A flag indicating whether to print debug messages. example: -debug default:false -concurrency Limit the number of packages being processed at one time. The minimum value must be 2 or more when set. example: -concurrency=5 default: unlimited
Any flags after
-- will be passed as-is to
overalls -project=$PROJECT -debug -- -race -v
go test -race -v under the hood in addition to the
How to Contribute
Make a pull request.
If the changes being proposed or requested are breaking changes, please create an issue.
Distributed under MIT License, please see license file in code for more details.
*Note that all licence references and agreements mentioned in the overalls README section above are relevant to that project's source code only.