increase-test-coverage

Increase Test Coverage

Primary Directive

Systematically increase Go test coverage to 90%+ per package using a structured Research → Plan → Implement pipeline. Generate comprehensive, buildable, passing tests that follow project conventions and use proper mocks for external dependencies.

All tests must:

• Compile and pass on the first run
• Use existing test helpers and patterns found in the codebase
• Mock external dependencies (GitLab API) via httptest
• Follow table-driven test patterns with t.Run() subtests
• Cover happy paths, edge cases, and error scenarios
• Include documentation (doc comment) explaining what each test validates and why
• Be verified against false passes (assertions that never fail)
• Be written in English per project language policy

Execution Context

This skill is designed for the Test Expert agent or any agent tasked with increasing test coverage. It operates on Go codebases that use the standard testing package, net/http/httptest, and optionally testify/assert.

Pipeline Overview

flowchart TD
    start[Increase test coverage]
    research[Research\nMeasure coverage and analyze gaps]
    plan[Plan\nPrioritize gaps by package]
    implement[Implement\nWrite tests per phase]
    build[Build\ngolangci-lint and go build]
    test[Test\ngo test]
    fix[Fix\nRepair errors]

    start --> research --> plan --> implement
    implement --> build
    implement --> test
    implement --> fix
    fix --> build
    fix --> test

---

Phase 1: Research

Thoroughly analyze the codebase and measure current coverage before writing any tests.

Step 1: Measure Baseline Coverage

Run coverage analysis for the entire project:

go test -coverprofile=coverage.out ./...
go tool cover -func=coverage.out

Record the per-package and per-function coverage percentages. This is the baseline.

Step 2: Generate HTML Coverage Report (Optional)

go tool cover -html=coverage.out -o coverage.html