Go test coverage

Ask your coding agent to set up Supercov in your project:

Run Supercov with go run github.com/supercorp-ai/supercov/cmd/supercov@latest.
Read supercov docs and check the supported Go toolchain before running our
existing go test suite. Follow supercov docs assertion-agent to build and
validate the assertion map. Show the coverage report and any measurement
limits. Don't change
application code or tests.

Run it yourself

Go support requires Go 1.22 or newer. A Go project needs Go and nothing else: go run with a version suffix resolves Supercov by module path, so it neither needs nor touches the go.mod in your current directory.

go run github.com/supercorp-ai/supercov/cmd/supercov@latest --version

You don’t need Node.js. If you would rather install the binary once, Homebrew and the platform archives on the latest release carry the same build at the same version.

Run your tests

From your module root:

go run github.com/supercorp-ai/supercov/cmd/supercov@latest -- go test ./...

Keep the flags your suite normally uses. Your package selection, -run filters and test flags still apply.

Inspect the run:

supercov runs latest
supercov runs latest gaps --limit 5

Check what the tests assert

Line coverage tells you a statement ran. It does not tell you that a test checked the result. The setup prompt asks your agent to map assertions to the code they check, and Supercov validates that map against execution and passing assertions in the same test. The assertion guide explains the score and why some statements, including test code, may remain unmapped.

Go-specific limits

Supercov measures the packages go test builds, not every .go file in the directory tree. Generated files and build-tagged code are measured only when the build includes them. See runner support for the detail available from go test and its measurement limits.

supercov docs coverage-model prints the guide for your installed version.