lecture 14 of 160 completed

Should you migrate, and how would you do it?

Five thousand tests and a proposal to switch tools. The highest-stakes decision these teams face, and it is usually decided badly.

What you'll learn

  • Which problems a migration does not solve
  • What a migration really costs
  • How to sequence one without a coverage gap

"Should we move to Playwright?" You will be asked this, and the quality of your answer is a senior signal in itself. Most teams decide it on enthusiasm in one direction or inertia in the other.

Start by naming the actual problem. "Selenium is old" is not a problem. These are:

  • The suite takes four hours and blocks releases.
  • Tests are flaky and the team has stopped trusting them.
  • Writing a test takes a day because the framework is unusable.
  • We cannot test the flows that matter (multi-tab, network state).
  • We cannot hire; every candidate wants to work with modern tooling.

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 →