Zomato Playwright Testing Interview Questions & Answers

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

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

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

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

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

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

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

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.

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.

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

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

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

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

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

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.

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.

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.

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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.

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

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

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.

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.

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.

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

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

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

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

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

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

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.

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

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.

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

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

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 browser is the engine instance; a context is an isolated session (cookies, storage); a page is a tab inside a context.

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.

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

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

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.

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

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

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

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

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.

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(); });

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

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

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

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

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

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

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

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 a class that takes a page, defines locators as properties and exposes action methods; instantiate it in a fixture for clean tests.