-
Notifications
You must be signed in to change notification settings - Fork 273
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
chore: update react-native to 0.69.1 #1010
Conversation
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.
Can we make sure the examples are upgraded as well? It's cool to make it separate though
jest.useFakeTimers(fakeTimerType); | ||
const { getByText, queryByText } = render(<BananaContainer />); | ||
test('waits for element until it stops throwing using modern fake timers', async () => { | ||
jest.useFakeTimers('modern'); |
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.
We could wait for Jest 28 PR to be merged first
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.
So the test works, it just needs to be using two separate test
entries instead of one test.each
entries.
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.
In my testing the test worked fine when each
cause had only one of modern
and legacy
entries, but failed when there were both of them. I have a feeling that his is somehow connected to after test cleanup since splitting tests helped.
@thymikee maybe it make more sense to you as you know more about Jest internals.
2201858
to
e4fcbf4
Compare
Summary
Support for React Native 0.69.1.
Resolves #998
Test plan
All checks and tests pass.