Skip to content
RED SAGSkills
hardAutomation Test Engineer interview question

Your company has 2,000 Selenium tests and wants to move to Playwright. How would you plan the migration?

What the interviewer wants to hear

  • Clarify the reason and success criteria
  • Pilot on a slice and compare results
  • Run both side by side; new tests in the new tool
  • Migrate by value, delete or push down low-value tests
  • Train the team and keep shared patterns and reports

Model answer

I would start with why. If the goals are less flakiness and faster runs, I define measurable targets, such as flake rate and suite duration. Then I run a pilot: migrate one important area, maybe 50 tests, and compare speed, stability and effort with the Selenium version. If it pays off, I avoid a big-bang rewrite. Both suites run side by side in CI, all new tests are written in Playwright, and old tests are migrated in order of value and pain, starting with the flakiest critical journeys. Many old UI tests should not be migrated at all; they can be deleted or replaced by API tests. I set up shared fixtures, page objects and reporting first so the new code is consistent, and I pair with team members to train them. The Selenium suite is retired once coverage is matched.

Can you answer it under time pressure?

Take a timed hard round and get scored on every answer.

Start mock interview

More hard Automation Test Engineer questions