Why our team chose to stay with Selenium instead of migrating — and we do not regret it

Every few months someone on our team brings up migrating to Playwright. We've evaluated it twice now and decided to stay on Selenium. Here's the honest reasoning: **Our constraints:** - Large Java codebase — entire test infra is Java, and our SDETs know Java deeply - Enterprise environment — Playwright's Node.js runtime adds a dependency management problem - Existing investment in a custom Selenium framework with 4 years of company-specific utilities **What Playwright offers that we're missing:** - Better auto-waiting (we work around this with explicit waits) - Trace viewer (we use Allure reports and they're sufficient) Migrations have real costs that don't show up in blog posts. If your team is deep in Java, Selenium 4 with the new CDP-based features is a solid, stable choice.