search

webdriverio-boneyard / wdio-selenium-standalone-service

WebdriverIO v4 service to start & stop Selenium Standalone http://webdriver.io
MIT License
54 stars 28 forks source link

Cannot run the service behind corporate proxy #34

Open kukuruznik opened 6 years ago

kukuruznik commented 6 years ago

Our proxy rules ban AWS. As the service is starting it does an attempt to download the latest selenium drivers and fails. The startup fails even when there are already some downloaded binaries from previous runs (downloaded via direct Internet access).

Proposed solution: Make the download optional - e.g. don't reject the promise when the download fails and let Selenium run with an older driver (if exists).

If you accept such a solution I am willing to create a pull request with the change.

joshden commented 6 years ago

Might be good to have some kind of option to ignore failures or not even attempt downloading the latest drivers. If we make this the default behavior to not fail on such failures, it might lead to a download failure being unintentionally not noticed.

inspiraller commented 6 years ago

I had the same problem. I developed a workaround by downloading the selenium server java file and chromedriver manually, using gulp plus node run cmd package to run dual cmds, updating some arguments in capabalities, and removing the reference in wdio.conf which refers to services. Here is my solution: https://github.com/inspiraller/cucumber-boilerplate-behind-corporate-network