Make sure you are comfortable with the following lessons:
Cloud runs can be triggered or scheduled at the Plan level, either on the Plans Page:
In the Plan Details Page:
Or set when creating/editing a Plan, which allows the User to select either by Deployment (via API or CI/CD), by scheduling the test to run on certain days of the week and at certain times (these options can be stacked, as shown in the video, so you can select Monday at 4:00AM and Wednesday at 1:00AM) or on a timer:
Scheduling Plans for certain days of the week allows you to run tests when you know your team will not be using the environment, enabling you to better manage your resources
Triggering Ad-hoc runs can be done either from the Test Details Page or in the Trainer. Please bear in mind that ad-hoc test runs are intended to provide a way to validate test edits without impacting overall stats, metrics, and insights - this means auto-heal will not impact any passing runs.
Triggering an Ad-hoc run from the page of the Test provides more options for how you’d like it to run:
Running tests from the Trainer enables you to get quick feedback on new or changed tests, ensuring your tests are working as expected without contributing toward your cloud run allotment. Here is how you can incorporate local runs into your workflow:
What did we learn?