Add documentation#72
Conversation
- Concurrency - BROWSERSTACK_NO_LOCAL variable
|
@veewee, thank you for your contribution! The However, it seems that the first part of the The part about exceeding the parallel test limit is important, but this information relates not only to concurrent test runs. So I would put it in a separate section: Exceeding the Parallel Test LimitWhen you run tests in multiple browsers or concurrently, you may exceed the maximum number of parallel tests available for your account. Assume your plan allows 2 parallel tests and you run one of the following commands: testcafe 'browserstack:ie@11.0:Windows 10' 'browserstack:chrome@59.0:Windows 10' 'browserstack:safari@9.1:OS X El Capitan' tests/acceptance/testcafe browserstack:ie@11.0:Windows 10 -c3 tests/acceptance/In this instance, BrowserStack will refuse to provide all the required machines and TestCafe will throw an error: To keep within your account limitations, you can run tests sequentially (or in batches), like in the following bash script (credits to @maoberlehner for this example): browsers=( "browserstack:ie@10.0:Windows 8" "browserstack:ie@11.0:Windows 10" "browserstack:edge@15.0:Windows 10" "browserstack:edge@14.0:Windows 10" "browserstack:firefox@54.0:Windows 10" "browserstack:firefox@55.0:Windows 10" "browserstack:chrome@59.0:Windows 10" "browserstack:chrome@60.0:Windows 10" "browserstack:opera@46.0:Windows 10" "browserstack:opera@47.0:Windows 10" "browserstack:safari@9.1:OS X El Capitan" "browserstack:safari@10.1:OS X Sierra" )
for i in "${browsers[@]}"
do
./node_modules/.bin/testcafe "${i}" tests/acceptance/
done |
This PR adds documentation about:
It took me a while to find the related issues so that I could solve this:
testcafewith a lot of browsers crashes BrowserStack #18However, it would be cleaner if this provider uses the
BROWSERSTACK_PARALLEL_RUNSconstant to handles the testcafe concurrency + browserstack session management as well.Currently browserstacks keeps stacking queued sessions when the testcafe remote session timeout is hit. These can be hard to kill in the browserstack GUI and are blocking a next test run as well.