# 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


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.drizz.dev/test-plan/test-plan-healing-and-auto-retry.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.