-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(refactor) Set global testTimeout in Jest config #1573
Conversation
Size Change: -110 B (0%) Total Size: 10.3 MB ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like the highest value that's being replaced here is 20000, so maybe we could try that?
Since Jest is used for unit tests, anything that's taking longer than 5000ms, IMO is either a broken test (i.e., it's executing more code than it should) or indicates that the production code is way to slow (I guess it's also possible that it means that too many tests are being executed in parallel).
It also seems to work perfectly with 10000ms. |
e039493
to
94f3bca
Compare
Thanks for the suggestions. I'm inclined to try out a |
* (refactor) Set global testTimeout in Jest config * Commit some orphaned translations * Lower global timeout to 20000ms
Requirements
Summary
This PR removes test timeouts from individual tests and moves them up into the global Jest config as a single
testTimeout
property whose value is set to20000ms
. Hopefully this tackles the issue where tests time out non-deterministically.20000ms seems like a reasonable value, though it'd be worthwhile trying to lower this figure down as we move along so we strike a good balance with a value that's not too low to prematurely terminate valid long-running tests, and not too high to unnecessarily prolong the feedback loop for test failures.
Screenshots
None
Related Issue
None
Other
None