Playwright Testing Interview Questions for Experienced Professionals (₹10–12 LPA)

Synchronous code runs line by line and blocks; asynchronous code starts a task and continues, handling the result later with promises or await.

Separate tests, page objects, fixtures, utilities, test data and config; use tags, projects, shared auth setup, linting, code review and a CI pipeline with sharding and reports.

Integrate axe-core through @axe-core/playwright, run an analysis on the page and assert that there are no violations.

JavaScript runs one call stack and uses queues for async work; the event loop pushes callbacks from the microtask (promises) and task queues when the stack is empty.

beforeEach runs the same code before every test in scope; fixtures are lazy, composable and only set up what a test uses.

map transforms each item, filter keeps items that match a condition, and reduce combines all items into a single value.

Create a class that takes a page, defines locators as properties and exposes action methods; instantiate it in a fixture for clean tests.

await page.route('**/api/users', route => route.fulfill({ status: 200, json: [{ id: 1, name: 'Test' }] }) );

The action runs without waiting, so the next step may run first — causing flaky failures or 'Target closed' errors. The @typescript-eslint/no-floating-promises rule catches it.

all waits for every promise and rejects on the first failure; allSettled waits for all and reports each outcome; race settles with the first one to finish.

Run npm init playwright@latest, which sets up config, example tests and browsers; execute with npx playwright test.

Record timestamps around the request or use response timing, then assert the duration is under an agreed threshold.

npx playwright codegen records user actions and generates test code with suggested locators, handy for starting tests.

It records screenshots, DOM snapshots, network calls and actions per step so you can replay a failed run and see exactly what happened.

The object behind the request fixture that holds base URL, headers and cookies, and can share cookies with a browser context.

Run in parallel with sharding, reuse authentication state, set up data through APIs, avoid unnecessary waits, run smoke on every commit and the full suite nightly.

npx playwright test tests/login.spec.ts, add -g "test title" to match a name, or use test.only while debugging.

Set retries in the config or CLI and failed tests re-run in a fresh context, with trace recorded on first retry to diagnose flakiness.

Use the request fixture: const res = await request.get('/api/users'); expect(res.ok()).toBeTruthy(); const body = await res.json();

API testing checks services directly and is fast and stable; UI testing checks the full user experience in the browser and is slower.

string, number, boolean, null, undefined, symbol, bigint and object (including arrays and functions).

Auto-waiting, a built-in test runner, Chromium/Firefox/WebKit with one API, network interception, the trace viewer and parallel runs out of the box — usually faster and less flaky.

await expect.soft(locator).toHaveText('...') records the failure but lets the test continue, so you see every mismatch in one run.

Define an interface for the payload, cast or validate the parsed JSON to it (for example with zod), and use that type in assertions to catch shape changes.

setInputFiles on the input for uploads; for downloads wait on page.waitForEvent('download') and save or inspect the file.

Placeholders for types that make reusable code type-safe, for example a helper function returning the same type of item that it receives.

Use page.route to intercept the call and fulfil it with fixed JSON so tests do not depend on external systems.

await request.post('/api/users', { data: { name: 'Asha' } }) automatically sets JSON headers and serialises the payload.

Add tags in the title (@smoke) or use the tag option, and run with --grep @smoke or --grep-invert.

Read the next page link or IDs from earlier responses, loop until done and assert counts and uniqueness; pass IDs between calls in the same test.

Log in once in global setup, save storageState to a JSON file and set use.storageState in the config so every test starts logged in.

Assert the status with expect(res.status()).toBe(200), parse res.json() and check fields, using schema validation for the structure.

Use dotenv files per environment, read them in playwright.config and set baseURL and credentials from variables, selecting with an ENV flag.

Use the official Playwright image which contains browsers and dependencies, mount the project and run npx playwright test for consistent CI environments.

Cover happy path, validation errors, auth and permissions, boundary values, idempotency, schema, performance and data cleanup.

