Leapwork: automation without code for efficient testing processes

In the world of software development and testing, there is an ongoing search for tools that can speed up and simplify processes. One notable player playing a role in this is Leapwork. Launched in 2017 as Leaptest, this no-code automation tool from Denmark has been steadily gaining ground by focusing on reducing the barrier between human and machine.

>>> Listen to our Podcast about Leapwork <<<

The evolution of Leapwork

The original idea behind Leapwork was ambitious: to optimize the User Experience (UX) and User Interface (UI) to create a user-friendly environment where no code is required. While the platform offers the ability to add code as needed, it excels in its ability to be used across multiple platforms: web, mobile, desktop and even virtual.

One of the most striking aspects of Leapwork is the heavy use of Optical Character Recognition (OCR). This allows users to do a lot without actually diving into the application’s code. Even in green screen applications that do not support unicode, OCR comes into its own.

Functionalities that make an impact

Leapwork is distinguished by its main functionalities aimed at simplifying the automation process. It works with building blocks, a visual automation flow that creates tests by adding action blocks and connecting them together. This means that even without programming knowledge or in-depth technical knowledge of the SUT (System Under Test) users can intuitively and easily interpret the automation flow.

The smart recorder, Leapwork’s version of a record-and-play-testing tool, is fast and especially accurate in choosing parameters for identification, which is not always the case with other tools. It also integrates Optical Character Recognition, allowing testing of almost any application, even if certain overlays or virtual apps make it difficult to access elements.

With a proprietary REST API, Leapwork allows users to launch certain processes or request data even from outside the platform. This facilitates integration with external applications and greatly simplifies the process.

Strengths and concerns

One of Leapwork’s strengths is its integrated version control, which requires users to add a note when saving tests. This promotes awareness of changes made and may take some getting used to at first but eventually proves useful for tracking progress.

Reusability of components, though powerful, requires discipline for maintenance. This is especially true for Subflows, a collection of steps to reuse or keep processes clear. Properly structuring tests and using Subflows is essential to maintaining a streamlined test flow.

But as with any tool, Leapwork has areas of concern. Technical limitations, being a relatively young tool, mean that not all new features are already available. The fact that Leapwork is a no-code tool also means that there are limited options for adding external code, with support only for JavaScript or limited C# blocks.

Is Leapwork the right choice?

Using Leapwork requires a degree of discipline and adherence to best practices. Extensive API and technical testing may require additional tools, although integration capabilities ensure that results can be included and reported within Leapwork.

It is essential to examine Leapwork’s compatibility with a project’s specific technology stacks. In addition, one must ask whether Leapwork really fits the organization and whether it effectively addresses the specific automation needs and problems.

My findings

Leapwork provides an intuitive, no-code environment for automated testing. It allows users to create test flows quickly and easily, albeit with a certain amount of discipline for maintaining and structuring the tests. The tool has its strengths, but also some limitations that require careful consideration before fully committing to its use.

As an automation software, Leapwork must fit the organization and adequately address its specific needs. Therefore, comparing and trying out the tool remains an essential step before fully relying on it for automated testing processes.

Author: Maxim Leyssens