Razorpay Playwright Testing Interview Questions & Answers

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.

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

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

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

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

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.

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

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

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

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.

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

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

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.

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.

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.

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.

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

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.

Workflow: checkout → setup-node → npm ci → npx playwright install --with-deps → npx playwright test → upload playwright-report as an artifact.

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

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

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.

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.

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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.

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

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.

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.

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

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.

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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.

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

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

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

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.

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.