A browser is the engine instance; a context is an isolated session (cookies, storage); a page is a tab inside a context.

Scripts that run once before or after the whole run, for seeding data, starting services or creating authentication state.

click simulates a real user click with actionability checks; dispatchEvent fires a DOM event directly without those checks.

Wait for the popup event with const [popup] = await Promise.all([page.waitForEvent('popup'), page.click('a')]), then interact with popup.

Reusable setup/teardown units injected into tests (page, context, request). You can extend test with custom fixtures such as loggedInPage.

page.route('**/api/items', route => route.fulfill({ json: [...] })) intercepts and replies with test data; route.abort() simulates failures.

Use timeout and expect.timeout in config, test.setTimeout() for one test and test.slow() for known slower tests.

Use npx playwright test --shard=1/4 in each CI job and merge reports afterwards to reduce total run time.

npm is the Node package manager. package.json lists the project's dependencies and scripts, such as the command that runs the tests.

An open-source end-to-end testing framework from Microsoft that automates Chromium, Firefox and WebKit through one API, in multiple languages.

Use device descriptors such as devices['iPhone 13'] in a project config to emulate viewport, user agent and touch.

A type alias describes a shape or union of values; an enum creates a named set of constants that exists at runtime.

Install the allure-playwright reporter, add it in the config reporters array and generate the report from the allure-results folder in CI.

Use a library such as zod or ajv to define the expected schema and parse the response to fail on missing or wrongly typed fields.

Set extraHTTPHeaders in the config or pass headers per request, for example Authorization: Bearer token fetched in a setup step.

locator.hover() and locator.dragTo(target) perform these actions, with auto-waiting for actionability.

Fixtures set up and tear down test dependencies. Extend with test.extend({ loggedInPage: async ({ page }, use) => { ...; await use(page); } }).

page.screenshot() for captures and config options use: { screenshot: 'only-on-failure', video: 'retain-on-failure' } for automatic evidence.

Syntax over Promises: an async function returns a Promise and await pauses until it resolves. Every Playwright action returns a Promise, so you await each step.

await expect(page).toHaveScreenshot('home.png') compares against a baseline image; tune maxDiffPixels and mask dynamic areas like dates.

Set them in the context options (geolocation, permissions, timezoneId, locale) to simulate users from other regions.

Declarations of var and functions are moved to the top of their scope at compile time; let and const are hoisted but stay in the temporal dead zone until declared.

Playwright locators pierce open shadow roots by default, so getByRole and CSS locators work without special handling.

var is function-scoped and hoisted. let and const are block-scoped; const can't be reassigned (though an object it points to can change). Prefer const, then let.

Strings in backticks that allow embedded expressions like `Hello ${name}` and multi-line text, useful for building dynamic locators and URLs.

Playwright supports multiple browsers, tabs, languages and has auto-waiting and tracing; Selenium has the widest ecosystem; Cypress runs in-browser with a great UI but has more limits across tabs.

Create test data through API calls, verify it in the UI and clean up via API, which makes UI tests faster and more reliable.

Define projects for chromium, firefox and webkit in playwright.config.ts, set workers, then run: npx playwright test

Before acting, Playwright waits for the element to be attached, visible, stable, enabled and able to receive events — so manual waits are rarely needed.

Destructuring pulls values from arrays or objects into variables; spread expands an array or object into another, useful for copying and merging config.

Rely on auto-waiting plus a web-first assertion on the final state, disable animations in config for tests and avoid fixed timeouts.

An object describing how to find an element, re-evaluated on every action so it always targets the current DOM.

Use page.waitForResponse(res => res.url().includes('/api/orders') && res.ok()) together with the action that triggers it.

A class receives page in its constructor, stores locators as properties and exposes actions like login(user, pass). Tests call page objects, not raw locators.

Click to open the control, then use getByRole('option') or a text locator for the target item, instead of relying on fragile index-based selectors.