Repository navigation
test_runner: add timeout for tests #43490
Copy link
Copy link
Closed
Labels
feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.test_runnerIssues and PRs related to the test runner subsystem.Issues and PRs related to the test runner subsystem.
Description
Activity
- addedfeature requestIssues requesting new Node.js features.Issues requesting new Node.js features.
on Jun 19, 2022 CC @benjamingr Please ping relevant people and add a label?
- addedtest_runnerIssues and PRs related to the test runner subsystem.Issues and PRs related to the test runner subsystem.
on Jun 19, 2022 @nodejs/test_runner
Yes, this is a good idea and I am in favor. Is this something you'd like to work on?
Yes, this is a good idea and I am in favor. Is this something you'd like to work on?
Yes, assuming no objections
Reacted by Benjamin GruenbaumNo objections - this is something we should definitely support.
Reacted by Moshe Atlow, Jordan Harband, Benjamin Gruenbaum and Erick Wendel- added a commit that references this issue
on Jul 14, 2022 - added 2 commits that reference this issue
on Jul 15, 2022 - added a commit that references this issue
on Jul 20, 2022 - added a commit that references this issue
on Jul 26, 2022 - added a commit that references this issue
on Jul 31, 2022 - added a commit that references this issue
on Oct 10, 2022 Has this been implemented?
Yeah there is a timeout parameter now check the test runner docs. @bitflower
Thanks for the feedback @benjamingr ! Sorry to not report back. I had found it in the meantime (it's different to e.g.
mocha).Reacted by Benjamin Gruenbaum
Metadata
Metadata
Assignees
Labels
feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.test_runnerIssues and PRs related to the test runner subsystem.Issues and PRs related to the test runner subsystem.
What is the problem this feature will solve?
currently - tests can easily be stuck or never end, which makes it very hard to understand and locate where your problem might originate
for example, this program will be very hard to debug:
What is the feature you are proposing to solve the problem?
add a timeout to tests running via
node:test, I propose adding a default timeout that will be configurableone of the most important parts of testing is failing fast and knowing what the failure is, and timing out will help determine which test is misfunctioning
What alternatives have you considered?
No response