Code Coverage With Gocov And Wercker

Wercker is a company that enables development teams to achieve their CI/CD goals with microservices and Docker.

Pieter Joost van de Sande
Pieter Joost van de Sande
August 5, 2013

Code coverage can be an important metric to watch. It gives you insight in which parts of your code are covered well by tests and which might need some extra attention.

In this post I will explain how I leverage gocov in adding test coverage reports to the build pipeline of one of my go projects.


Executing tests with gocov

To measure test coverage in Go we can use gocov created by Andrew Wilkins. It has atest command that executes the test with the default go test test runner and generates the coverage details in json format. The gocov test command respects the go test command and still prints output from it to the console. Here is an example of a script step that runs the tests for all packages and subpackages of the working directory and writes the coverage results to a file called coverage.json:

    - script:
        name: Test
        code: |-
          # Get gocov package
            go get

            # Execute actual tests and store coverage result
            gocov test ./... > coverage.json

Next to the coverage.json that will be created, it writes the following output:

  ok 0.070s
  ok  0.023s
  ok 0.022s
  ok 0.012s
  ?  [no test files]
  ok  0.021s
  ? [no test files]
  ? [no test files]

You can see the actual step result on wercker: go-cqrs / 6c8cd61 / test.

Generating the report

The coverage.json created by the previous step can now be used as input for thereport command. This commands generates a textual report based on thecoverage.json. It makes sence to do this in a seperate step to seperate the test output and the coverage output. Here is an example of a script step that executes thegocov report command:

  - script:
        name: Coverage
        code: gocov report coverage.json

This step will write the following output:     InitLogging     100.00% (3/3)  EventStore.ReadStream   0.00% (0/27)  EventStore.WriteStream  0.00% (0/22)  downloadEvent     0.00% (0/13)  processFeed     0.00% (0/9)  linksToMap    0.00% (0/4)  DailEventStore    0.00% (0/1)      ----------------------  3.80% (3/79)  InitLogging   100.00% (3/3)     -----------   100.00% (3/3)

You can see the actual step result on wercker: go-cqrs / 6c8cd61 / coverage.

Writing to the artifact dir

The coverage.json can also be used to create a nice self sufficient html report. We can use gocov-html tool for this. Here is how I enchanced the previous step and added html reporting that is stored in the artifact directory.

- script:
    name: Coverage
    code: |-
        go get
        gocov report coverage.json
        gocov-html coverage.json > $WERCKER_REPORT_ARTIFACTS_DIR/coverage.html

When this step succeeds you can download the artifacts package and opencoverage.html.

coverage report

What is next

Now wercker gives insight in your test coverage for your golang projects. The next step is to use the coverage as a number to pass or fail the build. Stay tuned for an update where we will create a step to do this.

Earn some stickers!

Let us know about the applications you build with wercker. Don’t forget to tweet out a screenshot of your first green build with #wercker and we’ll send you some @wercker stickers.

Follow us on twitter as well to stay in the loop.