Not calling test.done() will also cause test to be finished "improperly"?
Open
- Dominant language
- JavaScript
- Stars
- 1.9k
- Forks
- 359
- PR merge metrics
- No merged PRs in 30d
Description
Please refer to the full thread on http://stackoverflow.com/questions/9370617/possible-to-tell-nodeunit-not-to-finish-a-particular-test-until-test-done-is-c
Why does test end without test.done() from being invoked?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked Stack Overflow thread, then trace nodeunit's test completion behavior to reproduce what happens when test.done() is omitted. The issue names no repository files or tests; done means establishing whether this behavior is intentional and identifying the relevant completion logic or test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100