Coverage

This module uses nyc to track code coverage, even across subprocess boundaries. It is enabled by default, and there's nothing extra you need to do to use it.

Nyc in turn uses istanbul to do the actual coverage code transformation and reporting.

To disable coverage, run your tests with the --no-coverage argument. To re-enable, add the --coverage argument.

Maximal Coverage 💯

As of version 7, node-tap lets you easily enforce 100% coverage of all lines, branches, functions, and statements with one easy flag, if that's your thing:

{
  "scripts": {
    "test": "tap --100"
  }
}

If you do this in an open source module, please join the exclusive 100 club.

Travis-CI and Coveralls.io Integration

You can very easily take advantage of continuous test coverage reports by using Travis-CI and Coveralls.

  1. Enable Travis-CI by signing up, enabling tests on your repo, and adding a .travis.yml file to your repo. You can use this module's .travis.yml file as an example
  2. Enable Coveralls.io by signing up, and adding the repo. Note the repo API token.
  3. Back at Travis-CI, add a private environment variable. The name of the environment variable is COVERALLS_REPO_TOKEN, and the value is the token you got from Coveralls.
  4. When that token is set in the environment variable, tap will automatically generate coverage information and send it to the appropriate place.

Uploading Coverage to Other Services

There's no requirement that you use Coveralls! Any coverage service that understands lcov can be used as well.

For example, using CodeCov, you can do the following:

  1. Add codecov as a devDependency in your project with this command:

    npm install codecov --save-dev
  2. Add a test script that generates coverage information, and a posttest that uploads it to codecov:

    {
      "scripts": {
        "test": "tap",
        "posttest": "tap --coverage-report=text-lcov | codecov"
      }
    }

Local Coverage Reporting

Printing out a coverage report can be done along with tests, or after any covered test run, using the --coverage-report=<type> argument.

The most popular types are text and html, but any report style supported by istanbul is available, including:

  • clover
  • cobertura
  • html
  • json
  • json-summary
  • teamcity
  • text
  • text-lcov
  • text-summary

To specify a report format, you can use --coverage-report=<type>. The default type is text, which produces a pretty text-only table on the terminal. If you specify --coverage-report=html, then tap will attempt to launch a web browser to view the report after the test run. You can prevent launching a browser by specifying the flag --no-browser.

Coverage Maps

There are some situations where you may want to precisely specify which tests should provide coverage for which program files, or which tests perhaps should not be instrumented for code coverage at all.

In those cases, use a coverage map option.