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
Based on our experience, it seems that Jest's bail option only takes effect when multiple test files are running. In our case, all of our tests are contained within a single test file. This setup is intentional because:
All tests share the same canisters on the same replica, and splitting them into multiple files could introduce race conditions.
Many of our tests depend on state created or modified by earlier tests, making it logical to group them in one file.
Unfortunately, this also means there's no way to abort the entire test suite early if one of the initial tests fails, which limits the usefulness of bail in our current setup.
We plan to conduct further research to confirm this behavior and explore potential solutions, but now isn’t the right time to address this comprehensively. For now, this is an important consideration for any plans involving bail in our Jest configuration.
No description provided.
The text was updated successfully, but these errors were encountered: