Points to consider before starting automation with Leapwork

Here are important points to be keep in mind prior to getting started with Leapwork:

1. Leapwork architecture and deployment 

The Leapwork Automation Platform consists of three components:

• The Studio (the designer): This is the visual designer application used to create and maintain automation cases as well as review results
• The Controller (the server): This stores all automation assets and orchestrates running and gathering results.
• The Agent (the runner): This is the run-time agent that executes automation cases on virtual machines or in the cloud.

Deployment of the Leapwork Automation Platform can be combined with any of the following agents: Leapwork's Remote Agent, Selenium Grid, SauceLabs, BrowserStack, Gridlastic, and Lambda Test.

2. Defining the environment under test

Leapwork supports the execution of automation flows on remote machines. This allows flows to run uninterrupted and provides the possibility to run the same flow in different configurations.

Leapwork comes with four different types of environments, each offering different capabilities:

• Remote (Agent) – Leapwork Agent
• Web Only – Selenium Grid
• Web Only – Sauce Labs
• Web Only – Browser Stack
• Web Only – Gridlastic
• Web Only – Lambda Test

3. Case selection 

• Automation of regression, smoke, and sanity tests
• Tests that require multiple data sets
• Critical parts of the application
• Repetitive test runs
• High-risk test cases

4. Automation Plan:

An automation plan can help you to outline and describe the testing approach, including a list of tests  that can be automated in support of the delivered product. Ideally, your automation plan should include:

• An explanation of the automation coverage
• What is covered/ What is not covered
• Test environments
• Identification and description of any known risks
• Data requirements 
• Roles and responsibilities of team members

5. Automation strategy:

Test automation is a cornerstone in DevOps and, when implemented correctly, it helps increase output quality while minimizing costs.

A strategy can help you get a good headstart on automation. Your strategy checklist should include:  

• Scope
• Approach
• Risk analysis
• Environment
• Execution
• Release
• Failure analysis

6. Case execution:

Two key components of case execution are CI/CD integration and bug logging. 

• CI/CD integration: Leapwork integrates into your pipeline, including build and release systems, with dedicated plugins available for Jenkins, Azure DevOps, TeamCity, and Bamboo. To integrate Leapwork with alternative tools, you can use our public REST API.
• Bug logging: Leapwork can be set up to automatically generate bug reports from failed flows in a schedule. Built-in plugins are available for Jira, HP Quality Center, and Azure DevOps Server.

7. Reporting:

Reporting allows users to easily monitor and evaluate the state of their automation flows across projects, products, business units, and more. All execution results, including preview runs, manually triggered schedules, and API-triggered schedules, can be accessed in the reporting section.

If you have any questions, contact our Priority Support.