qunitjs / qunit / 2863

89%

main: 90%

push

travis-ci-com

Build: Add source maps and Node.js tests to coverage report

* Add BUILD_TARGET=coverage option to Rollup configuration
  to generate source maps.

* Then run the regular CLI tests.
  - Wrapped by the 'nyc' command which lazily instruments any
    files imported at run-time from bin/, src/cli/ or dist/,
    and then writes JSOn data to its private .nyc_output/ to
    keep track of which branches have been coveraged etc.

  - We use --use-spawn-wrap to also track the various bin/qunit.js
    subproceses spawned by our tests.

  - The 'nyc' command would normally immediately produce the
    HTML and LCOV reports, but we're using the --silent option
    to hold back on that.

* Then run the 'grunt qunit' tests in Headless Chrome.
  Just like before, we still use the same coverage bridge to write
  Istanbul's `window.__coverage__` to JSON files, just like NYC
  does for the Node.js tests.
  In order for the coverage report cover all Node.js and browser
  executions, we need to write the data to a single flattened
  directory.
  Subdirectories are not yet supported, so we need a reasonably
  unique file prefix (ref https://github.com/istanbuljs/nyc/issues/879).

* Then run 'nyc report' to generate the reports.

* For the CI build, invoke coveralls, same as before, although
  I've removed the grunt-coveralls wrapper and just used the
  coveralls CLI directly to make things less complicated.

This effectively increases code coverage from 55% to 61%.
It is higher because it now includes branches covered by Node
or CLI only. But it also covers more input files, previously just
dist/, and now bin/ and src/cli/ as well.

738 of 1427 branches covered (51.72%)

1428 of 2342 relevant lines covered (60.97%)

109.31 hits per line