Running automation flows day and night - and in parallel is very handy when testing software on different operation systems and versions. LEAPWORK's Run List and Scheduler features enable you to manage this process easily. Find out how in this tutorial.
LEAPWORK contains two great features to help you get productive with unattended automation: Run Lists and the Scheduler.
In the video below, we’ll show you:
- How Run Lists and the Scheduler can be used to manage large amounts of test automation and RPA flows.
- How flows can be grouped together, scheduled and run on anything from a few to dozens or even hundreds of Agents on-premise or in the cloud.
If you are working with test automation, you can think of a Run List as a test suite. It’s a group of flows that should be run together.
If you are using LEAPWORK for robotic process automation, you can think of run lists as a way to control the order in which your robots run.
We’ll look at how to do that in various configurations, such as running flows in parallel in a specific or random order, using a “setup-run-teardown” pattern, and using conditions to control if certain steps are run or not.
The scheduler is a powerful tool for taking control over your automation as well as optimizing time and resources. You can define actions based on conditions – for instance, send an email when something fails, add scheduled variables that the individual flows can use and update, and manage queueing and error handling scenarios.
LEAPWORK even calculates estimated run times based on past performance of selected flows and Agents, which is handy for Agent allocation planning, something we will dive into with the Schedule Assistant for the Enterprise Edition of LEAPWORK in another video.
Once you've executed a set of automation flows, the natural next step is to report on the results. Check out the tutorial on Reports and Dashboards.
For more information about setting up Agents in LEAPWORK, please see this page in the documentation.
Please note: if you have used a version of LEAPWORK prior to our 2020.1 release, "Agents" were previously referred to as “Environments”.