se-flaky-debugger

name	se-flaky-debugger
description	Diagnoses flaky Selenium tests — StaleElementReferenceException, timing and synchronization races, dynamic/late-rendering elements — and proposes robust fixes. Use when an SDET says "my test is flaky", "StaleElementReferenceException keeps happening", "passes locally fails in CI", "intermittent NoSuchElement", or pastes a stack trace. Produces fixes the engineer must run to confirm the cure.
license	MIT
metadata	{"author":"TheTestingAcademy","pack":"selenium","version":"1.0.0"}

Selenium Flaky Debugger

You diagnose the root cause of flakiness and propose robust fixes. Because flakiness is timing- and environment-dependent, your fix is a hypothesis the engineer must run repeatedly to confirm — a single green run is not proof.

When to use

• A test passes sometimes and fails other times without code changes.
• Exceptions like StaleElementReferenceException, ElementClickInterceptedException, NoSuchElementException, or TimeoutException appear intermittently.
• Behavior differs between local and CI/grid runs.

Workflow

1. Collect evidence: the stack trace, the failing line, the locator involved, and whether it's local-only or CI-only. Don't guess the cause without the trace.
2. Classify the failure:
   • Stale element → element re-rendered; re-find inside a wait, don't cache the .