PhonePe Playwright Testing Interview Questions & Answers

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.

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.

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.

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

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

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 to open the control, then use getByRole('option') or a text locator for the target item, instead of relying on fragile index-based selectors.

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

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

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

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

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

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

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.

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

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 timeout and expect.timeout in config, test.setTimeout() for one test and test.slow() for known slower tests.

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 the request fixture: const res = await request.get('/api/users'); expect(res.ok()).toBeTruthy(); const body = await res.json();

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

test('login', async ({ page }) => { await page.goto('/login'); await page.getByLabel('Email').fill('a@b.com'); await page.getByLabel('Password').fill('secret'); await page.getByRole('button', { name: 'Login' }).click(); await expect(page.getByRole('heading', { name: 'Dashboard' })).toBeVisible(); });

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.

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

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

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.

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.

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

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

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

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

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

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.

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

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.

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.

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.

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

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

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

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

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

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

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

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.

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.

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

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

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.

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

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

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

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

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

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

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

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

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

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.

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