nodejs/node

test_runner: print failed coverage reports with dot runner

Open

#60884 opened on Nov 28, 2025

View on GitHub
 (6 comments) (0 reactions) (0 assignees)JavaScript (117,218 stars) (35,535 forks)batch import
feature requestgood first issuetest_runner

Description

What is the problem this feature will solve?

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.

What is the feature you are proposing to solve the problem?

Similar to this PR, it would be nice to display some sort of failure reason so its clear why the command failed.

What alternatives have you considered?

No response

Contributor guide

Tech stack
nodejsjavascript
Domain
testingcli
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Node.js testingtest runnercoverage reportsdot reporter
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Review the test runner's coverage output handling, particularly the dot reporter. Reference PR #52655 for a similar change. Locate the relevant code in lib/internal/test runner/ and identify where coverage failures are reported. Then implement a failure message in the dot reporter's coverage end callback.