Swiggy Playwright Testing Interview Questions & Answers

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

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

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

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

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.

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

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

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.

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

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.

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

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

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

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

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.

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.

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

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

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

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

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

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

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

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.

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

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

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

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

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.

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.

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

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

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

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

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

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

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

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

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.

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

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

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.

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

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

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

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.

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 the official Playwright image which contains browsers and dependencies, mount the project and run npx playwright test for consistent CI environments.

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.

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.

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 dotenv files per environment, read them in playwright.config and set baseURL and credentials from variables, selecting with an ENV flag.

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

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.

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

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

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

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.

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

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

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

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

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

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

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

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

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.

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

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

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

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

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.

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

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