test(e2e): drive the onboarding chain in a real browser

[basb7]

The first end-to-end test, and the first test in this repository that exercises a screen at all.

What it does

One test, the whole chain: register → create an organization → create a project → create an environment → load /dashboard/environments cold and find it there.

Deliberately not four independent tests. The chain working is the thing that broke; four tests that each build their own state would stop testing it.

Proven to fail, not just to pass

Reintroducing the original defect — dropping refreshCapabilities() from the tenant refresh() — turns it red on exactly the step that asserts a fresh admin is offered a project rather than told they lack access:

✘ a new account can register and walk the whole chain
  Error: expect(locator).toBeVisible() failed — element(s) not found

Restored, green again.

A test whose failure has never been observed is a claim, not a check.

Worth knowing for anyone doing this next: the frontend container has no source mount. A source change needs docker compose -f compose.dev.yml up -d --build frontend before the test sees it. The first mutation attempt appeared to prove the test didn't catch the bug — it had simply never reached the running app.

No data-testid anywhere

Every selector is getByRole / getByLabel / getByText. That discipline paid immediately: the first run hit a strict-mode violation because an environment name appears both as a badge and as an option in the environment filter. A CSS-class selector would have silently picked one.

Two accessibility gaps surfaced the same way, by the test having nothing to grab: the copy-API-key button has no accessible name, and the registration error banner has no role="alert". Both are fixed in the follow-up, not here.

CI

A third job, E2E (onboarding chain). The two existing jobs are untouched, and that is not stylistic: main's ruleset requires Backend (lint + tests) and Frontend (lint + build) by exact name, so renaming either makes it unsatisfiable and blocks every merge in the repository. npm test still runs node --test.

The new job is not in the ruleset, which is intentional — an end-to-end test should earn the right to block merges before it does.

Running the real stack

docker compose -f compose.dev.yml up -d from the repo root. Global setup polls the API first and fails naming that command, rather than timing out on a selector twenty seconds later.

Leftover data — stated, not solved

Each run leaves an account, organization, project and environment in the development database. No teardown, on purpose: tearing down means driving the delete-confirmation dialog, doubling the test's surface for no coverage, and a failed run's leftovers are exactly what you want to inspect. Everything a run creates shares one id, so a run's debris greps as a unit. CI ends with docker compose down -v.

Verification

npm run test:e2e     1 passed
npm test             16 passed (unchanged)
npm run lint         clean
npm run build        compiled
pytest               592 passed, zero .py files touched

🤖 Generated with Claude Code