Skip to content
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.

Multiremote with wdio-sauce-service #50

Open
adrian-brown opened this issue Apr 13, 2018 · 5 comments
Open

Multiremote with wdio-sauce-service #50

adrian-brown opened this issue Apr 13, 2018 · 5 comments

Comments

@adrian-brown
Copy link

Hi,

I'm using wdio-sauce-service with remote and it works great with single instance tests, whoever with multiremote shows jobs in saucelabs where we have two browers running in parallel. When the job completes the status in saucelabs is unknown when Passed or Failed would have been expected. Does this work with multiremote, any example config (if relevant?)

Thanks 👍

Environment
wdio-sauce-service 0.4.7
wdio 4.8.0
sauce connect is used via HA setup so no sauceConnect used via the plugin

@christian-bromann
Copy link
Contributor

@adrian-brown we don't have support for multiremote. Happy to see this being implemented though.

@adrian-brown
Copy link
Author

Ah cool thanks for letting me know.

@brownad
Copy link

brownad commented Apr 29, 2018

would that also resolve the experience in saucelabs where many multiremote tests use the same running sauce VM at the moment causing a timeout eventually (I set 30 mins). Locally I get new instances of 2 chrome instances per multiremote test. I run the tests from wdio runner so don’t see how I can force new browser sessions for multiremote tests. Or is there a way?

@adrian-brown
Copy link
Author

Any chance this could be taken up, or is this a very isolated problem not shared by the masses? Using sauce in this way would be a big win vs running on an isolated container

@christian-bromann
Copy link
Contributor

@adrian-brown feel free to provide a PR

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants