Book demo
Start trial
Book demo
Start trial

The LEAP

Automation insights and productivity tips from LEAPWORK.

All Posts

How to Automate Remote Desktop Tests

Test automation is all about stretching your limited resources to do more in a shorter amount of time.

One very effective way to do that with LEAPWORK is to create your test automation cases once and then run them on endless repeat on one or more remote computers -- for instance in the Amazon EC2 or Microsoft Azure clouds or on virtual servers in your own network infrastructure.

We recommend that you install the LEAPWORK Agent (which is the executable that actually runs the tests) on one or more separate computers and then run your cases there instead of on your local computer. That way, you are not inconvenienced when LEAPWORK opens applications or uses the mouse or keyboard -- and you can get more done, faster.

The following diagram shows one way you could configure LEAPWORK to work:

Aktiv 4In this example, you could have Studio installed on your own computer or laptop, while the Controller could be installed on a server and the Agent could be installed on two or more other computers where the tests would actually be run.

LEAPWORK makes it very easy for you to setup a schedule that will execute any number of test automation cases on remote environments (agents). This is made possible by the built-in remote control protocol, which works a bit like Windows Remote Desktop or VNC:

Automated testing with remote control on a cloud server using LEAPWORK

Everything you need for codeless test automation

Learn more about codeless test automation in our guide to reducing risk, lowering costs, and driving value with test automation.

CTA-StartTrial-3

Claus Topholt
Claus Topholt
CTO and co-founder of LEAPWORK.

Related Posts

How Does Behavior-Driven Development (BDD) Support Agile Development?

Behavior-Driven Development (BDD) was carefully developed to support agile development in the software industry. This is because agile cannot be fully deployed if the testing process still follows a traditional methodology.

Functional UI Testing Whitepaper: An Introduction to Codeless Test Automation

Faced with frequent product releases and system upgrades, there is increasing pressure on the resources used in software testing. One small change or upgrade can affect the whole software within seconds meaning that, if the functionality is not being continuously tested as per design, a single bug could have a tremendous effect on user experience.

Traditional Development vs. Behavior-Driven Development (BDD)

  Behavior Driven Development (BDD) is no new concept in the software development industry. Still, many companies don’t fully understand the benefits of this framework in the development process. In a world where traditional development methodologies have excluded team members in silos, BDD serves as a collaborative force that fosters agile development.