using jest config to configure default timeout for integration tests #169
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.
As per suggestion by psteniusubi. But instead of adding "testTimeout" as a cli option, I think it is better to add it as a config. This should ensure it is picked up when running the tests from an IDE as well.
Note that there is actually an option for "testTimeout" that can be set in the config directly. But currently there is an issue with that (jestjs/jest#14513) and it does not look like it will be released in jest v29. When we upgrade, we can avoid the jest.setup.ts file.