Chimpy doesn't appear to support Sauce Connect (which is required for testing non-public apps via Sauce Labs) #132
Description
I was able to get Chimpy to connect to Sauce Labs with host=ondemand.saucelabs.com and port=80 and run tests. However, since the application I'm testing is not publicly available (which I'm assuming is the normal use case since it's a little late to test after deploying), I need to use the Sauce Connect proxy/tunnel so that Sauce Labs can reach our internal network to test the app.
The problem is that using Sauce Connect requires setting host=localhost and port=4445 in Chimpy config however Chimpy requires host=ondemand.saucelabs.com in order to use Sauce Labs, otherwise the code in src/lib/session-factory.js will not create a SauceLabsSessionManager.
I've tried changing that code in src/lib/session-factory.js so that it creates a SauceLabsSessionManager for host=localhost and port=4445, but it appears that the issue is more complex than this since I see my local Chrome browser pop up (which should no happen if using Sauce Labs) long before the code in session-factory.js is even run and the tests are still failing with a browser screenshot showing an empty page upon timeout.
Has anyone else been able to get Chimpy working with Sauce Connect tunnel? Is there some magic command/config param to tell Chimpy to use the tunnel? :)
PS. I've created a simple test that only uses only Webdriver.io + Sauce Connect + my localhost Meteor app (ie. no Chimp) and was able to get the test working. So I know that there's no networking issues, etc preventing the tests from running.
- Chimp version: 0.51.1
- Node.js: 6.11.4
- Java: 1.8.0_66
- Operation system: Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64
Join our Slack xolv.io/community #chimp channel, where you can find help and help others.