-
Notifications
You must be signed in to change notification settings - Fork 141
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
support for @testing-library/react with Select #118
Labels
help wanted
Extra attention is needed
Comments
|
in tests i typically mock all material ui components. do you have a reason for not doing so here? it is much easier just to replace all material ui inputs with native html tags. i think you can trust material-ui's internal unit tests to verify that a select input works the way it's supposed to. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am having trouble triggering the
onChange
orsetValues
when dispatching a change event when using aSelect
. Would you be able to provide an example for this? I have a suspicion this might be a bug.Here is what I have been trying:
This works for basic fields like
TextField
but I think some of theonChange
shims might be interfering the dispatched change event forSelect
.The
values
prop in theFormik
render scope never updates if the input is from theSelect
, however immediately updates if it's aTextField
.The text was updated successfully, but these errors were encountered: