-
-
Notifications
You must be signed in to change notification settings - Fork 32.6k
Closed as not planned
Labels
duplicateIssues and PRs that are duplicates of other issues or PRs.Issues and PRs that are duplicates of other issues or PRs.test_runnerIssues and PRs related to the test runner subsystem.Issues and PRs related to the test runner subsystem.
Description
Version
v19.7.0
Platform
Linux executive 5.19.0-35-generic #36-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 3 18:36:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
test runner
What steps will reproduce the bug?
Run a test with both --experimental-test-coverage
and --test-reporter=spec
arguments. When using default tap
reporter, the --experimental-test-coverage
shows proper tests code coverage info.
How often does it reproduce? Is there a required condition?
Always.
What is the expected behavior?
Tests code coverage info should be shown.
What do you see instead?
It's not shown.
Additional information
Since spec
reporter is intended to provide an user readable output, I propose to use Istambul text reporter, that's the same being used by Jest, NYC, and by extension also c8.
Metadata
Metadata
Assignees
Labels
duplicateIssues and PRs that are duplicates of other issues or PRs.Issues and PRs that are duplicates of other issues or PRs.test_runnerIssues and PRs related to the test runner subsystem.Issues and PRs related to the test runner subsystem.