Skip to content

test_runner: print coverage report with dot reporter#63443

Open
MD-Mushfiqur123 wants to merge 1 commit into
nodejs:mainfrom
MD-Mushfiqur123:fix/dot-reporter-coverage
Open

test_runner: print coverage report with dot reporter#63443
MD-Mushfiqur123 wants to merge 1 commit into
nodejs:mainfrom
MD-Mushfiqur123:fix/dot-reporter-coverage

Conversation

@MD-Mushfiqur123
Copy link
Copy Markdown

What

Print coverage report output when using the dot reporter with --experimental-test-coverage.

Why

Closes #60884. When running tests with both the dot reporter and coverage reports, if the coverage report fails there is no output (other than the dots) but the program exits with a failure status code. This is confusing - the user has no way to know why the command failed.

How

Added handling for the \ est:coverage\ event in the dot reporter (similar to how the spec reporter and TAP reporter already handle it). The dot reporter now yields the coverage report output when coverage data is available.

Testing

  • Existing dot reporter snapshot tests continue to pass (they don't use --experimental-test-coverage, so no coverage event is emitted)
  • Verified manually that spec and TAP reporters already show coverage output
  • CI will verify full test suite

@nodejs-github-bot
Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/test_runner

@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. test_runner Issues and PRs related to the test runner subsystem. labels May 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-ci PRs that need a full CI run. test_runner Issues and PRs related to the test runner subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

test_runner: print failed coverage reports with dot runner

2 participants