Running automation flows day and night - and in parallel is very handy when testing software on different operation systems and versions. Learn to schedule the execution of automated tests and processes on machines and devices dedicated to this purpose.
The LEAPWORK Automation Platform is made up of three components:
- Studio is a powerful, visual designer that can be used by anyone in your organization to easily design automation flows, set up schedules to run automation flows on physical or virtual machines and in the cloud, and dig into the results with dashboards and reports.
- The Controller handles how, when, and where automation flows are run. It hosts and stores all automation assets for collaboration such as flows, images, schedules, reports and so on.
- The Agents are doing all the work when it comes to executing automation flows as requested by either Studio or Controller.
How an Agent is configured is called an Environment. An Environment includes information about an Agent's type and location.
A Schedule is basically a selection of automation flows that are executed on one or more Agents. The Schedules are executed by the Controller, that combines the flows selected in the schedule definition with the Environments selected in the schedule definition.
You can create any number of Schedules, and an automation flow can be part of several Schedules. For example, we could have a schedule with 500 flows making up a full regression suite for a software product, but before running this on the full stack test environment, we want to make sure it's worth the effort. In this case we could create yet another schedule containing a subset of the flows and run it against a development server.
The tutorial below covers how Schedules and Environments, including how they are used and configured with LEAPWORK to run batches of flows at different schedules and devices.
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.