The following key points need to be kept in mind while starting Automation with Leapwork:
1. Leapwork Architecture and Deployment
- Leapwork Automation Platform consists of three components:
- Studio (the designer)-This is the visual designer application that is used to create and maintain automation cases as well as review results
- Controller (the server)-This is the server that stores all automation assets and orchestrates running and gathering results.
- Agent (the runner).-This is the run-time agent that executes automation cases on virtual machines or in the cloud.
- Deployment of Leapwork Automation Platform can be combined with any combination of n number of agents Remote Agent, Selenium Grid, SauceLabs, BrowserStack, Gridlastic, Lambda Test.
2. Defining the Environment under test
- Leapwork supports the execution of automation flows on remote machines. This allows for 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 would help you to outline and describe the testing approach and each of the tests related to the automation testing of the delivered product.
- It includes:
- Explanation of the automation coverage
- What is covered/ What is not covered
- Test Environments
- Identification and description of any known risks
- Data requirements
- Team members roles and responsibilities
5. Automation Strategy:
- Test automation is a cornerstone in DevOps and, when implemented correctly, it helps increase output quality while containing costs.
- Get ahead of automation with an in-depth checklist comprising of:
- Risk analysis
- Failure analysis
6. Case Execution:
- CI /CD Integration
- Plug Leapwork into your CD pipeline and integrate with build and release systems using our public REST API.
- Built-in plugins are available for Jenkins, Azure DevOps, TeamCity, and Bamboo.
- Bug logging
- Automatic generation of bugs for the failed flows in a schedule can be done with Leapwork.
- Built-in plugins are available for Jira, HP Quality Center, Azure DevOps Server.
- Reporting allows users to easily monitor and evaluate the state of their automation flows across projects, products, business units, etc. All execution results - both 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.