Refactor: Add current_path to 'Driver' protocol #89
Conversation
This file contains 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
ftes
force-pushed
the
refactor/add-current-path-to-driver-protocol
branch
from
c4bd730 to
4f3ae09
Compare
Closed
|
Thanks @ftes! |
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.
Extracted from #74
Goal
Support
assert_pathimplementations for browser-basedDriverimplementationsBackground
Browser-based tests have a decoupled state. It may be necessary to retry/await until the path is updated in the browser.
To support this, the
Driverimplementation should be allowed to choose how to fetch thecurrent_pathand not be forced to store it as a struct entry.