Feature: exit nodeunit on first failed test
- Dominant language
- JavaScript
- Stars
- 1.9k
- Forks
- 359
- PR merge metrics
- No merged PRs in 30d
Description
For me this is a huge issue: I have, not that unexpectedly, thousands of assertions going on in my tests, and so if I change something, this might trigger dozens or even hundreds of them to fail. This is becoming very annoying to handle with nodeunit, because I have to scroll back up through all that "junk" to find out what was the first test that failed and is most likely the root cause. If nodeunit would just have an option to quit right away on the first failed test, testing would be far faster and it would be more easy to use ":! nodeunit test" in vim :).
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating nodeunit's command-line option handling and test-runner flow, then determine where a first failed assertion can stop execution. Done means an explicit option causes nodeunit to quit on the first failed test, including when invoked from the CLI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100