Skip to main content

Recording a Flow

A fourth way to populate the step list on the New Playtest page, alongside writing steps by hand, describing them in your own words, and picking a built-in template: click through the real flow yourself, in your own browser, and VeriWasp converts what you did into the same editable step list the other three methods produce.

Starting a recording​

On the Starting point dropdown, choose Record it yourself (click through your flow). This replaces the step list with a setup panel containing a 🔴 Record with VeriWasp button and three instructions. That panel is a bookmarklet: a browser bookmark whose destination is a small script rather than a URL.

One-time setup​

Drag the 🔴 Record with VeriWasp button to your browser's bookmarks bar. This is a one-time-ever step: the bookmarklet itself isn't tied to this particular recording session, so you never need to drag a new one for a future recording. Once it's in your bookmarks bar, starting any future recording is just: click Record it yourself on the New Playtest form, then click the bookmark.

Recording​

With the bookmarklet installed, open your app (in the same tab or a new one) and click the bookmark. A small popup window briefly appears and closes on its own — this is VeriWasp figuring out which of your recording sessions the bookmarklet click belongs to, so the bookmarklet doesn't need a token baked into it. Once it closes, a small overlay appears in the bottom-right corner of the page reading "Recording... 0 step(s)."

From here, just use your app normally:

  • Clicking a link, button, or anything with an onclick handler records a click step. The step's description is built from the element's aria-label, placeholder, visible text, or name attribute, in that order, whichever is present first, the same signals the AI element resolver already uses at execution time (see Step Types & AI Resolution).
  • Typing into a text field or textarea records a type step once you leave the field (on blur, or when its value changes). Password fields are an explicit exception: the step is still recorded so the shape of the flow is right, but the value typed is never captured. That step comes back with its value left blank for you to fill in yourself once you're back reviewing the step list, rather than a real password ending up captured from your own browser.

The overlay's step counter updates live as you go. Assertions aren't captured (nothing you do while recording maps onto "verify something is present or absent") so you'll add those by hand afterward, same as finishing off an AI-drafted or template-based plan.

When you're done, click Finish in the overlay. The captured steps are sent back to VeriWasp, and the New Playtest page (which has been quietly polling in the background) picks them up automatically and swaps them into the normal, editable step list; no need to switch back to that tab first.

Page reloads and leaving the site​

Two situations interrupt a recording differently:

  • A same-origin reload (a real form submit, or a link that reloads the page you're on): nothing captured so far is lost, it's kept in the browser's session storage. But the freshly-loaded page is a clean slate as far as the browser is concerned, so recording doesn't automatically pick back up. Click the bookmark again on the new page to resume; the overlay reappears with your step count intact and you keep going from there.
  • A cross-origin navigation (an OAuth login screen, Stripe Checkout, or anything that takes you to a different site entirely): this is a hard stop. The step that triggered the navigation is still recorded, but nothing beyond it can be, since the recorder has no way to follow you off the original site. The overlay marks itself "paused" before this happens, and the steps you do get back are a clear, honest partial flow, not a silently truncated one; you finish the rest by adding steps manually in the step editor, the same way you'd extend any other draft.

Session lifetime​

A recording session stays open for 15 minutes after you start it. If you start one and don't finish within that window, the New Playtest page's setup panel tells you the session expired and to select Record it yourself again to start a fresh one. Recording nothing, or abandoning a recording partway, has no other consequence: no credit is spent and no run is created until you review the resulting steps and click Confirm & Create Run, same as every other starting point.