rtfeldman / rtfeldman/node-test-runner
Print statistics/progress on signal SIGUSR1 (Linux) / SIGINFO (macOS)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 140
- Forks
- 83
- Avg merge
- 8h 25m
- Merged PRs (30d)
- 5
Description
There's this idea of printing out progress to the user if a signal is sent to the running process (eg. with Ctrl+T on macOS or with kill -USR1 $PID on Linux)
For long-running elm-test instances, it might be nice to be able to get some progress info (eg. which tests are still running, how many fuzz iterations are left for each, how many failures has it already found, ...) mid-run.
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
The issue names no files, tests, or entry points. Start by locating the long-running elm-test execution path and existing command-line output, then investigate how process signals can be handled on Linux and macOS. Done means a running test process reports useful progress when the requested signal is sent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, linux, macos
- 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