Self-healing
Self-healing lets Mavster recover from a failed step by planning and executing recovery actions. Three modes, an Ultra-tier gate, and per-step opt-in.
When a step fails, Mavster's default behavior is to stop the test (or fall through to a "run on failure" branch if you've defined one). Self-healing is an opt-in alternative: Mavster's AI plans a few recovery actions and tries to execute them so the original step can be retried.
Self-healing is gated to the Ultra tier. Non-Ultra users see the control as a yellow lock chip with the tooltip "Self-healing is an Ultra feature — click to upgrade". Your chosen mode is preserved on the test even when locked, so an upgrade restores your preference.
The three modes
The mode is set via the chip in the test header. Display names and one-line descriptions:
| Mode | Display name | Description |
|---|---|---|
| Off | Strict | "Fail immediately on any unexpected UI" |
| Per Step | Per Step | "Heal only on steps with healing enabled" |
| Full Test | Full Test | "Attempt to recover any step that fails" |
Strict
Default. Self-healing is off; failures fail the test. Use for stable tests that should never auto-recover.
Per Step
Self-healing is opt-in per step. Only steps you've enabled with the per-step toggle will be healed; others fail strictly. The right choice when you want to grant healing to specific risky steps without giving it to everything.
Full Test
Every top-level step in the test is eligible for healing. The per-step toggle is locked on. Use for end-to-end tests where any step might be flaky and you want maximum recovery.
What happens when a step heals
When a step fails and healing is allowed, Mavster's AI tries a few recovery actions and then retries the original step. The outcome is one of:
- Healed — the retry succeeded; the test continues.
- Exhausted — recovery attempts ran out without the step passing; the test hard-fails.
Each healing incident is recorded against the test run for triage, including which step failed and a short reasoning summary.
When to enable healing
- Use Strict for happy-path tests that you want to be informative when they break — auto-healing can mask real regressions.
- Use Per Step for known-flaky steps in an otherwise stable test (e.g. a step that hits a third-party widget).
- Use Full Test for monitoring suites where the goal is "did the whole flow ever work end-to-end" rather than "did each individual step pass first try".
Tier gating
Without an Ultra subscription, the chip renders locked. Tapping it opens the upsell sheet. A non-Ultra user always gets strict behavior at run time, regardless of how the project's self-healing mode is set.