What is Leapwork Play?
Leapwork Play helps you create, run, and maintain automated tests for web applications with artificial intelligence (AI) assistance. It is part of Leapwork’s Continuous Validation Platform. You review the generated tests and decide whether they check the behavior you need.
You can start by recording browser actions, describing a test in natural language, or using requirements and documentation to plan test coverage. Play also supports existing Playwright scripts. This guide starts with recording so you can follow one workflow from test creation to its result.
Create a test case in Leapwork Play, record a short browser workflow, and run it to check the result. Play is generally available, and you can sign up for free at leapwork.ai.
For your first test, focus on one behavior and one expected result. You do not need to install a local recorder: Play provides a cloud browser for recording and running web tests.
Understand the core concepts
-
Test case: Steps and checks that validate one behavior or workflow.
-
Recorder: Captures your browser actions and turns them into automated test steps.
-
Cloud browser: A browser managed by Leapwork for recording and running tests, without installing a local recorder.
-
Playwright: The browser automation framework behind the generated test code, which you can inspect as you work.
Later, you can use a Knowledge Base to give Play application context and generate blueprints: outlines of what a test should validate. You do not need to start with those workflows to record your first test.
Before you begin
-
Choose a web application you have permission to test. For practice, use an application from the Leapwork Demo Sites.
-
Have the application URL and any approved test account ready. Use test data rather than real customer or payment information.
-
Decide what the test must prove. For example, a search test should check that a known result appears, rather than only record typing and clicking.
Start with an application the cloud browser can reach. Private applications may need additional connectivity setup.
Sign up and open Play
-
Open Leapwork Play.
-
Sign up for a free account, or sign in if you already have one.
-
Open the workspace and team where you will keep your test.
Free sign-up does not mean unlimited usage. Check the plan and credit information in your account before running longer workflows.
Create your first test case
A test case contains the steps and checks for one behavior. Give it a name that describes the expected outcome, such as “Find a known product”.
-
Create a test case in your team.
-
Enter a descriptive name for the test.
-
Add or select an environment for the application you want to test.
-
Set the application URL for that environment.
-
Connect to the cloud browser.
-
Confirm that the browser opens the intended application.
The application must be available before you start recording. If it does not load, check the URL and whether the cloud browser can reach it.
Record the workflow
The Recorder captures the actions you perform in the cloud browser and turns them into test steps.
-
Start recording in the test case.
-
Perform the short workflow you chose. Keep the recording focused on the behavior you want to test.
-
Add a validation for the expected result. Check an outcome that proves the workflow succeeded, such as the expected text or page content.
-
Stop recording.
-
Wait for Play to finish processing the recorded steps.
A sequence of clicks is not enough to prove that the application works. Include a validation so the test can detect an incorrect outcome.
Review the test before you run it
-
Review the recorded steps in order.
-
Remove accidental or repeated actions that are not part of the test.
-
Check that the validation tests the result you intended.
-
Check that the test data is safe to use again.
Play also exposes the generated Playwright implementation. You can inspect it when you need more detail about a recorded interaction.
Run the test and check the result
-
Run the recorded test case in Play.
-
Wait for execution to finish.
-
Review the execution result and the outcome of the validation.
-
If the test fails, inspect the first failing step and compare the actual application state with the expected result.
-
Correct the test or investigate the application behavior, then run the test again.
Your first test is complete when Play can repeat the workflow and the validation confirms the expected outcome. Check the validation itself before treating a successful run as evidence that the application behaves correctly.
Build on your first test
Add another test for a different outcome once the first test is repeatable. Keep each test focused so failures are easier to understand.
-
Reuse a common login workflow instead of recording it separately in every test.
-
Use requirements and documentation to plan more coverage with the Knowledge Base and Blueprint Generator.
-
Explore natural language test creation or connect an AI coding tool through Play’s MCP integration when you are ready to extend the workflow.
Get help
Use the Play community to ask questions and report problems. Include what you were trying to do, the step that failed, and the error message. Remove sensitive data from screenshots and recordings before sharing them.
Glossary
Below is a glossary to help you get acclimated to Play’s terminology and nomenclature.
|
Term |
Definition |
|
AI Agent |
An AI-powered assistant that helps create, manage, or interact with tests. |
|
Play |
Leapwork’s AI-native product for creating, running, and maintainingautomated tests for web applications. |
|
Blueprint |
A test case outline that describes what a test should validate, including high-level steps and expected results. A blueprint can be turned into a single executable test case. |
|
Blueprint Generator |
Play functionality that uses a Knowledge Base to generate multiple blueprints that can be converted into real test cases. |
|
Cloud Browser |
A zero-install, zero-maintenance browser environment managed by Leapwork, used to record and run tests in Play. Cloud browsers can be selected by browser type and geographic region. |
|
Cloud Execution |
Running tests in Play’s cloud environment instead of on local infrastructure. |
|
Continuous Validation |
Leapwork’s approach to continuously validating that software works as expected as it changes. |
|
Evidence |
Source material that supports a generated recommendation, Blueprint, or response. |
|
GA |
General Availability. |
|
Human-in-the-Loop Approval |
A review step where the user approves AI-generated actions before they are executed or adopted. |
|
Knowledge Base |
Play’s application-specific understanding generated from documentation, requirements, code, tickets, and test assets. |
|
Knowledge Graph |
A visual map of the functionality and dependencies Play identifies from your Knowledge Base. |
|
MCP |
A protocol that connects Play to AI coding tools such as Claude Code, Codex, or Antigravity. |
|
Playwright |
Playwright is an open-source end-to-end testing framework developed by Microsoft, designed for automating modern web applications across Chromium, WebKit, and Firefox browsers. |
|
Prompt |
A natural language instruction given to Play. |
|
Recorder |
Functionality that captures real user actions in the browser and turns them into an automated test. |
|
Self-Healing |
Play’s ability to help tests adapt when an application changes. |
|
Test Case |
A set of steps used to validate a specific behavior or workflow. |
|
Test Suite |
A collection of related test cases. |
|
Traceability |
The link between a generated test or recommendation and the source material behind it. |
|
XPath Healing |
A form of self-healing where Play helps recover or adapt a test when an XPath-based locator changes or breaks. |
Community Guidelines
Please help us maintain a safe space for the community to engage and collaborate positively by following these guidelines:
-
Keep preview information private. Do not post screenshots, recordings, product details, or commentary publicly unless Leapwork gives explicit approval.
-
Share feedback openly and constructively. Bugs, rough edges, missing features, confusing moments, and “this didn’t work how I expected” comments are exactly what we want.
-
Share what you’re trying, learning, loving, questioning, or breaking so this feels like an active community shaping Play together
-
Do not share sensitive customer, company, or personal data in Slack.
-
Use the feedback form for product feedback and bug reports so our team can track, triage, and follow up.
-
Be respectful. This is a builder community. Assume good intent, help others where you can, and keep discussion focused on learning and improving the product.
-
Discussion of other tools and competitors is welcome when it is constructive, respectful, and focused on learning not harassment, vendor-bashing, or unproductive criticism.
-
Features may change, break, improve, or be removed as we learn from usage and feedback.
FAQs
How do I access the product?
-
Play access is currently invite-only. If you received an invitation, use the access link below to sign in and begin exploring.
-
Access Play: https://leapwork.ai
How do I give feedback?
Your feedback is one of the most important parts of the Play. We are looking for honest, specific, and constructive feedback about your experience with Play. We want to understand what you tried, what worked, what did not work, what felt valuable, and what would make the product better.
Use the feedback form for product feedback, feature requests, confusing experiences, AI output quality issues, and workflow observations.
Join our community and post in the #feedback-and-ideas channel: Slack Community
How do I report a bug?
If something appears broken, unexpected, or impossible to complete, please report it as a bug. A good bug report helps us understand what happened, reproduce the issue, and prioritize the fix.
Join our community and post in the #bugs channel: Slack Community
How do I request support?
If you’re having trouble accessing the application or something appears to not be working as intended, please let us know and we will be able to support you ASAP.
Join our community and post in the #help-and-access channel: Slack Community