Architecture Overview

Studio, Controller and Agents

It’s important to understand that LEAPTEST is made up of three components: Studio, Controller and Agent:

Leaptest architecture overview, Studio, Controller and Agent with REST API

Studio is a desktop application made for Microsoft Windows 7 or later. It’s a powerful, visual designer that you can use to easily create automation cases, setup run schedules and dig into the results with dashboards and reports.

The Controller is a service that runs in the background, and it’s also made for Microsoft Windows 7 or later. It hosts all of the automation assets such as cases, images, schedules, reports and so on. It also controls how automation cases are run and on which environments.

Studio talks to the Controller using an open REST API that you can also tap into as much as you like.┬áIf you don’t know what a REST API is, don’t worry. It’s just our way of opening up our engine room to anyone who want to integrate LEAPTEST into their own systems.

The last component is the Agent, which is a service that will run in the background on any operating system or device that you want to run automation cases on. We call those environments. The Agent takes care of actually executing the automation cases on the environment and will continuously talk to the Controller using a closed remote control protocol, updating it on the current status.

For now, the Agent service is available on Microsoft Windows 7 SP1 or later and OS X / macOS.

You can connect as many Studios and Agents to a Controller as you have licenses for — for instance to share test cases and environments among team members.

It’s important to note that the Controller and Agents can be installed in closed networks without internet access, such as firewalled test networks. Studio, on the other hand, does require an internet connection for license activation and error reporting.

Author: Jakob Vinkel-Schaarup, July 8, 2016.