Queue your tests over and above your parallel limit for running concurrent tests
Your Automate plan supports running the number of parallel tests that you have purchased (5 during free trial). But with test queueing, you can send more parallel test requests to BrowserStack than your plan limit.
The following are the salient points for queueing your tests:
With this feature, BrowserStack accounts with 1-5 parallels, can queue 5 tests. And, accounts with more than 5 parallels will have a max queue length equal to the number of parallels.
For example, if you have 2 parallel tests for your account, you can queue up to 5 more tests, but if you have 200 parallel tests, you can queue up to 200 more tests.
Queuing is enabled by default by BrowserStack to ensure you don’t have to worry about managing the test execution on your end. This helps especially in the following scenarios:
In a few rare cases, BrowserStack will automatically put your tests in a queue for a short period of time so your other tests can run first. This is usually done when the device, browser & OS configurations you want to run your test on has a long start-time delay (either because of peak usage or booting up time). This makes way for the next test which can be quickly run - thus reducing the overall time taken to run your tests. The previously queued test will be automatically dequeued and run whenever a slot becomes available.
You can also choose to manage the dispatching of tests at your end with/without utilising the queueing functionality. You can use the Plan API to find out the parallel sessions running, the max allowed sessions, queued sessions and max allowed queued sessions for your plan and dispatch tests accordingly.
Contact our Support team for immediate help while we work on improving our docs.