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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

await request.post('/api/users', { data: { name: 'Asha' } }) automatically sets JSON headers and serialises the payload.

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

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.

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

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

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

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

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.

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

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

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.

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

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

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

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.

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

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

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

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

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

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.

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

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

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

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

npx playwright codegen records user actions and generates test code with suggested locators, handy for starting tests.

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

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

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

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

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

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

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

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