Setting

How can we choose the order of the cases in the Scheduling?

If you are using Leapwork for robotic process automation, you can think of run lists to control the order in which your robots run. There are two ways to decide the order of the flows: Ordering Flows In Steps The scheduler executes automated test cases in the order they have been arranged in the run list, from top-down.

How to conduct parallel and/or pairwise testing using Leapwork

With Leapwork users can run multiple flows at the same time in different machines by executing them in parallel or users can run the test pairwise where each flow will run on all selected environments to test all possible discrete combinations, here is how parallel and pairwise testing can be conducted using Leapwork.

How to do cross browser compatibility testing with Leapwork?

Leapwork fully supports cross-browser testing on all modern browsers. Please refer to the " Start Web Browser " block, that comes with the capability to launch the chosen browser from the available drop-down list as below: Any test which is created using one of the browser can also be executed on other browsers as well.

How to re-run failed test cases

Leapwork comes with a REST API, allowing any third-party system to schedule and run automation flows on the platform and retrieve the results. Rarely, runs that are scheduled through a third-party system may fail and we may need to rerun those failed test cases of the schedule. In Leapwork, we can manually re-run failed flows of a.

Could not connect to the controller- Please check that the Leapwork Automation Controller is running on : 9000

The Leapwork Controller is the central component in the Leapwork Automation Platform. The studio is depending on it to gain access to all the flows and related assets. The Controller also manages the Agents used for executing the automation flows. When a user starts the Studio the first time, it will automatically show the...

Controller service does not start automatically although it is set to do so

It's been observed that on some machines Leapwork controller service fails to start automatically, this issue may occur due to the system being unable to load too many applications at the boot time. To handle this challenge users can use the Automatic (Delayed Start) option in services to start Leapwork service.