Accenture Playwright Testing Interview Questions & Answers

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 request.post('/api/users', { data: { name: 'Asha' } }) automatically sets JSON headers and serialises the payload.

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

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

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.

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

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

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.

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

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

undefined means a variable has not been assigned; null is an intentional empty value.

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

API testing checks services directly and is fast and stable; UI testing checks the full user experience in the browser and is slower.

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.

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

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.

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

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

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.

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

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

locator.hover() and locator.dragTo(target) perform these actions, with auto-waiting for actionability.

A browser is the engine instance; a context is an isolated session (cookies, storage); a page is a tab inside a context.

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' }] }) );

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

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

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.

Install the allure-playwright reporter, add it in the config reporters array and generate the report from the allure-results folder in CI.

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

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

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

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

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

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.

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.

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

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

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

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

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.