Introduction
Group tests and configure to run on multiple environments easily.
Test Suite helps you group and manage tests, and also configure them to execute on multiple environments before every release. In this guide, we will cover how to create test suites and schedule them without the burden of complex manual configurations.
Creating a Test Suite
With Low Code Automation, creating a test suite can be achieved using both desktop as well as web application. Follow these steps to create a test suite:
- Navigate to Test Suites section from your web or desktop application.
- Click on Create test suite button.
- Provide name & description.
- Select tests from the list of recorded tests.
- Configure Scheduler and Host URL and create your test suite. Follow Test suite configuration for more info around this.
Configuring Test Suite
Configure your test suite to run multiple times in the week across different environments.
Scheduler
Scheduler automates the execution of test suites at predefined times and frequencies without any extra configuration. You can simply choose the days of the week and the desired execution time for your test suite. Low Code Automation automatically triggers the execution on BrowserStack cloud infrastructure when the scheduled time arrives.
Host URL
Host URL allows you to run tests on multiple environments with ease. This is achieved by providing the base URL of the environment where you want to run the test suite on. During execution, the base URL for all the tests within the test suite would be overriden with this Host URL.
Refer the table below to understand how the Host URL gets overriden for different cases.
Recorded Test URL | Test Suite Host URL | URL during Execution |
---|---|---|
staging.example.com | preprod.example.com | preprod.example.com |
staging.example.com | preprod.example.com:3000 | preprod.example.com:3000 |
staging.example.com:3000 | preprod.example.com | preprod.example.com |
staging.example.com:3000 | preprod.example.com:3000 | preprod.example.com:3000 |
staging.example.com/pricing | preprod.example.com | preprod.example.com/pricing |
staging.example.com/pricing | preprod.example.com:3000 | preprod.example.com:3000/pricing |
staging.example.com:3000/pricing | preprod.example.com | preprod.example.com/pricing |
staging.example.com:3000/pricing | preprod.example.com:3000 | preprod.example.com:3000/pricing |
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!