Record a flow in desktop Chrome and get end-to-end tests as a Playwright project: specs, page objects, locator files, test data and a GitHub Actions workflow. After each step, tick what your app showed (a message, a URL, a heading). Each tick is a check with the real value. No LLM writes the code: same recording, same output. It runs in your CI without Blendra. On Blendra's cloud runner, a failed test gets a rule-based cause with evidence. Free plan. 7-day Pro trial, no card.

Hi, I'm Blend, a solo developer from North Macedonia.

For about 3 years in QA automation and frontend, I kept rewriting the same end-to-end tests whenever the UI changed. I built Blendra for developers and QA engineers who want tests they'd keep in the repo.

Record a flow once in desktop Chrome and get:

A Playwright project: specs that call page objects, plus locator files, test data and a GitHub Actions workflow.
Checks you tick from what your app showed, each with the value it displayed.
Cloud runs. A failed test gets a rule-based cause, the evidence and one next step.

No LLM writes the code: same recording, same output. It runs in your CI without Blendra. Nothing is sent without an API token, and with BLENDRA_REPORTER=off it never contacts Blendra.

No account: paste a Playwright codegen script into the free converter (or press Try a sample) and get page objects in your browser tab. Nothing is uploaded.
https://blendra.app/tools/playwright-codegen-to-page-objects

No extension: sign up free and open the sample project, a recorded checkout with its checks and Playwright test.

The first 10 paying customers get 30% off for as long as they stay subscribed (applied automatically, offer ends 31 Dec).

I read and answer every comment, harsh ones included. When your UI changes, what breaks first in your suite: locators, test data or the flow itself?

no LLM writing the code and same recording = same output is the reason i'd try it, flaky generated tests are worse than no tests at all

on your question abuot what breaks first, my guess is locators most of the time. when a button moves into a new component, can you fix the locator file once and every spec picks it up??? or is it a re-record of the flow???