Recorder
The fastest way to a first draft: click Record, use your app the way a user would, and Studio writes each action as a step.
- Pick the app: one from your project, any URL, or (on macOS) a desktop app.
- Click Record. Web apps open in a browser window; desktop apps are watched where they are.
- Use the app. Each click, fill, key press and selection appears as a step, with the most stable selector Studio can find: an id if there is one, otherwise role and name, scoped if needed.
- Click Add assertion and pick an element in the live app to check it’s there, or that it shows a value.
- Edit or remove steps, then Save test. The new test opens in the Tests view.
Record again starts over; Discard empties the list.
Make the recording a good test
Section titled “Make the recording a good test”A recording is a draft. Before you keep it:
- Name it after the behaviour it checks.
- Add checks. A recording knows what you did, not what you expected to see. Every test should end with an
expect. - Replace sign-in and other shared steps with a
call:to a flow (Studio will hint where). - Remove detours: the misclick, the field you filled twice.
Made by
© 2026 Bussin Bytes Ltd · sisyphus.bussinbytes.io
