Change timeout for React Component test from 5s to 15s #1103
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jiji14
changed the title
|
Merging this as a workaround. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change timeout for React Component test from 5s to 15s
Why the test fails on GitHub Actions Environment
The test fails with the message
Exceeded timeout of 5000 ms for a testin the GitHub Actions environment. In Jest, the default test timeout is 5 seconds, which might be too short for React component testing. I guess this could happen in component tests where we trigger actions, render components, and check if the component exists or if the function gets called.What is changed to fix this issue
During our regular meeting, we reached an agreement to extend the timeout from 5 seconds to 15 seconds.
We will further discuss how to handle this issue, especially considering that as we write more component tests, this issue may arise again.
For more details, refer to Jest documentation.