The LEAP

Automation insights and productivity tips from LEAPWORK.

All Posts

How to Handle Visual Changes in Systems under Automation

Sometimes, user interface elements on screen can change size, color or shape depending on their state. For instance, a button might change from blue to green to signal something to the user.

In some situations, it might of course make sense to interact with the button only when it is green, and that can be done with a building block such as Click image.

However, there are other situations where the changes in state and visual appearance shouldn't impact test logic. For instance, if you want to double-click the Excel document shown below with a Click image block, it might not matter if the icon is unselected, selected or hovered by the mouse:

Image collections example with excel documents

In other situations, the same user interface element might be rendered very differently on regular HD and Retina resolution screens.

For all of these reasons, LEAPWORK now has built-in support for "image collections". An image collection is simply multiple representations of the same user interface element bundled together and understood as one.

One way to create an image collection is to capture a number of variations of the same image, as shown below:

Captured image collection images

Dragging one images onto another automatically creates an image collection which can then be named and expanded with more variations:

Image collection popup

Using image collections in your test cases is very simple; it works just like regular images. Just drag the image collection into a building block such as Click image and you are all set:

Image collection used in a case

When running this case, LEAPWORK will look for any and all of the images inside the image collection and click the first one found. If more than one is found, the "Use all occurrences" feature can be used to iterate through them.

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

Related Posts

How to Analyze Test Automation Results

As test automation is introduced to the software delivery process, the amount of available test results explodes. Robots, or test execution agents, can run 24/7 without breaks, and, on top of this, the number of test cases accumulate during each sprint. As such, more results are produced to be managed and analyzed. This requires the right approach.

Test Automation Strategy: A Checklist

Too often, test automation is not handled as a strategic choice as there’s too much focus on putting out fires here and now. Test automation is a cornerstone in DevOps, and when implemented correctly, it helps increase output quality while containing costs. Not surprisingly, IT departments everywhere are realizing the importance of having an actual test automation strategy.

5 Failures in Test Automation – and Best Practices for Tackling Them

Too many test automation projects fail – and often for predictable reasons. To help you avoid these pitfalls, we have condensed the most common issues into this short guide along with related best practices for achieving success with automation.