1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: running coverage for individual suites

Browse Source 
PR-URL: https://github.com/nodejs/node/pull/25622
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
This commit is contained in:
Benjamin Coe 2019-01-22 12:14:41 -08:00
parent 1ef175e5a4
commit e3f917ef65
No known key found for this signature in database
GPG Key ID: 7668A2653280F496
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
BUILDING.md
View File

@ -290,7 +290,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
@ -299,8 +300,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