Languages & formats¶

Upload whatever your test tool already writes — the format is detected from the file's content, no flag needed. The snippets below show the plain CLI; in CI, the same file goes in the files: of the GitHub Action or the Bitbucket pipe.

Go¶

go test ./... -covermode=atomic -coverprofile=coverage.out
gocov upload coverage.out

Go profiles record paths under the module path; the CLI reads it from go.mod automatically so diff coverage lines up. Only when uploading from outside the module directory pass -path-prefix yourself.

JavaScript / TypeScript¶

npx jest --coverage             # or vitest run --coverage, nyc, c8 ...
gocov upload coverage/lcov.info

Java / Kotlin¶

mvn verify                      # with the jacoco-maven-plugin
gocov upload target/site/jacoco/jacoco.xml

gradle test jacocoTestReport    # xml.required = true
gocov upload build/reports/jacoco/test/jacocoTestReport.xml

JaCoCo paths are package-qualified (com/example/Foo.java); diff coverage matches them against repo paths by suffix, so source roots like src/main/java need no configuration.

Python¶

pytest --cov --cov-report=xml   # coverage.py / pytest-cov
gocov upload coverage.xml

PHP¶

phpunit --coverage-clover clover.xml
gocov upload clover.xml

Ruby¶

bundle exec rspec               # with simplecov enabled
gocov upload coverage/.resultset.json

Several languages in one repo¶

Upload each report as its own part — a backend suite, a frontend suite, an e2e run — and gocov merges them into one report per commit:

gocov upload -part backend  coverage.out
gocov upload -part frontend coverage/lcov.info