What happened?
Unlike other languages, .NET is doing the first part of the location outside of the "driver finder." So the Driver verification class is not distinguishing between the default behavior and what a user might be passing in.
If the user is passing in something incorrect, we need to raise an exception for that, rather than try to remediate it the way we would if the default isn't working.
Also, unlike other languages .NET has you specify the directory the driver is in, not the full path to the file itself. We may want to be more accommodating of this possibility by checking if it is a full path or if it is the directory.
How can we reproduce the issue?
var service = ChromeDriverService.CreateDefaultService();
service.DriverServicePath = "definitely/not/a/driver/path.exe";
driver = new ChromeDriver(service);
Relevant log output
oh .NET and logging...
Operating System
any
Selenium version
trunk
What are the browser(s) and version(s) where you see this issue?
any
What are the browser driver(s) and version(s) where you see this issue?
any
Are you using Selenium Grid?
no
What happened?
Unlike other languages, .NET is doing the first part of the location outside of the "driver finder." So the Driver verification class is not distinguishing between the default behavior and what a user might be passing in.
If the user is passing in something incorrect, we need to raise an exception for that, rather than try to remediate it the way we would if the default isn't working.
Also, unlike other languages .NET has you specify the directory the driver is in, not the full path to the file itself. We may want to be more accommodating of this possibility by checking if it is a full path or if it is the directory.
How can we reproduce the issue?
Relevant log output
oh .NET and logging...
Operating System
any
Selenium version
trunk
What are the browser(s) and version(s) where you see this issue?
any
What are the browser driver(s) and version(s) where you see this issue?
any
Are you using Selenium Grid?
no