-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
update (docs): note working with cypress #44958
base: master
Are you sure you want to change the base?
Conversation
NhutMinhIT
commented
Jan 7, 2025
•
edited
Loading
edited
- I have followed (at least) the PR section of the contributing guide.
Signed-off-by: Nguyen Nhut Minh <[email protected]>
Netlify deploy previewBundle size report |
Signed-off-by: Nguyen Nhut Minh <[email protected]>
@@ -205,6 +205,7 @@ If you use the ListSubheader directly, **no additional code is required**. | |||
To properly label your `Select` input you need an extra element with an `id` that contains a label. | |||
That `id` needs to match the `labelId` of the `Select`, for example: | |||
- Note: When working with `cypress testing`, this element is rendered in a different location in the DOM (possibly a virtual dom), you can use `id` to identify the test element. |
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.
This doesn't feel right to me, data-testid
should work for a simple Select
interaction with cypress, see #44939 (comment) @NhutMinhIT
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.
See https://github.com/mui/material-ui/issues?q=label%3A%22component%3A+select%22+label%3Atest+is%3Aclosed for historical guidance on how to test with Cypress