Go Coverage
Framework Configuration
Key Requirements
- Coverage report must be in LCOV format
- Report must be saved as
coverage/lcov.info - Report must be uploaded as a GitHub Actions artifact named
coverage-report
Go has built-in support for test coverage with the go test command. By default, Go generates coverage reports in its own format, but you can easily convert them to LCOV format using the gcov2lcov tool.
Test Example
package calculator
import "testing"
func TestAdd(t *testing.T) {
result := Add(2, 3)
if result != 5 {
t.Errorf("Add(2, 3) = %d; want 5", result)
}
}
func TestSubtract(t *testing.T) {
result := Subtract(5, 3)
if result != 2 {
t.Errorf("Subtract(5, 3) = %d; want 2", result)
}
}Makefile (Optional)
# Makefile
.PHONY: test coverage
test:
go test -v ./...
coverage:
go test -v -coverprofile=coverage/coverage.out ./...
go tool cover -html=coverage/coverage.out -o coverage/coverage.html
coverage-lcov:
go test -v -coverprofile=coverage/coverage.out ./...
go install github.com/jandelgado/gcov2lcov@latest
gcov2lcov -infile=coverage/coverage.out -outfile=coverage/lcov.infoSetting Up GitHub Actions
Create a workflow file in .github/workflows/ directory. The filename can be anything you prefer (e.g. go-coverage.yml). Add the following content to your workflow file:
name: Go Coverage
# Run on target branch (probably default branch like main) to track coverage history
on:
push:
branches:
- main
# Optional: Only run when relevant files change (customize as needed)
paths:
- '**/*.go'
- go.mod
- go.sum
pull_request:
branches:
- main
paths:
- '**/*.go'
- go.mod
- go.sum
- '!.github/workflows/**'
workflow_dispatch:
# Auto-cancel outdated runs on the same branch
concurrency:
group: ${{ github.workflow }}-${{ github.head_ref || github.ref }}
cancel-in-progress: true
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v6
- name: Set up Go
uses: actions/setup-go@v5
with:
go-version: 'stable'
check-latest: true
- name: Install dependencies
run: go mod download
# PR: tests only, Push: tests with coverage
- name: Run tests
if: github.event_name == 'pull_request'
run: go test -v ./...
- name: Run tests with coverage
if: github.event_name == 'push'
run: |
mkdir -p coverage
go test -v -coverprofile=coverage/coverage.out ./...
- name: Convert to LCOV format
if: github.event_name == 'push'
run: |
go install github.com/jandelgado/gcov2lcov@latest
gcov2lcov -infile=coverage/coverage.out -outfile=coverage/lcov.info
- name: Upload coverage reports
if: github.event_name == 'push'
uses: actions/upload-artifact@v6
with:
name: coverage-report
path: coverage/lcov.infoKey Configuration Points
- Run tests with
-coverprofileflag to generate coverage data - Install and use
gcov2lcovto convert Go coverage to LCOV format - Upload the report as an artifact - name must be either
coverage-reportor end withlcov.info - Ensure the artifact contains
coverage/lcov.infofile
Why !.github/workflows/** on PRs Only?
On pull requests, we exclude workflow file changes to keep the setup PR minimal. When you're adding or editing a workflow file, pre-existing test failures in your codebase are irrelevant and shouldn't block the PR. On push(after merge to main), we don't exclude them so that the initial coverage report gets generated on your target branch.
Viewing Coverage Reports
After your workflow runs successfully, GitAuto automatically processes the coverage reports and displays them in the Coverage Dashboard. GitAuto only saves coverage data when the workflow runs on your target branch (configurable in your repository's Rules page, defaults to your repository's default branch, e.g., main or master). This typically happens when:
- You merge a pull request to your target branch
- You push directly to your target branch
- You manually trigger the workflow
About LCOV:LCOV (Linux Code Coverage) is a standard format for code coverage data. It's pronounced "el-cov" and is widely supported by various tools and services.
Using multiple languages? If your repository has multiple programming languages (the docs use PHP + JavaScript as an example, but any combination works), see our Multi-Language Coverage guide for setting up coverage across all languages.
Go Coverage Confusion?
Go testing is straightforward, but coverage configuration can be tricky! Whether you're dealing with module paths, coverage gaps, or CI/CD setup issues, we're here to help!
Contact us and let's get your Go tests covered!