Should your team still be using Selenium?, Selenium Senior

Should your team still be using Selenium?

Every Selenium team faces this question. Here is how to answer it fairly, in both directions.

What you'll learn

How to answer whether a team should still use Selenium
What Selenium's reach buys, and what it costs
How to make the case in either direction

If you work with Selenium, someone will eventually ask why you are not using Playwright or Cypress. It might be a developer, a new manager, or a candidate in an interview. You need a real answer, not a defensive one.

Let me give you both sides.

Selenium is still the right choice when:

Your team does not write JavaScript. Selenium has proper support for Java, Python, C# and Ruby. A Java team will maintain a Java suite far better than a JavaScript one they are uncomfortable in. This is the single strongest reason, and it is a good one.
You need browsers or platforms other tools do not reach, including older browsers some enterprise customers still use.
You have a large, working suite. A suite that catches real bugs today has value that a rewrite would destroy for months.
Your organisation needs a W3C standard tool with long-term support. In regulated industries this is sometimes a hard requirement, and Selenium's age and standardisation are advantages.

members only

Keep reading with the full course

The Foundations track and the first 5 lectures of each framework are free. This lecture is part of the paid course, which unlocks every lecture, all three frameworks, and downloads.

See the options →