-
-
Notifications
You must be signed in to change notification settings - Fork 33.5k
Closed
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.regressionIssues related to regressions.Issues related to regressions.test_runnerIssues and PRs related to the test runner subsystem.Issues and PRs related to the test runner subsystem.v22.xIssues that can be reproduced on v22.x or PRs targeting the v22.x-staging branch.Issues that can be reproduced on v22.x or PRs targeting the v22.x-staging branch.
Description
Version
22.8.0
Platform
arwin MBP-AJ-2023.local 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:04 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6020 arm64
Subsystem
No response
What steps will reproduce the bug?
Create an empty repro.test.js
file.
Run:
node --test-reporter=dot --test repro.test.js
=> the terminal clears
Whereas it doesn't, when --test-reporter=dot
is not provided.
Both cases were working fine with Node v22.5.1.
How often does it reproduce? Is there a required condition?
Systematically.
What is the expected behavior? Why is that the expected behavior?
The terminal should not clear, so the test results and stdout from previous commands remain on screen.
What do you see instead?
Blank terminal window.
Additional information
No response
pmarchini and avivkeller
Metadata
Metadata
Assignees
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.regressionIssues related to regressions.Issues related to regressions.test_runnerIssues and PRs related to the test runner subsystem.Issues and PRs related to the test runner subsystem.v22.xIssues that can be reproduced on v22.x or PRs targeting the v22.x-staging branch.Issues that can be reproduced on v22.x or PRs targeting the v22.x-staging branch.