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.
The 'no LLM writes the code, same recording = same output' line is what sold me — I've been burned by flaky AI-generated tests that change every run. For me it's usually the locators that break first when a button moves, so having each locator live once in a file I can edit like normal code is the part I'd actually use. Going to try the free converter on one of my own flows and see how clean the page objects come out.
Generating a complete Playwright project from recorded flows is really useful. When the UI changes, can Blendra update existing assertions and page objects without requiring developers to rebuild the test?
congrats on the launch blend. to your question, i think the flow breaks first more than locators. one new step in onboarding and the whole recorded path is wrong -> locators you can fix in one file like you said. can i re record only one step instead of the full flow?
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???
About Blendra on Product Hunt
“Record a flow once and get a Playwright test project you own”
Blendra launched on Product Hunt on November 12th, 2026 and earned 72 upvotes and 9 comments, placing #34 on the daily leaderboard. 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.
Blendra was featured in Chrome Extensions (52.9k followers), Software Engineering (43.3k followers) and Developer Tools (523.2k followers) on Product Hunt. Together, these topics include over 119.1k products, making this a competitive space to launch in.
Who hunted Blendra?
Blendra was hunted by Blend Emini. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Blendra stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
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:
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?