You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we know beforeAll/afterAll is typically used to setup/teardown resources for a test suite.
But currently if beforeAll is aborted by errors then afterAll won't be called, so that we can't surely cleanup resources that are prepared in the beforeAll.
Suggested solution
I think it is better if there's a way to wrap an entire test suite with one hook, so to speak, aroundAll().
But currently if beforeAll is aborted by errors then afterAll won't be called, so that we can't surely cleanup resources that are prepared in the beforeAll.
This is a bug. afterEach is called, if beforeEach failed. The same should apply to beforeAll/afterAll.
Clear and concise description of the problem
As we know beforeAll/afterAll is typically used to setup/teardown resources for a test suite.
But currently if beforeAll is aborted by errors then afterAll won't be called, so that we can't surely cleanup resources that are prepared in the beforeAll.
Suggested solution
I think it is better if there's a way to wrap an entire test suite with one hook, so to speak, aroundAll().
aroundEach is may also useful.
Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: