Playwright Testing Interview Questions & Answers (2026)

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

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

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.

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.

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.

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

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.

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

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

await page.route('**/api/users', route => route.fulfill({ status: 200, json: [{ id: 1, name: 'Test' }] }) );

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

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

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.

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.

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

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.

Read the next page link or IDs from earlier responses, loop until done and assert counts and uniqueness; pass IDs between calls in the same test.

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

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.

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

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

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

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.

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.

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.

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

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

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

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.

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.

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

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

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

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

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

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

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

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

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.

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

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

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

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

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.

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

Tag tests (in the title or with { tag: '@smoke' }) and run: npx playwright test --grep @smoke (use --grep-invert to exclude).

Use the official Playwright image which contains browsers and dependencies, mount the project and run npx playwright test for consistent CI 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.

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.

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

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

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.

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

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.

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

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

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

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

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

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

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

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

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

Tag tests (in the title or with { tag: '@smoke' }) and run: npx playwright test --grep @smoke (use --grep-invert to exclude).

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

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

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.

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

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

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

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

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.

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.

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

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

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

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

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

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

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.

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

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

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.

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

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.

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.

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

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

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.

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

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

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

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

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

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

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

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

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

Read the next page link or IDs from earlier responses, loop until done and assert counts and uniqueness; pass IDs between calls in the same test.

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

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

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

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

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.

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

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.

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.

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

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

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

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

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

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

await page.route('**/api/users', route => route.fulfill({ status: 200, json: [{ id: 1, name: 'Test' }] }) );

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

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

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.

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

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

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

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.

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

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

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

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

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.

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

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

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.

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

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.

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.

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.

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.

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

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

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 page.frameLocator('#frame').getByRole(...) so actions work inside the iframe with auto-waiting.

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

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

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.

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

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

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

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

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.

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

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

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

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

await page.route('**/api/users', route => route.fulfill({ status: 200, json: [{ id: 1, name: 'Test' }] }) );

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

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

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

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.

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

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

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

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.

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

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

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

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.

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

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.

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

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

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

await page.route('**/api/users', route => route.fulfill({ status: 200, json: [{ id: 1, name: 'Test' }] }) );

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.

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.

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

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

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.

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.

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

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.

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

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

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

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.

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

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.

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

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

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

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

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

Read the next page link or IDs from earlier responses, loop until done and assert counts and uniqueness; pass IDs between calls in the same test.

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.

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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 retries with backoff for the API step, set a suitable timeout, and use mocks for non-critical dependencies.

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

await page.route('**/api/users', route => route.fulfill({ status: 200, json: [{ id: 1, name: '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.

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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 page.waitForResponse(res => res.url().includes('/api/orders') && res.ok()) together with the action that triggers it.

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.

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

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.

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.

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

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

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.

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

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

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

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

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.

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

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

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

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

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.

await page.route('**/api/users', route => route.fulfill({ status: 200, json: [{ id: 1, name: 'Test' }] }) );

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.

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.

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

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.

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

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

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

Tag tests (in the title or with { tag: '@smoke' }) and run: npx playwright test --grep @smoke (use --grep-invert to exclude).

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

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.

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

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.

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.

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

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

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

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 page.waitForResponse(res => res.url().includes('/api/orders') && res.ok()) together with the action that triggers it.

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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.

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

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.

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

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

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

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.

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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.

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

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

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

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.

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

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

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

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

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

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

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

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.

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.

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

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

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.

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

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

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

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

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 retries with backoff for the API step, set a suitable timeout, and use mocks for non-critical dependencies.

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.

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

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

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

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

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

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

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

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

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.

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

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

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