Chore: Reduce mobile note screen test flakiness #11145
Merged
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.
Summary
This pull request attempts to fix CI failures related to recent changes to mobile tests. These failures seem related to the recent switch to fake timers in
screens/Note.test.tsx
. This pull request attempts to enable fake timers only for the parts of the tests that relate to performance, while preventing test warnings that were previously resolved by switching to fake timers.Notes
act
(orwaitFor
, or certainreact-native-testing-library
queries) during testing,react-test-renderer
(used byreact-native-testing-library
) produces a warning. Several addedwaitFor
s andact
s are intended to prevent warnings related to background state changes.