Deloitte Playwright Testing Interview Questions & Answers

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

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

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.

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

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.

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

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

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.

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

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

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

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.

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

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

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

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.

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

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

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

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

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

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.

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

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.

User-facing ones: getByRole, getByText, getByLabel, getByPlaceholder and getByTestId, which are more resilient than CSS or XPath.

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

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

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

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.

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

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

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

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

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

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

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

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

var is function-scoped and hoisted. let and const are block-scoped; const can't be reassigned (though an object it points to can change). Prefer const, then let.

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

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

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

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

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

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

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.

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

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.

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

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

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

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

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.

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

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

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

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

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

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

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 expect.soft(locator).toHaveText('...') records the failure but lets the test continue, so you see every mismatch in one run.

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

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.