AssertionErrors should use process.stderr instead of console.log
Open
- Dominant language
- JavaScript
- Stars
- 1.9k
- Forks
- 359
- PR merge metrics
- No merged PRs in 30d
Description
Would be nice if I had the option to mute AssertionError traces by piping stderr elsewhere. I recommend a new reporter, maybe "default-pretty" and "default-verbose" which produce the same results but with the assertions errors going to stderr
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no file or test. Start by locating the reporter entry points and the current console.log handling for AssertionErrors, then run the existing test suite to understand output behavior. Done means the proposed reporter behavior preserves existing results while allowing assertion traces to be redirected through stderr.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100