Paytm Playwright Testing Interview Questions & Answers

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

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.

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

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

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.

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

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.

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.

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

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

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

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

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

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.

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

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

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.

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

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

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

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

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

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

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.

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

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.

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.

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

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 type alias describes a shape or union of values; an enum creates a named set of constants that exists at runtime.

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.

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

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

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

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

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

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

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

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

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

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

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

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.

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

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.

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.

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

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.

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