Skip to content

test_runner: print failed coverage reports with dot runner - #62078

Closed
mizoz wants to merge 1 commit into
nodejs:mainfrom
mizoz:test-runner-coverage-fix
Closed

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

Conversation

@mizoz

@mizozmizoz commented Mar 2, 2026

Copy link
Copy Markdown

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
Copy Markdown
Collaborator

Review requested:

  • @nodejs/test_runner

@nodejs-github-botnodejs-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.
Fixesnodejs#60884
Signed-off-by: AZ & QZ <dev@local>
@mizoz
mizozforce-pushed the test-runner-coverage-fix branch from d71eee3 to d0f8b20CompareMarch 10, 2026 13:11
@mizoz

Copy link
Copy Markdown
Author

👋 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!

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

Copy link
Copy Markdown
Member

Duplicate of#61423

@JakobJingleheimerJakobJingleheimer marked this as a duplicate of #61423Mar 10, 2026
@mizoz

Copy link
Copy Markdown
Author

Closing this since it duplicates #61423. Thanks for pointing that out.

@mizozmizoz closed this Apr 28, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

duplicateIssues and PRs that are duplicates of other issues or PRs.needs-ciPRs that need a full CI run.test_runnerIssues 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

@mizoz@nodejs-github-bot@JakobJingleheimer