Quick Description

Neo offers the possibility to configure a driver path directly via properties using the property neodymium.webDriver.chrome.pathToDriverServer (or similiar for other browsers). Unfortunately this does not work.

Actual Behaviour

When I configure a driver in the properties file, neo is still taking the one from the path.

Expected Behaviour

When I configure a driver in the properties file, neo will take the one I configured.

Steps to reproduce

With a valid driver in path, set the property to an old or non existing driver path and start a test.

##Additional Info

For Chrome the issue is that we set chromeBuilder.usingDriverExecutable(new File(driverInPathPath)); in the BrowserRunnerHelper.java no matter what, we need to check if a driver is configured before doing so.
This is true for FireFox as well.

Please check for all supported browsers.