Testing·Advanced·Conceptual·1 min read
What are the main sources of e2e flakiness and how do you address them?
Short interview answer
Timing (fixed waits instead of waiting on state), unstable selectors (CSS or DOM structure), shared or leftover test data, animations, and real network variance. Fixes: condition-based waits, role or dedicated test-attribute selectors, per-test data isolation, disabling animation, and controlling or stubbing volatile dependencies.
Key takeaway
Explain the underlying mental model clearly, then support it with a concrete example and its trade-offs.