Use named factory methods for WinAppDriver and its Capabilities. #91
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
tristanlabelle
changed the title
jeffdav
approved these changes
Sep 11, 2023
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.
Overloading initializers was not as clear and required putting the verb in the label of the first argument, which would not have worked for
WinAppDriver.Capabilities.attachToDesktopsince it takes no arguments. I think it's useful to distinguish between different operations clearly.Also factored the different places where we use
ProcessInfoto figure out standard windows paths into aWindowsSystemPathstype. This could eventually useSHGetKnownFolderPathinstead of environment variables.Fixes #81