Test-More / Test-More/Test2-Harness
fast-fail mode?
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 28
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Might make sense to add a fast-fail mode, where the moment anything happens that makes the test fail, it is killed and reported as failure, not allowed to continue.
Why:
Often at work I find myself running the entire test suite just to get a list of what tests fail. Usually this is because of a new feature or big change. I mainly just want a count of failures, and will then run the tests one by 1 to figure out the issue and fix it. In this case having a failing test continue to stumble does not help, I do not need the extra debugging. In this case a fast-fail would save me a lot of time.
Maybe --fast-fail?
This should probably wait for the 'overlord' branch to be completed and merged, the implementation would be significantly simpler.
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 reviewing the overlord branch, which the issue identifies as a prerequisite for a simpler implementation. Then trace how the test suite currently continues after failures and determine where a --fast-fail option belongs. Done means the option stops execution at the first failure and reports the run as failed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- cli, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100