Skip to content

test_runner: print failed coverage reports with dot runner#62078

Open
mizoz wants to merge 1 commit intonodejs:mainfrom
mizoz:test-runner-coverage-fix
Open

test_runner: print failed coverage reports with dot runner#62078
mizoz wants to merge 1 commit intonodejs:mainfrom
mizoz:test-runner-coverage-fix

Conversation

@mizoz
Copy link

@mizoz mizoz commented Mar 2, 2026

Fixes #60884

Summary

When running tests with both the dot reporter and coverage reports, if the coverage report fails there was no output (other than the dots) but the program exits with a failure status code.

This change adds coverage failure output to the dot reporter, similar to how the spec reporter handles coverage events. Now users can see why the command failed without needing to check F12 console.

Changes

  • Import getCoverageReport from reporter utils
  • Track coverage events in dot reporter
  • Print coverage failures at the end of test output

Testing

  • Code follows project guidelines
  • Self-review completed
  • Commits are signed

@nodejs-github-bot
Copy link
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 Mar 2, 2026
When running tests with both the dot reporter and coverage reports,
if the coverage report fails there was no output (other than the dots)
but the program exits with a failure status code.

This change adds coverage failure output to the dot reporter, similar
to how the spec reporter handles coverage events. Now users can see
why the command failed without needing to check F12 console.

Fixes nodejs#60884

Signed-off-by: AZ & QZ <dev@local>
@mizoz mizoz force-pushed the test-runner-coverage-fix branch from d71eee3 to d0f8b20 Compare March 10, 2026 13:11
@mizoz
Copy link
Author

mizoz commented Mar 10, 2026

👋 Hi! I've rebased this PR on the latest main branch. The rebase was successful with no conflicts.

CI checks are now pending and should start automatically. Once they complete, the PR should be ready for review by @nodejs/test_runner.

Thanks!

@JakobJingleheimer JakobJingleheimer added the duplicate Issues and PRs that are duplicates of other issues or PRs. label Mar 10, 2026
@JakobJingleheimer
Copy link
Member

Duplicate of #61423

@JakobJingleheimer JakobJingleheimer marked this as a duplicate of #61423 Mar 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

duplicate Issues and PRs that are duplicates of other issues or PRs. 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

3 participants