Tech Mahindra Playwright Testing Interview Questions & Answers

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

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.

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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.

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

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.

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

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

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

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

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.

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 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 page.frameLocator('#frame').getByRole(...) so actions work inside the iframe with auto-waiting.

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

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

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

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

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.

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

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

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

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.

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

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

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

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

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

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

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.

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

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

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

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.

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

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

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

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.

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