feat: support assertView calls on any valid webdriver element#1293
Merged
Conversation
…browser-side logic to work with element references
commit: |
✅ Testplane E2E run succeed
|
✅ Testplane browser-env run succeed
|
sipayRT
approved these changes
Jul 16, 2026
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
2 participants
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's done?
The idea:
element.selectorin assertView and then tried to find element using this selector>>>.lable(for shadow dom),div*=Some text(for webdriverio-style text based selectors) or testing-library selectorsOn client side, I've also migrated all places that were quering page for elements to use single lib.query* methods, that support xpath selectors.