Playwright Testing Interview Questions for Mid-Level Roles (₹8–10 LPA)

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.

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

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

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.

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

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

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

Turn on trace: 'on-first-retry', open the trace viewer, check network and timing, replace hard waits with web-first assertions, isolate test data and check for sharding conflicts.

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

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

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

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

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.

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

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

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.

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

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

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

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 a library such as zod or ajv to define the expected schema and parse the response to fail on missing or wrongly typed fields.

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.

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

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

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.

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

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

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

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.

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

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

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

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

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.

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

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

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

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

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

Use expect(page).toHaveScreenshot() to compare with stored baselines, with thresholds and masks for dynamic regions.

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

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

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

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.

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

List, dot, line, HTML, JSON and JUnit reporters, plus integrations such as Allure, configurable per environment.

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

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.

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

setInputFiles on the input for uploads; for downloads wait on page.waitForEvent('download') and save or inspect the 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.

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

Add retries with backoff for the API step, set a suitable timeout, and use mocks for non-critical dependencies.

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

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

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

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.

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

test.step groups actions into named steps in reports; annotations such as test.skip, test.fixme and test.slow communicate intent and adjust behaviour.

TypeScript + POM + custom fixtures, environment configs, API helpers for test data, tags like @smoke, sharding across CI machines, retries with traces, HTML/Allure reports, lint and review rules.

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

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

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

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

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.

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

const [download] = await Promise.all([ page.waitForEvent('download'), page.getByText('Export').click(), ]); await download.saveAs('reports/file.csv');

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

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

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

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.

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.

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

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

Use --debug or the Inspector, page.pause(), UI mode, the trace viewer and headed runs with slowMo.

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

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