The LEAP

Automation insights and productivity tips from LEAPWORK.

All Posts

How to Build Cross-Application Test Automation

Business-critical processes of everyday work often involve several applications across environments, i.e. both desktop and web applications. This makes it especially challenging to test those processes with conventional methods.

Relying on programming for cross-application test automation is often both difficult and time-consuming as it would require in-depth knowledge of the systems and languages of the different applications involved. With visual automation design, a test case can be built and managed from one place, using the same intuitive logic across the entire flow.

In a previous post, we outlined how to automate desktop testing with simple flowcharts. We presented an example of a desktop-based business flow in an insurance company that was put under automated testing.

In this post, we outline an example of a test case that involves both web and desktop applications to show how the same, intuitive approach of flowchart-based automation can be used in a cross-application test scenario.

Specifically, the flow under test involves three applications:

  • A desktop-based CRM system;
  • A desktop email client;
  • A web-based email application.

1. Draft the automation flow

The first step is to set up a flow. This can be done in a visual manner using building blocks as depicted below.

The purpose of this test case is to test the sending and receiving of an email to an address found in the CRM system.

Cross application automation flow Sketching the process to be tested. As illustrated, the flow passes through several application boundaries. This sketch serves as the basis for designing the automation case.

 

2. Set up with a no-code automation tool

Next step is to set the flow up in your automation tool. This is easiest with a no-code tool that uses the same building block format. The tool should of course also allow you to automate across technologies.

The flow combines web and desktop automation. This is easily done with LEAPWORK by using a mix of Web and Desktop UI building blocks. 

LEAPWORK cross application automation flow How to design the test case with LEAPWORK using flowchart-based automation.

 

There are blocks for each of the actions involved, including generic action such as:

  • Starting applications
  • Finding and interacting with objects
  • Setting values

In this test case, we have also included a custom block (the purple one): The process of logging in to the CRM system has been created as its own reusable block. Check out this video walk-through about custom-made building blocks to learn more.

3. Transfer values effortlessly across applications

A very useful feature of this test case is how easily values can be shared between applications. This is activated by the blue arrow in the flow.

The element used for verification in this test case is an email subject line; if the specified subject line can be found in the inbox of the web-based email client, the case has passed. The subject line is set as a value in a building block for desktop automation, and then it automatically serves as input in the verification step of the test case that takes place in a web application.

LEAPWORK Find Web Element building block
The blue arrow represents the automated input feed to the verification step of the test case.

 

This direct transfer of values across applications and environment, without having to rely on intermediary steps, makes it incredibly easy to run varying test scenarios.

To learn how the automation case was built step by step, watch the instructional video below. It's also available in our Learning Center.

 

 

The benefits of automating a cross-application test case like this with visual flow-based design include:

  • Testers can manage the entire flow from one place.
  • The case can be designed in minutes and from then on, it can run repeatedly, 24/7 if needed.
  • The case can change hands without extensive handover between colleagues.
  • Values set in one application can automatically be used as direct input in another application.

Learn more about flow-based design and no-code automation by signing up for our webinar below.

Join our webinar

Aske Denning
Aske Denning
Content Marketing Manager at LEAPWORK

Related Posts

Best Practices for Building Maintainable and Scalable Test Automation

There’s a major difference between automating twenty test cases and automating 2000 test cases; while it’s completely possible to take an ad-hoc approach when there are only a few test cases, it becomes an entirely different story when test cases run into the thousands.

How to Build Stable Test Automation

Test automation brings many benefits with it, such as increased execution and reduced risk. But these benefits may be diminished if the tests aren’t performing as intended. There are several reasons why tests become unstable, most of which you can turn around by following these best practices and guidelines.

How to Effectively Analyze Test Automation Results

If you have introduced test automation as a means to achieve more efficient testing, you’re probably also interested in making the test result analysis process as efficient as possible. This requires the right approach and the right set of tools.