Playwright Testing Interview Questions for Top Product Companies (₹50+ LPA)

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

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

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

Log in with request.post, call request.storageState(), and create a browser context using that state.

POST the query and variables as JSON to the single endpoint and assert both data and errors fields in the response.

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.

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.

User-facing ones: getByRole, getByText, getByLabel, getByPlaceholder and getByTestId, which are more resilient than CSS or XPath.

Both describe object shapes. Interfaces can be extended and merged; type aliases can also describe unions and primitives. Use interfaces for page or test-data shapes, types for unions.

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

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

Capture the download event, save it with download.saveAs, then read the file in Node and assert on name, size or content.

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.

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

A short function syntax that does not have its own this and arguments, taking them from the surrounding scope.

obj?.a?.b safely reads nested properties and returns undefined instead of throwing if something in the chain is missing.

Send invalid payloads or missing auth and assert 400, 401 or 404 codes and the error message bodies.

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

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

Named configurations that run the same tests across different browsers, devices or environments.

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

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

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

Tag tests (in the title or with { tag: '@smoke' }) and run: npx playwright test --grep @smoke (use --grep-invert to exclude).

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

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

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

In a fixture or beforeEach, call the API (request.post) to create the user or order, use it in the UI test, then delete it in teardown. It is faster and more reliable than creating data through the UI.

Register page.on('dialog', d => d.accept()) before the action triggers the dialog.

Use environment variables or .env files, a baseURL in config, API calls for setup and cleanup, and unique data per run.

Functions that take other functions as arguments or return them, such as map, filter and reduce, or a helper that wraps retry logic around a test step.

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

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

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

A Locator is lazy, re-resolved on every action and auto-waits (recommended). An ElementHandle points to one DOM node and can go stale.

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

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

Use request.post with multipart: { file: { name, mimeType, buffer } } and assert the response and stored file details.

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

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

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

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.

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

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

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

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

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.

Use try-catch with await, or .catch() on promises, and make sure rejected promises are never left unhandled.

waitForSelector is a lower-level wait; locator assertions are preferred as they retry and are more readable.

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.

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

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

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.

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.

Both describe the shape of data. Interfaces are extendable and suit object contracts; type aliases can also model unions and primitives.

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

Log in once in a setup project, save storageState to a file and reuse it in other projects or tests.

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.

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

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.

TypeScript adds static types on top of JavaScript and compiles to it. Types catch errors early and give better autocomplete, which helps in larger test suites.

const [newPage] = await Promise.all([ context.waitForEvent('page'), page.getByText('Open').click(), ]); await newPage.waitForLoadState();

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

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.

Files run in parallel by default; set workers in the config and use test.describe.configure({ mode: 'parallel' }) for tests inside a file.

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

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

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

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.

Fetch tokens in a fixture with expiry tracking and refresh it when it is about to expire, keeping tests unaware of the details.

undefined means a variable has not been assigned; null is an intentional empty value.

A function that remembers variables from its outer scope even after that scope has finished. They are used for private state and factory helpers.

Use page.frameLocator('#frame').getByRole(...) so actions work inside the iframe with auto-waiting.

Assertions like expect(locator).toBeVisible() that retry until they pass or time out, unlike one-off checks.

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

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