[rust] Selenium-Manager fails when a browser detection fails with browser version (#11382)#11399
Merged
bonigarcia merged 1 commit intotrunkfrom Dec 12, 2022
Merged
Conversation
diemol
approved these changes
Dec 9, 2022
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.
Description
When a browser version is specified in Selenium Manager (using
--browser-version), for instance, an unstable version (e.g.,beta,dev, orcanary/nightly), instead of falling back to the latest driver, Selenium Manager should raise an error.Motivation and Context
This PR implements #11382.
Types of changes
Checklist