Playwright Interview Questions

Why would you migrate from Selenium to Playwright?

How do Playwright fixtures, projects and auto-waiting change framework design?

Fixtures replace base classes for setup, projects replace testng.xml for browser/environment matrices, and web-first assertions with auto-waiting remove most explicit wait code.

How does Playwright auto-waiting differ from Selenium waits?

Playwright checks actionability (attached, visible, stable, enabled, receives events) before every action and retries until the timeout, so explicit waits are rarely needed.

Which locators do you prefer in Playwright and why?

Role-based and label-based locators first (getByRole, getByLabel), then getByTestId; raw CSS/XPath last because they couple tests to markup.

How do you reuse authentication instead of logging in per test?

Log in once in a setup project, save the session with storageState, and load that state in the config so each test starts signed in.

How do you mock or intercept network calls in Playwright?

page.route intercepts matching requests so you can fulfil them with fixtures, abort them, or modify the response — ideal for error states and third-party isolation.

How do you debug a test that only fails in CI?

Turn on trace, video and screenshot on first retry, download the artifact and open the trace viewer — it replays DOM snapshots, network, console and the action timeline.

How does parallelism work in Playwright, and how do you scale it in CI?

Playwright runs files in parallel across worker processes, each with its own browser context; scale further by sharding the suite across CI machines and merging the reports.

What is locator strategy, and why does it matter in Playwright?

locator strategy is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply locator strategy in a production Playwright project?

Apply locator strategy through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is auto-waiting, and why does it matter in Playwright?

auto-waiting is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply auto-waiting in a production Playwright project?

Apply auto-waiting through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is web-first assertions, and why does it matter in Playwright?

web-first assertions is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply web-first assertions in a production Playwright project?

Apply web-first assertions through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is browser contexts, and why does it matter in Playwright?

browser contexts is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply browser contexts in a production Playwright project?

Apply browser contexts through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is fixtures, and why does it matter in Playwright?

fixtures is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply fixtures in a production Playwright project?

Apply fixtures through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is projects, and why does it matter in Playwright?

projects is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply projects in a production Playwright project?

Apply projects through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is parallel execution, and why does it matter in Playwright?

parallel execution is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply parallel execution in a production Playwright project?

Apply parallel execution through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is test retries, and why does it matter in Playwright?

test retries is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply test retries in a production Playwright project?

Apply test retries through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is trace viewer, and why does it matter in Playwright?

trace viewer is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply trace viewer in a production Playwright project?

Apply trace viewer through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is screenshots and videos, and why does it matter in Playwright?

screenshots and videos is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply screenshots and videos in a production Playwright project?

Apply screenshots and videos through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is network interception, and why does it matter in Playwright?

network interception is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply network interception in a production Playwright project?

Apply network interception through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is APIRequestContext, and why does it matter in Playwright?

APIRequestContext is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply APIRequestContext in a production Playwright project?

Apply APIRequestContext through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is authentication state, and why does it matter in Playwright?

authentication state is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply authentication state in a production Playwright project?

Apply authentication state through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is page object models, and why does it matter in Playwright?

page object models is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply page object models in a production Playwright project?

Apply page object models through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is component testing, and why does it matter in Playwright?

component testing is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply component testing in a production Playwright project?

Apply component testing through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is frames, and why does it matter in Playwright?

frames is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply frames in a production Playwright project?

Apply frames through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is popups and downloads, and why does it matter in Playwright?

popups and downloads is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply popups and downloads in a production Playwright project?

Apply popups and downloads through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is file uploads, and why does it matter in Playwright?

file uploads is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply file uploads in a production Playwright project?

Apply file uploads through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is geolocation and permissions, and why does it matter in Playwright?

geolocation and permissions is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply geolocation and permissions in a production Playwright project?

Apply geolocation and permissions through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is mobile emulation, and why does it matter in Playwright?

mobile emulation is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply mobile emulation in a production Playwright project?

Apply mobile emulation through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is visual comparisons, and why does it matter in Playwright?

visual comparisons is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply visual comparisons in a production Playwright project?

Apply visual comparisons through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is clock mocking, and why does it matter in Playwright?

clock mocking is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply clock mocking in a production Playwright project?

Apply clock mocking through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is test sharding, and why does it matter in Playwright?

test sharding is a core Playwright concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply test sharding in a production Playwright project?

Apply test sharding through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.