-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
WIP: enzyme click bug #48
WIP: enzyme click bug #48
Conversation
@marcelomorgado This is all great info. Thanks for looking into this! If we publish a new version of the SDK with the sync version of |
Yes, It'll should work. |
@marcelomorgado If I recall correctly, we're keeping this open until we publish a new version of the SDK and then potentially merging it. Is that right? |
No, not really, This PR isn't to be merged. It's for doc only. I was going to share this on Enzyme/React-native issues but it wasn't necessary. There are three issues related with tests until now:
The issue related with Expo SDK is that: #12 (comment) (Snapshot)
Ref: https://blog.expo.io/expo-sdk-v32-0-0-is-now-available-6b78f92a6c52
After creation of remain issues I think we could close this PR without merge. |
Thanks for the status update. That all makes sense. Thanks! |
Refs: #12 (comment)
I've looked deeply about this issue and Enzyme team will not make "simulate" as an async function. Reasons: here, here and here.
Since calling a component function isn't ideal because the test shouldn't be aware of component internal behavior, I've found a trick to turn around that:
They are working on new function called invoke that will do the same as above: