JOIN WAITLIST

Playwright IDE
for Manual QA

[HOW WE CAN HELP]
We help you bring test automation to Manual QA teams without slowing down delivery.
[TRY IT YOURSELF]
JOIN WAITLIST

Record tests and scale automation without writing any code.

[STEP 1]
Record steps in a table
Instead of manually entering steps into a table, the QA just enables recording mode in the browser and walks through the test flow.
[STEP 2]
Add manual step if needed
Run the flow directly on your machine and view results without writing a script. Skip complex automation steps and proceed as usual.
[STEP 3]
Get actionable test reports
View test results instantly in a readable format without setting up dashboards or exporting data to other tools.
50% OFF
$10
$20
/per seat
Join the waitlist today and get 50% off at launch. Simple UI testing at half the price.
[WHAT MANUAL QA CARES ABOUT]
Recording test without codding
Faster delivery time and regressions
Centralized test reports
Parallel test execution on server
Faster ROI for turbulent teams
[FREE & OPEN-SOURCE VERSION]
[PRO VERSION]

Test automation that simplifies QA the way it was meant to be.

...I want to automate UI tests with Playwright without writing any code myself.
Mickael B.
... It should let me add manual steps inside a test script when automation isn’t enough. ...
Andrew T.
I need the flexibility to add code to specific steps, and to import/export tests from Selenium IDE or to Playwright seamlessly.
Victor R.
[TRY IT YOURSELF]
Try it before anyone else
You test every day - now it’s our turn to make it easier for you.
Join our beta and help us refine the tool built for testers like you.
Oops! Something went wrong while submitting the form.

FAQ

What’s the difference between Playwright IDE and typical IDEs like IDEA and VS Code?
IDEA and VS Code are traditional coding environments, designed for writing and maintaining source code across many languages and frameworks.

Playwright IDE is a no-code testing tool, focused on creating, running, and managing Playwright tests through a visual, table-based interface. Instead of writing test code, users define test steps, actions, and assertions in a structured UI, making test automation accessible to QA engineers and non-developers.
How Playwright IDE differs from Selenium IDE?
Playwright IDE uses a similar table format for tests as Selenium IDE, so it feels familiar if you've used that before. The main difference is it runs on Playwright, which handles modern websites more reliably and with fewer issues. It also includes options like manual steps and small code additions for handling complex parts.
Playwright vs Playwright IDE: framework or no-code tool?
Playwright is a developer framework for writing automated UI tests in code.
Playwright IDE is a no-code layer on top of it - it lets manual QA engineers record actions, add manual or coded steps, and export them into Playwright scripts without writing any code.
How does the manual step feature work in Playwright IDE?
With Manual Steps, you can add a row in your test table that pauses the automation and shows instructions for a manual check, such as "Look at the email and confirm it's correct." After you do the check and continue, the test picks up from there. This works well for situations where automation alone isn't enough, and you don't need to code for it.
Is coding required to use Playwright IDE?
No, coding isn't required. You can record and run tests without writing any code, similar to Selenium IDE, while using Playwright for better performance. If a step needs adjustment, you have the option to add a short code snippet in the table.
How do I set up CI/CD with Playwright IDE?
To set up CI/CD, export your tests as Playwright files and add them to a tool like GitHub Actions or Jenkins. The process involves a few basic steps, and there are guides to help. This way, tests can run automatically without much coding involved.
How does exporting to Playwright work in Playwright IDE?
Exporting turns your table-based test into Playwright code with a single click. You can also import tests from Selenium IDE to get started. This allows you to use the code for more advanced testing or across different browsers if needed.
Join the Beta
JOIN WAITLIST