Recording your first test

What gets captured on each step

• The action: click, type, select, navigate, hover, key press.
• The element, with every locator strategy the recorder could derive for it. This is the raw material self-healing uses later.
• The network requests the step triggered, with status, timing and size, so an API-level assertion can be added without a second tool.
• Screenshots along the flow, used by visual regression and by the failure view.

Adding assertions

Assert on visible text, element state, URL, or a network response while you record. An assertion is a step like any other and can be edited afterwards. Recordings without assertions still replay, but they only prove that the journey did not crash, which is rarely what a release decision needs.

Authentication

Record the sign-in as part of the flow, or sign in once and let the platform store the session state and reuse it on replay. Stored session state is kept server-side and scoped to the recording session. For applications behind SSO, record the SSO steps once with a test identity.

Replaying

Run the recording on demand, on a schedule, or from a CI trigger. When a step fails, the failure view shows the failing step, the locator it used, the request it made and the screenshot at that moment. When the failure is a selector that no longer matches, the heal-review queue proposes a repair; nothing changes until a person approves it.

Exporting as code

Any recording exports as Playwright, Cypress or Selenium code. The exported test runs in your own framework without the platform. Teams use this to keep an existing framework while using the recorder and heal review to cut maintenance.

test('checkout', async ({ page }) => {
  await page.goto(env.BASE_URL);
  await page.getByRole('button', { name: 'Add to cart' }).click();   // elem_0004
  await expect(page.getByTestId('cart-count')).toHaveText('1');       // assertion 1
});