Intuit Playwright Testing Interview Questions & Answers

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

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

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

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

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

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

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.

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

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

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

Assertions like expect(locator).toBeVisible() that retry until they pass or time out, unlike one-off checks.

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.

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

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.

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.

Log in with request.post, call request.storageState(), and create a browser context using that state.

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

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

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

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

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

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

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

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.

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

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

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.

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

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

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

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.

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

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

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

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

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

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.

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.

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.

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

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

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

Use expect(page).toHaveScreenshot() to compare with stored baselines, with thresholds and masks for dynamic regions.

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.

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

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

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

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

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.