Replies: 1 comment
-
Just updated the link to stackblitz. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Version Number
7.55
Codesandbox/Expo snack
https://stackblitz.com/edit/sb1-qxv9vybk?file=index.html
Steps to reproduce
If I run the code where it has the useForm and my component is directly there, when I assert, it works fine. But when I have a context and I wrap my test around the context, If I have a setValue due to a condition (I used a setValue without conditions, but in real code I have a condition for it to setValue, but the outcome is the same) even waiting for the value to be there, it is never there. Although locally while running my code, it sets correctly, only on the test environment it does not work.
I've been using findBy and waitFor to wait for value to be set, but I always get timeout. If you run the app.test code it works, but the form.test does not.
Expected behaviour
I should be able to assert the information was changed even if I have my component wrapped on a formProvider.
What browsers are you seeing the problem on?
No response
Relevant log output
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions