Improve UX for hanging tests

[mkcode]

Summary:

If a test does not exit after completing, that usually indicates that some async resource is not properly waited for or cleaned up. Jest ships with a --detect-open-handles CLI flag to help locate this, but it doesn’t work in all case. This project would explore how this detection could be made smarter so people spend less time trying to fix their tests.

• Issue: Detect infinite loops and stop tests jestjs/jest#9785
• Work in progress PR: fix: improve open handles detection · Issue fix: improve open handles detection jestjs/jest#9532 · facebook/jest

Level of complexity: Medium

Experience wanted:

• JavaScript
• Jest testing framework

Deliverables:

• Fixing the reported cases in Jest’s issue tracker where --detect-open-handles doesn’t work properly

[mkcode]

We will not be completing this task during the fellowship

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.