-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
Closed
Labels
coverageIssues and PRs related to native coverage support.Issues and PRs related to native coverage support.feature requestIssues that request new features to be added to Node.js.Issues that request new features to be added to Node.js.test_runnerIssues and PRs related to the test runner subsystem.Issues and PRs related to the test runner subsystem.
Description
What is the problem this feature will solve?
This issue is for tracking remaining work to stabilize code coverage in the test runner. When this feature originally shipped, it had documented limitations. Those have all been resolved.
Note that stabilization does not prevent future semver-minor additions or bug fixes.
Here is the minimum list of things that I think need to be resolved:
- Coverage should be supported via the
run()
API. -
lib/internal/test_runner/coverage.js
should not callparseCommandLine()
. The flags should be passed in. This is related to test_runner: do not read fromprocess.argv
andprocess.cwd()
in run() #53867. -
--experimental-test-coverage
is replaced/aliased with--test-coverage
What is the feature you are proposing to solve the problem?
Eventually stabilizing test runner code coverage
What alternatives have you considered?
No response
MoLow, atlowChemi and tonivj5avivkeller, jaydenseric and tonivj5
Metadata
Metadata
Assignees
Labels
coverageIssues and PRs related to native coverage support.Issues and PRs related to native coverage support.feature requestIssues that request new features to be added to Node.js.Issues that request new features to be added to Node.js.test_runnerIssues and PRs related to the test runner subsystem.Issues and PRs related to the test runner subsystem.