Cisco Playwright Testing Interview Questions & Answers

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.

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.

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.

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

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.

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

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

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

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.

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

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

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

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

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

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

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.

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

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.

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

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.

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

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

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

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

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

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

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.

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.

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

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

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

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.

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).

TypeScript adds static types on top of JavaScript and compiles to it. Types catch errors early and give better autocomplete, which helps in larger test suites.

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

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

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

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 npx playwright test --shard=1/4 in each CI job and merge reports afterwards to reduce total run time.

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

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.

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.

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.

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

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

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

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

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

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

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

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

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.

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

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

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

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

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