-
Notifications
You must be signed in to change notification settings - Fork 401
Running Remote Tests in Parallel on Sauce
seb vincent edited this page Dec 24, 2013
·
1 revision
This is a list of points to be careful:
-
There might be jobs stuck in the queue, since you have a limited test slots, so you have to watch http timeout and retries, one long test might trigger http timeouts and mess up the test suite. This is a good formula to keep in mind: (num_of_jobs - num_of_slot) * max_job_length < http_timeout * retry
-
You might need to increase your test suite timeouts to take in account the wait above.
-
Session not shared between browsers
-
Test isolation
-
The server you are testing against, in particular if you are using sauce connect, the start/stop server takes much longer than with local test (This is more an issue related to remote than parallel, but will be more apparent).