This repository was archived by the owner on Jul 29, 2024. It is now read-only.
fix(element chaining): make element chaining work when the control fl… #4029
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.
…ow is disabled
Also added some tests to
spec/ts/noCF/smoke_spec.ts
double checking that the control flow is off@juliemr I know we talked offline and said it'd be best not to mess with
getWebElement
and have chaining only work on value. But given functions likeisElementPresent
andequals
andcount
, it seems like there are going to be a lot of edge cases on that route and no clear dividing line on which functions should work and which shouldn't. This implementation is relatively clean, and should be very rigorously tested by our suite. So let me know.