Visa Playwright Testing Interview Questions & Answers

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

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

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

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

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.

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

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.

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

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.

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

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

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.

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

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

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.

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.

Syntax over Promises: an async function returns a Promise and await pauses until it resolves. Every Playwright action returns a Promise, so you await each step.

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

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

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

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

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

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

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

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

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

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

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 codegen records user actions and generates test code with suggested locators, handy for starting tests.

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.

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

Send invalid payloads or missing auth and assert 400, 401 or 404 codes and the error message bodies.

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

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

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

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.

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.

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

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

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

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

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

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

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

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

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

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.

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

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

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.

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

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

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.

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

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

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

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