AAWEA.ORG

E2E Until Green

Run end-to-end tests, fix UI and integration failures, and loop until the E2E suite passes.

👁 1,560 views 📥 1,067 installs 👤 by loops!

Manual start

↓

1

Run E2E

Run the project's E2E test command and capture failures.

> npm run test:e2e
2

Fix failures

Fix the smallest root cause for failing E2E specs. Prefer stable selectors and realistic waits.
3

Re-run E2E

Re-run E2E until all specs pass.

> npm run test:e2e

↓

✓

Exit condition: tests_pass

E2E suite exits 0

> npm run test:e2e

📊 Flow Diagram

flowchart TD Start(["Manual start"]) Start --> S0 S0("Run E2E") S1("Fix failures") S0 --> S1 S2("Re-run E2E") S1 --> S2 Exit{"E2E suite exits 0"} S2 --> Exit Exit -- "No" --> S0 Exit -- "Yes" --> Done(["Success"]) style Exit fill:#fffbeb,stroke:#f59e0b,stroke-width:2px,color:#92400e style Done fill:#ecfdf5,stroke:#10b981,stroke-width:2px,color:#065f46

Run "E2E Until Green" in your agent

Prompt only

Deeplinks and "Open in Cursor" only paste the kickoff prompt. They do not install hook files — your agent cannot tell whether files are on disk until you add them yourself.

Two separate pieces

Kickoff prompt — tells the agent the goal, check command, exit condition, and how to self-pace.

Kickoff prompt

Start the "E2E Until Green" loop.

Goal: E2E suite passes
Max iterations: 10
Between iterations run: npm run test:e2e
Exit when: E2E command exits 0

Step 1: Run E2E tests. Fix the first failing spec, then repeat.

Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

Anti-gaming rules

Rules the agent must follow so it cannot cheat the exit condition.

Do not modify the check command or exit criteria to force success
Do not skip, disable, or bypass checks to pass the exit condition
If stuck after several iterations, stop and report blockers instead of gaming metrics