01
How do you mock network requests?
Show answer
page.route('**/api/items', route => route.fulfill({ json: [...] })) intercepts and replies with test data; route.abort() simulates failures.
Pine Labs Playwright Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Pine Labs hiring for Playwright Testing roles
Pine Labs is an Indian merchant commerce and payments company known for card payment terminals at retail stores. It offers point-of-sale payments, EMI and buy-now-pay-later options at checkout, online payments and gift card solutions through Qwikcilver. It serves merchants in India and other Asian markets and hires software engineers, quality engineers, data analysts and product roles.
For Playwright Testing roles, this Pine Labs practice set focuses most on API Testing (7), Playwright Core (6), Fixtures and Hooks (5), JavaScript and TypeScript (4). It has 1 easy, 33 medium, 6 hard questions, so you can start easy and work up to the harder ones.
- Company type
- Fintech
- Headquarters
- Noida, India
- Main India offices
- Noida, Bengaluru
Pine Labs Playwright Testing interview process
- Online coding assessment
- Technical round 1 (DSA)
- Technical round 2 (design or domain)
- Hiring manager and HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for Pine LabsStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
3 questions free Unlock the rest in seconds
02
What are union types and type narrowing in TypeScript?
Show answer
A union type allows several types, such as string | number or 'admin' | 'user'. Before using type-specific methods, you narrow the type with checks like typeof, instanceof, in or comparing a literal field. TypeScript then knows the exact type inside that branch. In tests, unions model options like a role parameter that accepts only known values.
03
How do you handle GraphQL APIs in Playwright?
Show answer
POST the query and variables as JSON to the single endpoint and assert both data and errors fields in the response.
04
How do you install and start a Playwright project?
Show answer
Run npm init playwright@latest, which sets up config, example tests and browsers; execute with npx playwright test.
05
How do you run tests on mobile viewports?
Show answer
Use device descriptors such as devices['iPhone 13'] in a project config to emulate viewport, user agent and touch.
06
A setup fixture creates expensive test data and suite time has doubled. How do you redesign it?
Show answer
Measure first with the report timings. Then create data through the API instead of the UI, move read-only shared data into a worker-scoped fixture, and seed common reference data once in a setup project. Keep per-test data only for things a test changes. Cache login with storageState. This usually cuts setup time sharply without losing isolation.
07
How does sharding split tests when fullyParallel is on compared with off?
Show answer
With fullyParallel off, Playwright shards by test file, so one large file always lands on one shard and shards can be uneven. With fullyParallel on, it shards by individual test, giving much more even distribution. Either way the split is deterministic, so the same shard number always gets the same tests for a given set of files, which helps reproduce failures.
08
How do you attach a screenshot or log to the report from inside a test?
Show answer
test('report', async ({ page }, testInfo) => {
await page.goto('/reports');
await testInfo.attach('report page', {
body: await page.screenshot(),
contentType: 'image/png',
});
await testInfo.attach('meta', { body: 'build 42', contentType: 'text/plain' });
});
09
How do you handle authentication to avoid logging in every test?
Show answer
Log in once in a setup project, save storageState to a file and reuse it in other projects or tests.
10
How do you test that duplicate POST requests do not create duplicate orders?
Show answer
If the API supports an idempotency key header, send the same POST twice with the same key and assert one order exists and both responses return the same id. Send it with different keys and expect two orders. Also try concurrent requests with Promise.all to check race conditions. Without a key, document the risk to the team.
11
How do you read a Playwright timeout error message?
Show answer
The error names the action and locator, for example locator.click: Timeout 30000ms exceeded, followed by a call log. The call log lists each attempt, such as waiting for the element to be visible, enabled and stable, or another element intercepting pointer events. The last lines show what blocked the action. Read it before changing timeouts.
12
How do you handle rate limits or slow APIs in tests?
Show answer
Add retries with backoff for the API step, set a suitable timeout, and use mocks for non-critical dependencies.
13
How do you share one authenticated API context across all tests in a worker?
Show answer
Create a worker-scoped fixture that calls request.newContext with baseURL and an auth header, or logs in through the API and keeps the cookies. Pass it to use, and dispose it after use returns. Every test in that worker gets the same ready context, so login happens once per worker. Do not store per-test data on it, or tests start depending on each other.
14
How do access modifiers help in page object classes?
Show answer
private and protected hide internal locators and helper steps, so tests can only call meaningful public methods such as login or addToCart. This keeps tests readable and lets you change internals without breaking callers. readonly on the page field prevents it from being replaced. TypeScript enforces these at compile time only, not at runtime.
15
How do you test accessibility with Playwright?
Show answer
Integrate axe-core through @axe-core/playwright, run an analysis on the page and assert that there are no violations.
16
What are projects in playwright.config?
Show answer
Named configurations that run the same tests across different browsers, devices or environments.
17
What is the difference between null and undefined?
Show answer
undefined means a variable has not been assigned; null is an intentional empty value.
18
What are web-first assertions?
Show answer
Assertions like expect(locator).toBeVisible() that retry until they pass or time out, unlike one-off checks.
19
How do you assert that a request was sent with the correct payload?
Show answer
const reqPromise = page.waitForRequest(r =>
r.url().endsWith('/api/orders') && r.method() === 'POST'
);
await page.getByRole('button', { name: 'Place order' }).click();
const req = await reqPromise;
expect(req.postDataJSON()).toMatchObject({ qty: 2, sku: 'MOU-01' });
20
How does visual testing work in Playwright?
Show answer
await expect(page).toHaveScreenshot('home.png') compares against a baseline image; tune maxDiffPixels and mask dynamic areas like dates.
21
How do you integrate Playwright with Allure or other reports?
Show answer
Install the allure-playwright reporter, add it in the config reporters array and generate the report from the allure-results folder in CI.
22
How do you send authentication headers?
Show answer
Set extraHTTPHeaders in the config or pass headers per request, for example Authorization: Bearer token fetched in a setup step.
23
How do you debug a test in VS Code with the Playwright extension?
Show answer
Install the Playwright Test for VS Code extension. Open the Testing panel to see tests, then set a breakpoint in the test file and click Debug Test. Execution stops at the breakpoint with the browser open, so you can inspect variables. Turn on Show browser to watch runs, and use Pick locator or Record at cursor to add steps.
24
How do you organise tests with page object model in Playwright?
Show answer
Create a class that takes a page, defines locators as properties and exposes action methods; instantiate it in a fixture for clean tests.
25
Why should you dispose an APIRequestContext?
Show answer
A context created with request.newContext() holds cookies, connections and stored responses in memory. Calling await context.dispose() frees them, and any later call on it fails. Without disposing, long runs can leak memory. The built-in request fixture is disposed automatically, so this matters for contexts you create in fixtures or helpers.
26
How do you take visual snapshots of each component state in component tests?
Show answer
Mount the component once per state, for example default, disabled, loading and error, and call await expect(component).toHaveScreenshot() for each. Since only the component is on the page, images are small, stable and fast to review. Run them in the same Docker image as CI. This often replaces many full-page visual tests that break for unrelated reasons.
27
What is testInfo and what can you do with it?
Show answer
testInfo is passed as the second argument to tests and hooks. It gives the test title, project name, retry number, status and output path. You can attach files, add annotations, change the timeout with testInfo.setTimeout, or skip conditionally. For example, attach extra logs only when testInfo.status differs from testInfo.expectedStatus.
28
What is the Clock API in Playwright?
Show answer
page.clock lets tests control time. clock.install() fakes Date and timers, clock.setFixedTime() freezes the current date, and clock.fastForward() or runFor() moves time ahead. This is useful for session timeouts, countdowns, scheduled banners and date-based logic, without waiting real minutes. Install the clock before the page loads so the app uses fake time from the start.
29
How do you test a page in dark mode or with reduced motion?
Show answer
Set colorScheme: 'dark' or reducedMotion: 'reduce' in the context options or test.use. You can also switch during a test with page.emulateMedia({ colorScheme: 'dark' }). Then assert the right styles or take a screenshot comparison. Reduced motion also helps stability, because many apps skip animations when that preference is set.
30
How do you fail a test if the page logs any console error?
Show answer
test('no console errors', async ({ page }) => {
const errors: string[] = [];
page.on('console', m => { if (m.type() === 'error') errors.push(m.text()); });
page.on('pageerror', e => errors.push(e.message));
await page.goto('/dashboard');
expect(errors).toEqual([]);
});
31
How do you read environment variables safely in a TypeScript test project?
Show answer
Load a .env file with a package like dotenv in playwright.config, then read process.env.BASE_URL. Values are string | undefined, so validate them early and throw a clear error if a required one is missing. Keep .env out of git and commit an .env.example instead. In CI, set the same names as secret variables.
32
How do you locate elements inside a specific row or card?
Show answer
Chain locators: find the container first, then search inside it. Example: page.getByRole('row', { name: 'INV-104' }).getByRole('button', { name: 'Download' }). Each step narrows the search area, so short names like Edit or Download stay unique. Chaining also documents intent clearly and avoids long CSS paths that break when markup changes.
33
How would you design API test coverage for a new endpoint?
Show answer
Cover happy path, validation errors, auth and permissions, boundary values, idempotency, schema, performance and data cleanup.
34
How do you return a fake JSON response that depends on the request body?
Show answer
await page.route('**/api/quote', async (route) => {
const body = route.request().postDataJSON();
const price = body.plan === 'pro' ? 999 : 299;
await route.fulfill({
status: 200,
json: { plan: body.plan, price },
});
});
35
Design a Playwright framework for a 500-test suite.
Show answer
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.
36
Write a GitHub Actions job that runs the suite in four shards.
Show answer
jobs:
e2e:
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:
shard: [1, 2, 3, 4]
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
- run: npm ci && npx playwright install --with-deps
- run: npx playwright test --shard=${{ matrix.shard }}/4 --reporter=blob
- uses: actions/upload-artifact@v4
with:
name: blob-${{ matrix.shard }}
path: blob-report
37
How do you balance pressure to automate quickly against writing stable tests?
Show answer
Situation: a manager wanted 50 tests for a release in one week. Task: deliver without creating a flaky suite. Action: I agreed on the 20 highest-risk flows first, used stable locators and shared fixtures, and listed the rest as follow-ups. Result: the 20 tests ran green in CI from day one and the rest were added next sprint.
38
How do you record a trace manually with the tracing API?
Show answer
Call await context.tracing.start({ screenshots: true, snapshots: true }) before the steps, and await context.tracing.stop({ path: 'trace.zip' }) after them. This is useful in scripts that use the library without the test runner, or when you want a trace of only part of a flow. tracing.group can label sections of steps.
39
How do you test a component that reads from a global state store?
Show answer
Wrap the mounted component in the store provider inside beforeMount, and use hooksConfig to choose the initial state for each test, such as a logged-in user or an empty cart. Build the store in the browser side of index.tsx, not in the test file. Then interact with the component and assert on the rendered output rather than reading store internals.
40
How do you set baseURL and common headers for API tests?
Show answer
Put them in the use block of playwright.config: use: { baseURL: process.env.API_URL, extraHTTPHeaders: { Accept: 'application/json', Authorization: `Bearer ${process.env.TOKEN}` } }. The request fixture then sends them on every call, and tests use short paths like /api/users. Keep tokens in environment variables, never in the repository.
Tips to crack the Pine Labs Playwright Testing interview
- Learn how card payments work at a store terminal, including authorisation, settlement and EMI conversion at checkout.
- Practise DSA and backend design, focusing on reliability and security for systems handling financial transactions.
- Read about Pine Labs products like EMI offers and gift cards to show interest in merchant commerce.
- Keep a one-minute story ready for every project on your CV: problem, your part, tools, result.
- Practise the hard questions on this page aloud; Pine Labs interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Pine Labs Playwright Testing interview?
Candidates usually go through 4 stages: Online coding assessment; Technical round 1 (DSA); Technical round 2 (design or domain); Hiring manager and HR round. The exact rounds change with the role, team, location and your experience, so confirm the process with the recruiter.
Which topics should I prepare for the Pine Labs Playwright Testing interview?
This practice set leans on API Testing (7), Playwright Core (6), Fixtures and Hooks (5), JavaScript and TypeScript (4). Revise those first, then practise explaining one or two of your own projects end to end, because most Pine Labs interviewers ask you to walk through real work.
Are these the exact questions asked at Pine Labs?
No. These are curated practice questions that match the skills and difficulty usually tested in fintech interviews like Pine Labs's. They are not a leaked or verified list of past questions.
Where does Pine Labs hire Playwright Testing professionals in India?
Pine Labs has large teams in Noida, Bengaluru. Openings and locations change often, so check the Pine Labs careers page and filter by city and experience.
Playwright Testing questions for similar companies
Fintech
Paytm
Playwright Testing interview questions
Noida, Bengaluru, Mumbai
View questionsFintech
Visa
Playwright Testing interview questions
Bengaluru, Mumbai
View questionsFintech
CRED
Playwright Testing interview questions
Bengaluru
View questionsFintech
Juspay
Playwright Testing interview questions
Bengaluru
View questionsFintech
Groww
Playwright Testing interview questions
Bengaluru
View questionsFintech
Stripe
Playwright Testing interview questions
Bengaluru
View questionsMore ways to practise
Company-wise Playwright Testing questionsPackage-wise Playwright Testing questionsExperience-wise Playwright Testing questionsRole-wise Playwright Testing questionsCity-wise Playwright Testing questionsMost asked Playwright Testing questionsScenario-based questionsPractical / hands-on questionsHR & behavioural questionsPlaywright Testing mock interviewOnline assessment questionsTechnical round questionsManagerial round questionsPlaywright Testing topic sheets