rtfeldman / rtfeldman/node-test-runner
UI Indicating Progress of the test run (or that it's working at all)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 140
- Forks
- 83
- Avg merge
- 8h 25m
- Merged PRs (30d)
- 5
Description
2 Helpful reasons for output
Psychological
With large amounts of test files, running tests can take long (in problematic case we spoke of in particular, 68717 ms). During this time, it doesn't feel very good as the developer to watch nothing happen on the screen.
Helpful
In the case that you won't take the next action until all tests pass (like commit or push), it's useful to know as soon as possible when tests break. In the current state, we don't know until the end if there are any test breaks- but it would be very helpful to see them as they come out so as a developer I can either:
- End early
- Start fixing tests as others run
@stoeffel may have additional cases
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reproducing a long test run and tracing how its output is emitted; done should mean that progress is visible and test failures appear as they occur, with enough detail to stop early or begin fixes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100