testdriverredrawlisted

<!-- Generated from redraw.mdx. DO NOT EDIT. --> ## Overview The redraw system waits for the screen to become stable after an interaction. Then it continues. It finds when animations, page loads, and network requests are complete. This stops actions on a screen that changes. <Note> **Redraw is disabled by default from v7.3.** Enable it if your tests interact with applications that have many animations or load states. </Note> ## How It Works Redraw uses a **two-phase detection** method: 1. **Change Detection**. TestDriver compares the present frame to the first screenshot from after the action. If the pixel diff is more than 0.1%, the screen changed. 2. **Stability Detection** — TestDriver compares frames that come after each other with z-score analysis. When the diff between frames is less than 0.1%, or the z-score is negative (the present diff is less than the average), the screen is complete. The screen is **complete** when both phases finish: the screen changed from the first state AND the frames that come after each other are now stable. ```mermaid flowchart TD A[Action performed] --> B{Phase 1: Change Detection\ndiffFromInitial > 0.1%?} B -- "Yes (screen changed)" --> C{Phase 2: Stability\nz-score < 0 or\ndiffPercent < 0.1%?} C -- "Yes (frames stable)" --> D[Screen settled ✓] B -- "No (waiting...)" --> B C -- "No (waiting...)" --> C ``` ### Polling The system polls at **500ms intervals**, comparing screenshot frames. This reduces WebSocket