rtfeldman / rtfeldman/node-test-runner
Better support for long running tests
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 140
- Forks
- 83
- Avg merge
- 8h 25m
- Merged PRs (30d)
- 5
Description
This is somewhat similar to #169.
Long running tests could do with an ETA estimate of how long they are going to take. This is particularly the case when running with large --fuzz values, as the test time is relatively predictable (anecdote: running my test suite with --fuzz 10000 took 11,462ms; running it with --fuzz 1000000 took 1,214,796 ms, so a 100x increase in fuzz resulted in 105x increase in time, so this is pretty much linear).
The other thing is relatively minor, but showing elapsed time in ms is pretty... er... optimistic. Also difficult to read - Duration: 1214796 ms. Much easier would be Duration: 20 m 14 s.
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
Start by tracing how long-running tests and the --fuzz option report progress and duration in the test runner. Determine how an ETA could be calculated and how elapsed durations should be formatted; done means long fuzz runs show a useful estimate and readable units.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100