Skip to content

Commit

Permalink
doc: running coverage for individual suites
Browse files Browse the repository at this point in the history
PR-URL: #25622
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
Reviewed-By: Sakthipriyan Vairamani <[email protected]>
  • Loading branch information
bcoe authored and addaleax committed Jan 23, 2019
1 parent 7490fc8 commit eac438a
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions BUILDING.md
Original file line number Diff line number Diff line change
Expand Up @@ -281,7 +281,8 @@ the first command `./configure --coverage`).
_Generating a test coverage report can take several minutes._

To collect coverage for a subset of tests you can set the `CI_JS_SUITES` and
`CI_NATIVE_SUITES` variables:
`CI_NATIVE_SUITES` variables (to run specific suites, e.g., `child-process`, in
isolation, unset the opposing `_SUITES` variable):

```text
$ CI_JS_SUITES=child-process CI_NATIVE_SUITES= make coverage
Expand All @@ -290,8 +291,8 @@ $ CI_JS_SUITES=child-process CI_NATIVE_SUITES= make coverage
The above command executes tests for the `child-process` subsystem and
outputs the resulting coverage report.

Alternatively, for the JavaScript test suite, you can use the `CI_JS_SUITES`
variable to run tests in isolation, outputting reports:
Alternatively, you can run `make coverage-run-js`, to execute JavaScript tests
independently of the C++ test suite:

```text
$ CI_JS_SUITES=fs CI_NATIVE_SUITES= make coverage-run-js
Expand Down

0 comments on commit eac438a

Please sign in to comment.