Customize your Browser Automation Grid

With BrowserStack’s Automate TurboScale, you can customize the resources. timeouts or different parameters of a browser automation grid as per your testing requirements.

With a simple but powerful UI console, you can customize the grid with the following capabilities.

Grid Concurrency

With Grid Concurrency settings, you have the flexibility to configure the number of concurrent browser tests you can run. By default, when the new grid is created, it supports a concurrency of 50. From Automation Console, select the particular grid and update this setting as per your testing scale from the Settings tab.

Browser Resources

Now manage the resources behind the browser instances spawned for running a test. Use this configuration if your websites or tests require higher CPU/Memory behind the browser instances. If the tests are lighter on resources, you can reduce the resources to reduce the overall Grid utilization and optimize the infrastructure utilization for running your automation.

Configure Browsers

Now manage the browsers supported on this particular Grid. By default, this Grid supports all browsers. Use this option to restrict test sessions on a specific browser(s). Use this option when the resource consumption behind the browsers varies according to different browsers, and you need to control the resources getting utilized behind the Grid.

Configure different Timeouts

Set up different test-level timeouts as per your testing requirement.

Idle Timeout

Whenever a test session is executed, Grid marks the test as inactive if there is inactivity between the commands and stops the session with the Selenium server. This is required for Grid to ensure it handles the tests appropriately if there is a connectivity issue between the client and the Grid. Grid waits for a certain amount of time before timing out the test. This waiting period is called idle timeout. You can configure this idle timeout for a particular Grid.

Queue Timeout

Whenever a test session is queued due to insufficient resources or any internal reason, Grid retries the test request for a certain amount of duration before dropping the test and sending an error message to your test-suite client. This duration is called Queue Timeout. You can configure this queue timeout for a particular Grid.

Queue Retry Interval

Whenever a test session is queued due to insufficient resources or any internal reason, Grid retries the test request for a certain amount of duration before dropping the test. The grid retries a test waiting in the queue after a certain time interval. You can configure this interval for a particular Grid.

Test Timeout

Whenever a test session is executed, Grid stops accepting the commands after a certain test duration. This is required for Grid to ensure the test isn’t running forever. You can configure this test timeout for a particular Grid.

Configure Test Artifacts

Now manage the test artifacts generated on a particular Grid. By default, all the logs like video, and framework logs are enabled by default on this Grid and are retained for 7 days. Use this option to restrict particular test artifacts being generated or tune the duration for logs retention as per your testing or compliance needs.