Playwright IDE
for Manual QA
[HOW WE CAN HELP]
We take the pain out of UI testing.
No scripts. No setup. No coding stress.
Just record, run, and repeat while we handle the automation behind the scenes.
[TRY IT YOURSELF]
JOIN WAITLIST
Selenium IDE style,
but on Playwright
Record steps in a table
Instead of manually filling in a table of steps, the QA simply enables recording mode in the browser and walks through the test flow.
Playwright automatically captures each action and generates a clear, editable table of steps ready for review and automation.
Add Manual Step if needed
Some parts of testing still require a human touch. Approvals, visual checks, login with 2FA that are bloody difficult to automate in any way.
Just mark a step as “Manual” if you want automation.
You decide how technical the workflow gets.
Run locally or in CI, upgrade steps with code if needed and export everything to Playwright
You can run the flow directly on your machine and see results without writing a full script.
In addition, you can go deeper and enhance any step with small pieces of code.
Then export the whole flow to Playwright to get a complete, production-grade automated test you actually understand.
.png)
Key features
[WHAT MANUAL QA CARES ABOUT]
Made for the
challenges you face
.svg)
...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.
FAQ
What’s the difference between Playwright IDE and Selenium IDE?
.svg)
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.
What’s the difference between Playwright and Playwright IDE?
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.
.png)
.svg)
.svg)