Managing tests with Low Code Automation
Organize your tests and schedule executions for regression testing.
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 page, we describe how you can create test suites and schedule them without the burden of complex manual configurations.
Creating a Test Suite
With Low Code Automation, you can create a test suite using both desktop as well as web application. Follow these steps to create a test suite:
- Go to the Test Suites section on your web or desktop application.
- Click Create test suite.
- Provide name & description of your test suite.
- Select the desired device profile (Desktop or Mobile/Tablet).
- For Desktop, you are provided with the options to select Chrome, Edge, Firefox and Safari under the Execution browsers.
- When running tests on Mobile/Tablet, you have the option to choose between an Emulated device or a Real device under Run tests on.
- For Desktop, you are provided with the options to select Chrome, Edge, Firefox and Safari under the Execution browsers.
- Click Add test(s) to select tests from the list of recorded tests and click Proceed.
You can also filter tests based on tags to quickly select relevant tests. - On the Step 2: Additional configuration window, configure Schedule, Time, local testing, and Host URL and save your test suite. Refer to Test suite configuration for more information.
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 |
Related topic
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!