JP Morgan Chase Playwright Testing Interview Questions & Answers

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 retries in the config or CLI and failed tests re-run in a fresh context, with trace recorded on first retry to diagnose flakiness.

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

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.

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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.

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

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

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

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

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

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.

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

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.

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

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

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

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

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

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

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

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

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

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

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.

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.

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.

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

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');

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.

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

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

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

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

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.

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

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

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

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

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.

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.

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