From f84d89d17c16447f8b0607ea47a9c7068d0cd10a Mon Sep 17 00:00:00 2001 From: cjihrig Date: Sat, 7 Jan 2023 21:16:54 -0500 Subject: [PATCH] doc,lib,src,test: rename --test-coverage Add experimental to the name. --- doc/api/cli.md | 22 +++++++++++----------- doc/api/test.md | 20 +++++++++++--------- doc/node.1 | 6 +++--- lib/internal/process/pre_execution.js | 6 ++++-- lib/internal/test_runner/harness.js | 2 +- lib/internal/test_runner/runner.js | 2 +- src/node_options.cc | 5 +++-- test/parallel/test-runner-coverage.js | 14 ++++++++------ 8 files changed, 42 insertions(+), 35 deletions(-) diff --git a/doc/api/cli.md b/doc/api/cli.md index faaa2957f4dde5..255d7ed00d5bdd 100644 --- a/doc/api/cli.md +++ b/doc/api/cli.md @@ -436,6 +436,17 @@ added: Use this flag to enable [ShadowRealm][] support. +### `--experimental-test-coverage` + + + +When used in conjunction with the `node:test` module, a code coverage report is +generated as part of the test runner output. If no tests are run, a coverage +report is not generated. See the documentation on +[collecting code coverage from tests][] for more details. + ### `--experimental-vm-modules` - -When used in conjunction with the `node:test` module, a code coverage report is -generated as part of the test runner output. If no tests are run, a coverage -report is not generated. See the documentation on -[collecting code coverage from tests][] for more details. - ### `--test-name-pattern`