Recipes

Short, task-first answers for browser automation work: find the problem, copy the pattern, then adapt it to your test.

Start here

Six representative recipes cover the recurring work: state, network, waiting, files, capture, and frames.

Reuse a login session Log in once, save the browser state to a file, and load it into fresh contexts. Mock an API response Serve a fixed JSON payload for an endpoint so you can reach a rare or fragile UI state. Wait for an element to disappear Let a spinner, loader, or toast finish before you assert on what replaces it. Upload a file Set files on a file input, upload several at once, and clear the selection without touching the OS dialog. Record and open a trace Capture actions, DOM snapshots, and network activity from a run, then inspect the trace locally. Interact inside an iframe Scope a locator to a frame with frameLocator, then act and assert inside it.

Browse by task family

Choose the kind of task, then open a focused recipe or the complete category.

Locate & inspect Find the right element before acting: text, attributes, frames, Shadow DOM, and repeated page structures.

Forms & input Drive real controls: text fields, selects, checkboxes, keyboard shortcuts, drag and drop, hover menus, and date pickers.

Files & downloads Upload files into controls and capture downloaded artifacts from the browser.

Waits & assertions Replace sleeps with page-state checks, retrying expectations, polling, and disappearance waits.

Network & mocking Wait on backend calls, prepare data through APIs, stub services, and keep noisy requests out of the scenario.

Sessions & auth Prepare authenticated state with cookies, HTTP auth, storage state, and consent handling.

Dialogs & windows Handle popups, beforeunload prompts, JavaScript dialogs, and browser windows deliberately.

Capture & debug Record the evidence you need when a run fails: traces, video, and focused screenshots.