Skip to content

Commit e3f917e

Browse files
committed
doc: running coverage for individual suites
PR-URL: nodejs#25622 Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Vse Mozhet Byt <[email protected]> Reviewed-By: Sakthipriyan Vairamani <[email protected]>
1 parent 1ef175e commit e3f917e

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

BUILDING.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -290,7 +290,8 @@ the first command `./configure --coverage`).
290290
_Generating a test coverage report can take several minutes._
291291

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

295296
```text
296297
$ CI_JS_SUITES=child-process CI_NATIVE_SUITES= make coverage
@@ -299,8 +300,8 @@ $ CI_JS_SUITES=child-process CI_NATIVE_SUITES= make coverage
299300
The above command executes tests for the `child-process` subsystem and
300301
outputs the resulting coverage report.
301302

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

305306
```text
306307
$ CI_JS_SUITES=fs CI_NATIVE_SUITES= make coverage-run-js

0 commit comments

Comments
 (0)