When you want a bit more control of how web and desktop objects are located when designing UI automation, the LEAPWORK Strategy Editor is your friend.
When automating tests and processes with LEAPWORK, you can, in most cases, capture UI elements once with a single click, and then let LEAPWORK take care of finding that element in the future. In some cases, you'd want a bit more control of what's going on under the hood when elements are located. That's what the Strategy Editor is for. Common examples of when you'd want to work with the Strategy Editor are:
- Data-driven automation
- Dynamic selections, e.g. finding the first article in a list, and not a specific article
- When your want to make sure elements are captured with a specific approach
Complex applications that complicates how elements are captured
The introductory tutorial below will give you a basic understanding of how the Strategy Editor works, including:
- What is a locator strategy?
- How to set conditions for a locator strategy
- How to validate those conditions
The tutorial uses the structure of a web page as an example of how you can use different strategies to capture elements. The basics of the Strategy Editor apply to both web and desktop applications, while the latter is covered more in depth in another tutorial.