The issue involves extending existing test runner functionality with a clear pattern to follow.
The issue involves improving the test runner to display coverage failure reasons when using the dot reporter. The contributor plans to follow the pattern established in a previous PR (#52655) to implement this feature. There are no apparent blockers, and the scope is well-defined.
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.
Similar to this PR, it would be nice to display some sort of failure reason so its clear why the command failed.
No response
Claim this issue to let others know you're working on it. You'll earn 10 points when you complete it!