From eac438acc8d887adcb5345064c1c0751006c4d7b Mon Sep 17 00:00:00 2001 From: Benjamin Coe Date: Tue, 22 Jan 2019 12:14:41 -0800 Subject: [PATCH] doc: running coverage for individual suites PR-URL: https://github.com/nodejs/node/pull/25622 Reviewed-By: Michael Dawson Reviewed-By: Vse Mozhet Byt Reviewed-By: Sakthipriyan Vairamani --- BUILDING.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/BUILDING.md b/BUILDING.md index b848f777f36d0e..7e39f50ba17ce0 100644 --- a/BUILDING.md +++ b/BUILDING.md @@ -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 @@ -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