Adobe Playwright Testing Interview Questions & Answers

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

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

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.

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

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

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

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

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

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

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 Locator is lazy, re-resolved on every action and auto-waits (recommended). An ElementHandle points to one DOM node and can go stale.

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

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

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.

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.

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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.

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

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

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

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.

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

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

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.

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.

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.

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

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.

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

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.

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

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