Open Castone22 opened 5 years ago
I think that sounds like a good plan of action.
Having it be manageable through the configs allows a user to still zero in on specific versions (maybe they're using the beta builds), while also allowing Oz itself to handle the webdriver versions overall.
Currently the way we manage driver versions is less than ideal.
I saw someone bring up using Titus' webdrivers gem to manage driver versions and honestly this might make the most sense, there's not a lot of reason to reinvent the wheel for something like this.
I am however convinced that we should create an interface for managing them using configs, and have ConfigurationEngine and BrowserEngine handle the actual interface with the webdrivers gem.
Any thoughts?