01
How do you validate JSON schema?
Show answer
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.
Lenskart Playwright Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Lenskart hiring for Playwright Testing roles
Lenskart is an Indian eyewear company that sells spectacles, sunglasses and contact lenses through its website, app and a large chain of retail stores. It combines online shopping with home eye tests, virtual try-on technology and in-house manufacturing. It hires software engineers, data analysts, product managers and retail and operations roles across its technology and business teams.
For Playwright Testing roles, this Lenskart practice set focuses most on Visual & Accessibility Testing (7), API Testing (6), Playwright Core (5), Component Testing (4). It has 5 easy, 29 medium, 6 hard questions, so you can start easy and work up to the harder ones.
- Company type
- E-commerce & consumer tech
- Headquarters
- Gurugram, India
- Main India offices
- Gurugram, Bengaluru
Lenskart Playwright Testing interview process
- Online coding or analytics assessment
- Technical round
- Case or managerial round
- HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for LenskartStart 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
The app polls a status endpoint every few seconds. How do you test the change from Pending to Done?
Show answer
Mock the endpoint with a counter: return Pending for the first two calls and Done after that. Then assert the UI shows Pending and later Done using web-first assertions with a suitable timeout. You can also use page.clock to speed up the polling interval instead of waiting real seconds. This makes a slow real-world process quick and deterministic.
03
How do you do visual regression testing?
Show answer
Use expect(page).toHaveScreenshot() to compare with stored baselines, with thresholds and masks for dynamic regions.
04
Write a component test for a Counter that increments on click.
Show answer
import { test, expect } from '@playwright/experimental-ct-react';
import { Counter } from './Counter';
test('increments on click', async ({ mount }) => {
const component = await mount(<Counter initial={2} />);
await component.getByRole('button', { name: 'Add' }).click();
await expect(component.getByTestId('count')).toHaveText('3');
});
05
How do you create test data through the API before a UI test?
Show answer
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.
06
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.
07
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.
08
An API test fails randomly because another test changes the same record. How do you fix it?
Show answer
Make each test own its data. Create the record inside the test or a fixture with a unique name, such as one using a timestamp or the worker index, and delete it in teardown. Avoid shared seed records for anything that gets modified. Shared read-only reference data is fine. This also lets tests run fully in parallel.
09
What can automated accessibility tools not catch?
Show answer
Scanners like axe find rule-based problems such as missing labels, bad contrast or invalid ARIA, which is roughly a third to a half of real issues. They cannot judge whether alt text is meaningful, whether focus order makes sense, whether error messages are understandable, or whether a screen reader user can actually finish the task. So automated scans are combined with keyboard tests and periodic manual checks with screen readers.
10
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.
11
How do you run the same visual tests at mobile, tablet and desktop sizes?
Show answer
Create one project per size in playwright.config, for example using devices['Pixel 7'], devices['iPad Mini'] and a desktop viewport, and point them at the same visual test files with testMatch or a tag. Because the project name is part of the baseline file name, each size keeps its own images automatically. This keeps the test code identical while covering responsive layouts.
12
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
13
A beforeAll creates one user and tests in the same file fail randomly in parallel mode. Why?
Show answer
With fullyParallel, the file's tests run in different workers, so each worker creates its own user, or tests in one worker share one user and change its state. Shared mutable data causes random failures. Give each test its own data through a test-scoped fixture, or create a unique user per worker with workerInfo.workerIndex in the name.
14
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.
15
How do you test that a modal dialog traps focus and returns it when closed?
Show answer
Open the dialog with a button and assert the dialog role is visible and focus moved inside it. Press Tab more times than there are controls and check with toBeFocused that focus never leaves the dialog. Press Escape, assert the dialog is hidden, and check that the opening button is focused again. Running the same test with Shift+Tab covers backward navigation as well.
16
A locator matches three Delete buttons and the test fails with a strict mode violation. How do you fix it?
Show answer
First scope the locator to the item you mean, for example the row that contains the user's name: page.getByRole('row', { name: 'Ravi Kumar' }).getByRole('button', { name: 'Delete' }). Do not reach for first() or nth() as a quick fix, because the order can change and the test may delete the wrong record. Scoping by meaningful context is stable and readable.
17
How do you test file downloads and verify their content?
Show answer
Capture the download event, save it with download.saveAs, then read the file in Node and assert on name, size or content.
18
Write a test that logs in and checks the dashboard heading.
Show answer
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();
});
19
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([]);
});
20
Write a component test that checks an onSubmit callback receives the form data.
Show answer
test('submits the entered name', async ({ mount }) => {
const submitted: string[] = [];
const component = await mount(
<NameForm onSubmit={(name) => submitted.push(name)} />
);
await component.getByLabel('Name').fill('Asha');
await component.getByRole('button', { name: 'Submit' }).click();
await expect.poll(() => submitted).toEqual(['Asha']);
});
21
A screenshot test fails with only a few pixels different because of anti-aliasing. What do you do?
Show answer
Open the diff image in the HTML report to confirm it is just edge smoothing and not a real change. If baselines were made on a different machine, regenerate them in the CI image. If the noise is genuine and repeatable, allow a small maxDiffPixels for that assertion or project. Avoid large ratios, because they also let real layout shifts through.
22
How do you measure API response time?
Show answer
Record timestamps around the request or use response timing, then assert the duration is under an agreed threshold.
23
Describe a time you convinced developers to add accessible labels or test ids.
Show answer
Situation: many inputs had no labels, so our tests relied on long CSS selectors that broke often. Task: get stable hooks without slowing developers. Action: I listed the worst screens, showed how getByLabel tests read and how the same labels help screen reader users, and offered to raise small pull requests myself. Result: the team added labels to new work as a rule and locator breakages dropped sharply.
24
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.
25
A test fails only in WebKit. How do you investigate?
Show answer
Run it alone with --project=webkit --headed and record a trace. Compare it with the Chromium trace to see where behaviour differs, such as date input format, scrolling, font rendering or a missing browser API. Check the app's support matrix. If it is a real product bug, raise it, and skip the test for WebKit with a linked ticket until it is fixed.
26
How do you wrap a component in a theme or router provider using hooksConfig?
Show answer
// playwright/index.tsx
import { beforeMount } from '@playwright/experimental-ct-react/hooks';
import { ThemeProvider } from '../src/theme';
export type HooksConfig = { theme?: 'light' | 'dark' };
beforeMount<HooksConfig>(async ({ App, hooksConfig }) => {
return <ThemeProvider mode={hooksConfig?.theme ?? 'light'}><App /></ThemeProvider>;
});
// in a test
await mount(<Header />, { hooksConfig: { theme: 'dark' } });
27
What are the built-in fixtures page, context, browser and request?
Show answer
page is a fresh tab for each test. context is the isolated browser context that owns the page, with its own cookies and storage. browser is the shared browser instance for the worker. request is an APIRequestContext for HTTP calls. You ask for them by name in the test function, and Playwright creates and cleans them up automatically.
28
How do project dependencies differ from globalSetup?
Show answer
A setup project is a normal test file that other projects list in dependencies. It shows in the HTML report, can use fixtures, and records traces, so failures are easy to debug. globalSetup is a plain function that runs before everything without fixtures or traces. The docs now recommend project dependencies for login and data seeding.
29
Visual tests pass on developers' laptops but fail in CI with tiny font differences. Why, and how do you fix it?
Show answer
Font rendering, anti-aliasing and installed fonts differ between Windows, macOS and Linux, so the same page produces slightly different pixels. The fix is to generate and compare baselines in one fixed environment, usually the official Playwright Docker image used in CI. Developers update baselines by running that container locally or through a CI job, not from their own machines. Loosening thresholds should be the last resort.
30
How do you test offline behaviour?
Show answer
Call context.setOffline(true) to cut all network access for the context, then check that the app shows an offline banner or queues actions. Switch back with setOffline(false) and verify it syncs. You can also set offline: true in the context options. For a single failing endpoint, use route.abort instead of going fully offline.
31
How do you exclude a third-party widget or switch off one rule in an axe scan?
Show answer
// scan the page but skip the chat widget you do not own
const results = await new AxeBuilder({ page })
.include('main')
.exclude('#third-party-chat')
.disableRules(['duplicate-id'])
.analyze();
expect(results.violations).toEqual([]);
// log a ticket for anything you exclude
32
How do you reuse login state across tests?
Show answer
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.
33
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.
34
How do you keep API tests independent of environment data?
Show answer
Do not depend on records that happen to exist in a shared environment. Each test or fixture creates what it needs through the API and cleans up after. Read environment-specific values such as base URL and credentials from config. For reference data that must exist, seed it in a setup project and verify it before tests run.
35
Does headless mode behave differently from headed mode?
Show answer
Modern Chromium headless uses the same browser code as headed, so behaviour is very close. Differences still appear in viewport size, GPU rendering, fonts and some OS dialogs. Tests should set an explicit viewport and not depend on window focus. If something passes headed but fails headless, record a trace and compare screenshots.
36
How do you open an HTML report downloaded from a CI artifact?
Show answer
Unzip the artifact and run npx playwright show-report followed by the folder path, for example npx playwright show-report ./playwright-report. This starts a small local server, which is needed because traces load through it. Opening index.html directly from disk often fails to show traces. You can also upload a single trace zip to the online trace viewer.
37
Write a visual assertion that masks a live clock and an ad banner.
Show answer
// masked areas are painted with a solid box
await expect(page).toHaveScreenshot('home.png', {
mask: [
page.getByTestId('live-clock'),
page.locator('.ad-banner'),
],
maskColor: '#FF00FF',
animations: 'disabled',
fullPage: true,
});
38
Write a component test that checks a required field shows an error on blur.
Show answer
test('shows error when email is left empty', async ({ mount }) => {
const component = await mount(<EmailField required />);
const input = component.getByLabel('Email');
await input.focus();
await input.blur();
await expect(component.getByText('Email is required')).toBeVisible();
await expect(input).toHaveAttribute('aria-invalid', 'true');
});
39
A test must confirm that an error banner does not appear, but it always waits the full timeout. How do you fix it?
Show answer
Use a web-first negative assertion such as await expect(banner).toBeHidden() or not.toBeVisible(); they pass as soon as the element is absent, so they do not wait the full timeout. The real problem is timing: assert after a positive signal, such as the success message appearing, otherwise the banner may simply not have rendered yet and the check passes too early.
40
Write a custom fixture that gives a logged-in page.
Show answer
import { test as base } from '@playwright/test';
export const test = base.extend({
loggedInPage: async ({ page }, use) => {
await page.goto('/login');
await page.getByLabel('Email').fill('qa@test.in');
await page.getByLabel('Password').fill('Pass@123');
await page.getByRole('button', { name: 'Sign in' }).click();
await use(page);
},
});
Tips to crack the Lenskart Playwright Testing interview
- For tech roles, practise DSA and backend basics, and be ready to discuss APIs, databases and scaling e-commerce systems.
- For analyst roles, revise SQL, Excel and metrics like conversion rate, average order value and store performance.
- Understand Lenskart's omnichannel model of online plus offline stores to answer business and product questions with context.
- 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; Lenskart interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Lenskart Playwright Testing interview?
Candidates usually go through 4 stages: Online coding or analytics assessment; Technical round; Case or managerial round; 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 Lenskart Playwright Testing interview?
This practice set leans on Visual & Accessibility Testing (7), API Testing (6), Playwright Core (5), Component Testing (4). Revise those first, then practise explaining one or two of your own projects end to end, because most Lenskart interviewers ask you to walk through real work.
Are these the exact questions asked at Lenskart?
No. These are curated practice questions that match the skills and difficulty usually tested in e-commerce & consumer tech interviews like Lenskart's. They are not a leaked or verified list of past questions.
Where does Lenskart hire Playwright Testing professionals in India?
Lenskart has large teams in Gurugram, Bengaluru. Openings and locations change often, so check the Lenskart careers page and filter by city and experience.
Playwright Testing questions for similar companies
E-commerce & consumer tech
BigBasket
Playwright Testing interview questions
Bengaluru
View questionsE-commerce & consumer tech
Delhivery
Playwright Testing interview questions
Gurugram, Bengaluru
View questionsE-commerce & consumer tech
Myntra
Playwright Testing interview questions
Bengaluru
View questionsE-commerce & consumer tech
MakeMyTrip
Playwright Testing interview questions
Gurugram, Bengaluru
View questionsE-commerce & consumer tech
Meesho
Playwright Testing interview questions
Bengaluru
View questionsE-commerce & consumer tech
Target
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