Playwright Interview Questions and Answers for Automation Testers

Dynamic content is handled using locator assertions, network waiting, and proper synchronization rather than manual delays.

Common issues include using static waits, relying on brittle selectors, sharing test data, and depending on execution order.

Locator-based assertions are preferred because they auto-wait and stay connected to the DOM. Raw value checks are more fragile and timing-dependent.

Playwright assertions automatically retry until the condition is met or a timeout occurs. This makes them more reliable than immediate value comparisons.

Instead of using static waits or sleep, Playwright encourages using locator-based assertions with expect. This waits dynamically until the expected condition is met.

Playwright provides frame-specific locators to interact with elements inside iframes. Handling frames explicitly avoids flaky behavior caused by context switching.

Resilient locators use roles, accessible names, text, or test IDs. These are more stable than CSS or XPath selectors, which often break when UI structure changes.

Auto-waiting ensures that elements are visible, enabled, and stable before any action or assertion is performed. This removes the need for explicit waits and reduces flaky failures caused by timing issues.

Locators are Playwright’s core abstraction for finding and interacting with elements. They automatically wait for elements to be ready and re-query the DOM, which makes tests more stable than traditional selectors.

Retries can mask flaky tests instead of fixing the root cause. A better approach is improving locators, waits, and test isolation.

Retries can be configured in the Playwright config or per test. They automatically rerun failed tests to handle transient issues.

By default, test files run in parallel, while tests within a file run sequentially unless configured otherwise.

Playwright uses a worker-based model where test files run in parallel by default, each in an isolated browser context.

Tests are typically organized into spec files, shared fixtures, utility helpers, and page objects. This structure improves readability, reusability, and long-term maintenance of the automation framework.

Headless or headed mode can be configured globally or overridden via CLI. The baseURL is defined in config so tests can use relative paths, improving readability and making environment switching easier.

Projects allow you to define multiple test environments within the same test suite. For example, you can create projects for Chromium, Firefox, mobile viewports, or different user roles. This avoids duplication and improves coverage.

The playwright.config file controls how tests run. Common configurations include browser projects, baseURL, timeouts, retries, reporters, parallel workers, screenshots, videos, and trace settings. Centralized configuration helps maintain consistency across environments.

The HTML reporter generates a detailed test report and opens automatically after local runs, showing failures, traces, and artifacts.

Traces can be enabled conditionally in config to capture data only for failed retries, keeping CI runs efficient.

Trace Viewer captures screenshots, DOM snapshots, network activity, and actions. It allows replaying failed tests visually.

Playwright Inspector allows step-by-step execution, live DOM inspection, and locator validation during test runs.

Custom fixtures can be created by extending the base test and adding setup logic such as login steps. This avoids repeating login code across tests.

Fixtures are more flexible, composable, and scoped compared to traditional hooks. They allow dependency injection rather than shared mutable state.

Each test gets its own isolated environment by default. This ensures that actions in one test do not affect others, making parallel execution safer.

Fixtures provide a clean way to set up and tear down test dependencies such as pages, contexts, or test data. They improve reuse and enforce test isolation.

Playwright is an open-source automation framework developed by Microsoft for end-to-end testing of web applications. Teams choose Playwright because it offers built-in auto-waiting, fast execution, reliable locators, parallel execution, and strong debugging tools. Unlike older tools, Playwright reduces flaky tests and works consistently across modern browsers.

Compared to Selenium, Playwright offers auto-waiting, modern locator strategies, faster execution, and better isolation using browser contexts. Testers focus less on manual waits and more on validating user behavior, which improves test reliability and speed.

Playwright Test is the built-in test runner that comes with Playwright. It includes test discovery, expect assertions, fixtures, hooks, parallel execution, retries, reporters, and powerful debugging tools like Trace Viewer and Playwright Inspector. This removes the need for external runners.

Playwright supports Chromium, Firefox, and WebKit, enabling true cross-browser testing. It runs on Windows, macOS, and Linux, and supports both headless and headed execution. This makes it suitable for local development and CI environments.