Improved reporter experience
- Dominant language
- JavaScript
- Stars
- 20.8k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
By default it provides minimal output. We show a spinner and the status of the last test, so you get a sense of activity, and once an entire test file completes do we print failures. In verbose mode, we'd print the results of all tests & hooks, including logs. Various counts for passing and failing tests are always shown at the end of the output.
If a TTY is not available, we wouldn't print a spinner and only write the appropriate output for a test file once it completes.
We'd use [`ink`](https://www.npmjs.com/package/ink) to construct the output.
Contributor guide
Research direction
No files or tests are named. Start by reviewing the requested reporter behavior and the Ink dependency, then define the output for default and verbose modes, including per-file failures, logs, final counts, and TTY versus non-TTY behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100