> For the complete documentation index, see [llms.txt](https://docs.drizz.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drizz.dev/test-plan/test-plan-healing-and-auto-retry.md).

# Test Plan Healing & Auto-Retry

Drizz Test Plans include an intelligent, built-in healing framework designed to deliver **high-reliability test execution** even when applications exhibit transient or inconsistent UI behavior.\
The system automatically detects anomalies, re-validates steps, and retries flows to maintain consistency and reduce false failures.

### **Automatic Retry Mechanism**

Whenever a failure is detected, Drizz automatically re-executes the test file once more. This controlled retry mechanism helps teams distinguish between genuine defects and incidental instability.

**Auto-retry ensures:**

1. **Reduced flakiness** from temporary UI delays, slow loads, or minor rendering gaps
2. **Clear differentiation** between consistent failures and environment-specific anomalies
3. **Improved root-cause analysis (RCA)** by identifying steps that fail deterministically
4. **Higher accuracy in reporting**, improving signal-to-noise ratio for failures

### **Why Auto-Retry Matters**

1. **Stabilizes long and complex flows** where intermediate screens may render inconsistently
2. **Minimizes false negatives**, resulting in more reliable build pipelines
3. **Isolates true functional regressions** from incidental or timing-based variances
4. **Ensures production-grade reliability**, allowing teams to ship with confidence
5. **Improves CI/CD trustworthiness**, reducing manual re-runs and triage fatigue