We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A previous PR added some jest-dom inspired assertions like toHaveAccessibleDescription #18332.
toHaveAccessibleDescription
A very good additional would be to also match toHaveAccessibleErrorMessage https://github.com/testing-library/jest-dom#tohaveaccessibleerrormessage
toHaveAccessibleErrorMessage
This allows you to assert that an element has the expected accessible error message.
await component.getByLabel('An input').fill('incorrect value'); await expect(component.getByLabel('An input'). toHaveAccessibleErrorMessage('You have entered invalid text');
At the moment to accomplish the same thing multiple assertions need to be made to test this common a11y patterns.
Playwright should aim to provide a first-class experience for testing a11y
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
🚀 Feature Request
A previous PR added some jest-dom inspired assertions like
toHaveAccessibleDescription
#18332.A very good additional would be to also match
toHaveAccessibleErrorMessage
https://github.com/testing-library/jest-dom#tohaveaccessibleerrormessageThis allows you to assert that an element has the expected accessible error message.
Example
Motivation
At the moment to accomplish the same thing multiple assertions need to be made to test this common a11y patterns.
Playwright should aim to provide a first-class experience for testing a11y
The text was updated successfully, but these errors were encountered: