You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.
Unless I'm missing something, right now there is no way of using wdio-sauce-service with sauce connect unless the machine running the tests has Internet access and can reach saucelabs.com.
Even thought wdio-sauce-service can pass a proxy configuration to sauce-connect-launcher, so that the sauce-connect can reach saucelabs.com via a proxy, the code in suace-service.js that calls the Sauce REST API to update the test passed/failed metadata does not support using a proxy.
As a result, when running test on machine A with no Internet access, but configured to connect the SauceLabs via the Selenium Relay running as part of SauceConnect on machine B, the test is "completed" (all the steps are completed without error), but the test fails after 90 seconds, since wdio-sauce-service fail to update the test result via the REST API.
The text was updated successfully, but these errors were encountered:
@rveguilla thanks for filing the issue. Yes this is definitely and issue. Though it shouldn't be a problem to propagate the proxy information to the request call.
Unless I'm missing something, right now there is no way of using wdio-sauce-service with sauce connect unless the machine running the tests has Internet access and can reach saucelabs.com.
Even thought wdio-sauce-service can pass a proxy configuration to sauce-connect-launcher, so that the sauce-connect can reach saucelabs.com via a proxy, the code in suace-service.js that calls the Sauce REST API to update the test passed/failed metadata does not support using a proxy.
As a result, when running test on machine A with no Internet access, but configured to connect the SauceLabs via the Selenium Relay running as part of SauceConnect on machine B, the test is "completed" (all the steps are completed without error), but the test fails after 90 seconds, since wdio-sauce-service fail to update the test result via the REST API.
The text was updated successfully, but these errors were encountered: