Capgemini Playwright Testing Interview Questions & Answers

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

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

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.

Assert the status with expect(res.status()).toBe(200), parse res.json() and check fields, using schema validation for the structure.

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

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

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.

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.

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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.

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

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

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.

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

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

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

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

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

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

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.

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.

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.

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

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

Scripts that run once before or after the whole run, for seeding data, starting services or creating authentication state.

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

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

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.

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 browser is the engine instance; a context is an isolated session (cookies, storage); a page is a tab inside a context.

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

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.

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

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

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

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.

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

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

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

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 --debug or the Inspector, page.pause(), UI mode, the trace viewer and headed runs with slowMo.

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.

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 a class that takes a page, defines locators as properties and exposes action methods; instantiate it in a fixture for clean tests.

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

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

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.

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

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

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.

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

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

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