This resonates. Frontend testing often feels inverted high unit coverage but low confidence, then e2e tests that introduce flakiness and maintenance overhead. The gap between component correctness and real user behavior is where most bugs hide, yet bridging it without brittle selectors and timing hacks is hard. Your example highlights the core issue: when synchronization becomes guesswork, tests stop validating behavior and start fighting the framework. A pragmatic, layered strategy fewer but higher-value e2e flows, strong integration tests around critical boundaries, and disciplined test IDs tends to scale better than chasing coverage. You’re not alone in this frustration it’s less about perfection and more about optimizing for signal over noise.