Infosys Playwright Testing Interview Questions & Answers

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

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.

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

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.

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

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

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.

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

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

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

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

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

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

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

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.

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.

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

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

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

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

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

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 device descriptors such as devices['iPhone 13'] in a project config to emulate viewport, user agent and touch.

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

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.

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.

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

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

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.

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

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

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

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

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

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

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.

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

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.

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

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

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.

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

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.

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

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.

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.

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

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

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.

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

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

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

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

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.