Include roles from shadowDOM in Error message#999
Open
kilmc wants to merge 2 commits intotesting-library:mainfrom
Open
Include roles from shadowDOM in Error message#999kilmc wants to merge 2 commits intotesting-library:mainfrom
kilmc wants to merge 2 commits intotesting-library:mainfrom
Conversation
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 2cc2867:
|
Author
|
Is there anything I can do to move this along, even if it's going to be rejected? |
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What:
Adds a check which improves Error messages for folks testing Web Components using
getByRole.Note: This PR is focused on getting a correct Error message and not a passing test. This fix will be most useful to folks using
dom-testing-libraryin conjunction with the wrapper library referenced in this comment in #413.Why:
When testing Web Components the returned error is incorrect. The example below walks you through this case.
Contents of the shadowDOM for
<custom-button>Below is a test assertion with a minor typo in it.
Before the change in this PR the error message returned is:
After the change the error becomes:
How:
Adds a check for
node.shadowRootinflattenDomto ensurechildreninside of Web Components are traversed.Checklist:
docs site N/A