Skip to content

Record and generate e2e testsOne recorded flow, and everything Blendra makes from it.

Follow one login on a demo app, Acme.

The product windows on this site are illustrations drawn from Blendra's real fields and labels, with demo data.

Recording

Recorded in your own Chrome

Install the recorder, press Start on any site you open in Chrome, and use your app. Blendra records clicks, typing, selects, checkboxes and navigation across pages, single-page apps and iframes, with what the app showed after each step and a ranked locator for each element.

Checks

Tick what the app showed

Tick recommended ticks the clear outcomes in one click, and values that change, like order numbers and dates, become patterns.

Code

Real Playwright in your repo

One spec per journey and page objects shared by every journey. Playwright TypeScript on every plan; Playwright Python and Cypress (New) on Pro+ and Team. Download it with Export suite.

Scenarios

Same steps, other data

Suggest with AI proposes more data variations, for 1 AI request.

Run

Run it in your CI.

GitHub Actions or any other CI works. Results from CI need an API token, on Pro and above.

Cloud runs

Not on blendra.app yet

Cause

Every failure gets a cause

Each cause is rule-based and free on every plan: what happened, whose move it is and what to do next. Explain with AI turns it into two plain sentences for 1 AI request.

Test case

A test case a person can read

One click makes a test case from a recording (a test doc, in the app): preconditions, test data, numbered steps and expected results. Where the recording has checks, the expected results are their sentences.

Library

New tests from what you already recorded

Every recording fills a page library of pages, actions and elements. Rename them once and the page objects read better everywhere. In the Test Builder, arrange Go to, Do and Check steps from them.

  • Capture elementsSoon
  • Suggested testsSoon
  • Verified failure scenariosSoon

API

API tests, per environment

Write HTTP tests with status, header, body, JSON path and response-time checks, and export them to tests/api/. IDs in paths are the values you set.

Run on

The whole loop, one step at a time.

How it works

For one tester or a QA team

Pro and Pro+ are one seat. Team includes 5 seats (+$50 a month or $500 a year each), each with one of these roles. Invite QA and engineering to the same suite.

Workspace roles

  • Owner
  • Admin
  • QA lead
  • QA engineer
  • Developer
  • Viewer

Record your own flow.