You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: extension/templates/platforms/web.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -422,8 +422,7 @@ The engine resolves the chain: `enter_dashboard` extends `login` → executes lo
422
422
2.**`extends` chains** — a setup can extend another setup (max 3 levels deep to keep it simple)
423
423
3.**No circular references** — `A extends B extends A` is invalid (engine will reject it)
424
424
4.**setup + flow interaction** — in flow mode, setup steps are included in scenario 1 but skipped (along with navigate) in subsequent scenarios
425
-
5.**Each setup MUST end with a verification step** (`assert_text` or `screenshot`) to confirm the path succeeded
426
-
425
+
5.**Each setup MUST end with a verification step** (`assert_text` or `screenshot`) to confirm the path succeeded6. **Checkpoint recovery (v14.14)**: When a step fails and the engine needs to recover, it automatically re-executes the scenario's `setup` steps to restore the app to the correct page, then retries the failed step. This means: **a scenario with a well-defined `setup` is self-healing**. A scenario WITHOUT a setup cannot recover — the engine can only use AI screenshot coordinates as a fallback. MANDATORY: any scenario that navigates through 2+ steps (login → click module → reach target page) MUST use `setup` to define that path.
0 commit comments