Auto-E2E

The problem

Today's tools draw the arrow from the wrong end

Every team that automates end-to-end testing ends up with the same four pains. None of them is about the framework.

Today's tools The product lives in 2–3 heads someone clicks Recorded clicks or AI-written steps generate · heal Test files become the only spec ✗ break when a button moves This project owner corrects The product code · docs · owners Feature map what it does + depends on Scenario tree how it's used, per feature Tests, any form playwright · selenium · …
Recorders, generators and self-healing locators all start from the click. They are ledgers of tests. The question of which tests, and why, stays in the heads of the two or three people who know the product.
2–3 people know how it should work

They are the authority — and have no time to keep an inventory of features and scenarios.

The script became the spec

A moved button breaks the only written record of the requirement.

Feedback arrives at the release

Days after the developer moved on — the dependency was knowable at the merge request.

Tools optimise the wrong layer

Cheaper tests, same blind spot: nobody knows what to test.

A real case

At a company we work with, users who registered with email + password landed on "Sign-in cancelled". The real state was "email not verified". Nobody had written the scenario registered → not yet verified → allowed in, so there was no test and no screen for it. The product lead found it by asking an AI to walk through the flow and record it — a scenario tree, drawn by hand, once, after the fact.

When you find out

The break is visible at the merge request. Today it is found at the release.

Today task MR merge release weekly E2E found here, days later With the map task MR merge release E2E confirms caught at the MR ↑ scenarios drafted here
Analysis moves to the merge request. The map already exists, so the model never rediscovers the product per run; dependency breaks surface at the MR, not at the weekly release.

Sound familiar?

Tell us which of the four you have. That conversation is how we pick the first teams.

Get early access See how it works