tool · one of 34 Pro script file
Recorder
Can I record what I just did as a test?
The gap between reproducing a bug by hand and having a test for it is transcription, and transcription is where the reproduction gets lost. This records what you do - including across navigations - and writes it as a script.
Reach it Press ⌘ + K on any tab and type recorder. Ctrl + K on Windows and Linux
in the panel · this one is Pro
What this actually is
record clicks and typing out as a test in your frameworkWhile reproducing something, not afterwards. The panel owns the step list rather than the page, because a navigation destroys anything running inside the page - which is why recorders that live in the page lose everything at the first link.
Asked about this tool
3 of themDoes my typing leave the browser?
No. The recording is built and printed in the page; nothing is uploaded, and the panel makes no request while recording. Password fields are never captured at all, so there is nothing to leak even locally.
Will the test still pass tomorrow?
That depends on the selectors, which is why the fragile ones are marked. A step locked to a role and an accessible name survives a redesign; one locked to div > div:nth-child(3) does not, and you are told which you have.
Can it record a login?
It records the steps and leaves the password as a placeholder for you to fill from an environment variable - which is how the test should have been written anyway.
how to use recorder
- Open Recorder before you reproduce anything, not afterwards.
- Do the thing. Clicks, typing and navigations are all recorded, including across pages.
- Stop, and read the step list. The panel holds it because a navigation destroys anything in the page.
- Export the Playwright spec. Password fields are redacted.
70 of these · no host permissions · three free audits