Print test failures on INFO signal
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 117
- Forks
- 51
- Avg merge
- 59m
- Merged PRs (30d)
- 3
Description
Hi,
One thing I miss from minitest is if I have a slow test suite, and there is a failure, I can hit Ctrl-T to send a SIGINFO and it will print out the current failures with a stack trace. Then I can decide if I want to kill the process and fix those or just let it go.
I made a video to demonstrate.
I will try to make a PR for this, but I wanted to file a ticket a) so I don't forget, and b) in case someone can get to it before me.
Thanks!
Contributor guide
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 reviewing the test runner's handling of SIGINFO and how it records failures during a slow suite. The change is done when sending Ctrl-T prints current failures with stack traces without stopping the test process; the issue provides no file or test names to begin from.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100