Leapwork

I think that the codeless interface is a brilliant idea and increases the efficiency of the testing team significantly. For my team, where testing is just one of the responsibilities we have when upgrading and patching the product, we don't want to start training people up on programming languages so that they could start writings tests. With Leapwork the learning curve is very shallow and people can get started right away.
I am impressed with the selection of blocks that have been included and haven't required any functionality so far that there wasn't either a block for or a could make a simple sub-flow for.
The strategy editor, which is used to decide how to identify the GUI elements being manipulated, is really really clever!

The debugging functionality needs to be improved. When running complicated flows with mutiple sub-flows inside, when a bug occurs it is difficult to dig down into the sub-flow where the problem occured, and even when you've reached it there is no context specific data on the variables feeding into or out of the trouble making block.
I don't think that their approach to customer support is correct, and I have spent hours spinning my wheels as I carried out long conversations with their support stuff via a chat window on their homepage.
Some of the initial steps that are required, like making a test flow to log onto the Leapwork agent server, were not clearly explained.

The functionality of the platform was as expected. We chose to engage with Leapwork to help us automate some web-based processes, and admittedly that's not their bread and butter.

Lack of communication and customer service.

- Ability to create automated tests for a thick client
- User friendly views for creating tests from a flowchart
- The ability to scheduled tests

- Scheduled tests couldn't deliver notifications to multiple emails
- Email validation was very strict.
- Electronic signature image recognition was slow and timed out frequently

Leapwork is a visual object oriented tool for creating flows that automate repetitive actions in the operation of software, both for desktop apps and for websites, ideal for testing! No matter how simple or complex the flow, there are actually little restrictions because the set of building blocks is very complete where each block also has a rich set of options to specify its actual behaviour. Better yet, the set may be expanded with custom made reusable subflows as blocks for commonly executed general actions such as logging into an environment or application or opening specific web pages, ensuring that the flows remain easy to understand at each level and easier to maintain. An extensive set of examples makes it very easy to give it a go and when I do then encounter a problem in applying Leapwork, the helpdesk helps me out using a very efficient chat. Flows may be executed interactively on a desktop or laptop or on a server, on BrowserStack or on a Selenium Grid, but also may be scheduled to run automatically at specific moments. Also, these schedules may be started from DevOps or by calling the REST API from e.g. Powershell scripts.

Leapwork is a very flexible and versatile tool that is fun to use. But when you flip that coin, it turns out it also is easy to make flows that are difficult to maintain. And yes, it takes some self-control not to step into this trap. But then, I made flows for adaptive websites that run on various window sizes and on test, acceptance and production sites ... all in the same flow! The reason why complex flows sometimes are not easy to maintain is because Leapwork has only limited options to execute flows step-by-step. This makes it difficult to pinpoint the exact location in the flows where things go wrong and therefore need some tweaking. The tweaking itself is easy and straightforward, but finding out where and when and why is a challenge. Also, it is not easy to output specific information without the need to go through the complete log that the flow creates.