testdriverredrawlisted

<!-- Generated from redraw.mdx. DO NOT EDIT. --> ## Overview The redraw system waits for the screen to stabilize after an interaction before continuing. It detects when animations, page loads, and network requests have settled, preventing actions from being performed on a changing screen. <Note> **Redraw is disabled by default since v7.3.** Enable it explicitly if your tests interact with applications that have significant animations or loading states. </Note> ## How It Works Redraw uses a **two-phase detection** approach: 1. **Change Detection** — Compare the current frame to the initial screenshot taken right after the action. If the pixel diff exceeds 0.1%, the screen has changed. 2. **Stability Detection** — Compare consecutive frames using z-score analysis. When the diff between frames drops below 0.1% or the z-score is negative (current diff is below average), the screen has settled. The screen is considered **settled** when both phases complete: the screen changed from the initial state AND consecutive frames 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 traffic w