01
What are closures?
Show answer
A function that remembers variables from its outer scope even after that scope has finished. They are used for private state and factory helpers.
Zensar Technologies Playwright Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Zensar Technologies hiring for Playwright Testing roles
Zensar Technologies is an Indian IT services company and part of the RPG Group. It provides digital experience, application engineering, testing, cloud and data services to clients in manufacturing, retail, financial services and hi-tech. In India it hires for software engineers, test engineers and data professionals.
For Playwright Testing roles, this Zensar Technologies practice set focuses most on Debugging and Trace Viewer (6), JavaScript and TypeScript (5), Network Mocking (5), Parallel Runs, Sharding & Reporting (5). It has 17 easy, 23 medium questions, so you can start easy and work up to the harder ones.
- Company type
- IT services
- Headquarters
- Pune, India
- Main India offices
- Pune, Hyderabad, Bengaluru
Zensar Technologies Playwright Testing interview process
- Online assessment (aptitude + reasoning)
- Coding test
- Technical interview
- HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for Zensar TechnologiesStart 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
Why mock the network in UI tests at all?
Show answer
Mocking makes tests fast, stable and independent of backend data or third-party outages. It also lets you test states that are hard to create for real, such as empty lists, errors or huge responses. The trade-off is lower confidence that frontend and backend work together, so keep some unmocked end-to-end tests for critical journeys.
03
How can you view a trace file without a local Playwright install?
Show answer
Open trace.playwright.dev in a browser and drag the trace zip onto the page. It is a static web app that loads the trace locally in the browser, so the file is not uploaded to a server. This lets developers or managers look at a failed CI run quickly. For full features and offline use, npx playwright show-trace works too.
04
How do you open a trace file?
Show answer
Download trace.zip from the test results or CI artifact. Run npx playwright show-trace path/to/trace.zip to open it locally, or drag the file into trace.playwright.dev, which processes it in the browser without uploading it. In the HTML report, failed tests with a trace show a trace link you can click directly.
05
What do headed mode and slowMo do?
Show answer
--headed shows the browser window instead of running headless, so you can watch the test. slowMo, set in launchOptions, adds a delay in milliseconds before every action, which makes fast steps visible. Both help when you are writing or debugging a test. Do not leave slowMo on in CI, because it slows every action.
06
How many workers does Playwright use by default, and how do you change it?
Show answer
By default Playwright uses about half of the logical CPU cores on the machine. You can set workers in playwright.config as a number or a percentage string such as '50%', or override it on the command line with --workers=4. Many teams use process.env.CI ? 2 : undefined so CI runners with few cores are not overloaded while laptops use their full power.
07
What is Playwright component testing?
Show answer
Component testing mounts a single UI component, such as a React or Vue button or form, in a real browser page and tests it with the normal Playwright API. Playwright bundles the component with Vite, serves it on a small page and gives you a mount fixture. You get real browser rendering and events, which unit tests in jsdom cannot give, while staying much faster than full end-to-end flows. The feature is still marked experimental.
08
Tell me about a bug you found through API testing that UI tests missed.
Show answer
Situation: the UI hid a delete button for normal users, so UI tests passed. Task: check permissions properly. Action: I called the delete endpoint directly with a normal user's token and it returned 204. Result: the team fixed the server-side permission check, and I added role-based API tests for every admin endpoint.
09
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']);
});
10
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.
11
In what order do hooks and fixtures run?
Show answer
Worker fixtures and beforeAll run first for the worker. For each test, the test fixtures it needs are set up, then beforeEach hooks run, then the test body. Afterwards afterEach hooks run, then test fixtures are torn down in reverse order. afterAll and worker fixture teardown run when the worker finishes. Fixtures are lazy, so unused ones never run.
12
How do you handle dialogs such as alerts?
Show answer
Register page.on('dialog', d => d.accept()) before the action triggers the dialog.
13
How do you keep test code, page objects and utilities organised as a repository grows?
Show answer
Use a clear layout: tests grouped by feature, a pages folder for page objects, a fixtures folder that exposes them, and api and data folders for helpers and builders. Add path aliases in tsconfig, a lint config with the Playwright plugin, and a short contributing guide. Review new helpers in pull requests so duplicate utilities do not spread.
14
How do you run one group of tests serially while the rest of the suite runs in parallel?
Show answer
Put the group in its own project with fullyParallel: false and limit it to one worker, which recent versions allow with a workers setting on the project, or run it in a separate CI step with --project=serial --workers=1. Inside a file, test.describe.configure({ mode: 'serial' }) keeps order. Use project dependencies if the group must run after the parallel tests.
15
Which methods does the Playwright Reporter interface provide?
Show answer
The main ones are onBegin with the config and full suite, onTestBegin and onTestEnd for each test, onStepBegin and onStepEnd for steps, onStdOut and onStdErr for output, onError for errors outside tests and onEnd with the overall result. onEnd can be async, so you can send results to an API before the process exits. You register the reporter by path in the reporter config.
16
How do you check colour contrast in Playwright tests?
Show answer
Playwright has no built-in contrast assertion, so you run axe-core through @axe-core/playwright, whose color-contrast rule checks text against WCAG ratios such as 4.5 to 1 for normal text. Scan pages in each theme, for example after emulating dark mode with colorScheme. Axe may report some elements as needing review, for example text over images, and those need a manual look.
17
Write a fixture that gives each parallel worker its own test account.
Show answer
import { test as base } from '@playwright/test';
export const test = base.extend<{}, { account: { email: string; password: string } }>({
account: [async ({}, use, workerInfo) => {
const i = workerInfo.parallelIndex;
await use({
email: `qa.user${i}@example.test`,
password: process.env.QA_PASSWORD!,
});
}, { scope: 'worker' }],
});
18
How does expect.poll work and when would you use it?
Show answer
expect.poll calls a function again and again until the value it returns passes the matcher or the timeout runs out. It is useful for values that are not locators, such as an API status or a database count. Example: await expect.poll(async () => (await request.get('/api/job/7')).status()).toBe(200). You can tune the intervals and the timeout.
19
How do you inspect a specific network request in the trace viewer?
Show answer
Open the Network tab in the trace viewer, which lists every request in the test. Click one to see method, URL, status, request and response headers and bodies, and timing. Selecting an action filters the list to requests around that step. This shows whether a UI failure came from a failed API, a slow response or unexpected data.
20
How do you emulate a mobile device in Playwright?
Show answer
Import devices from @playwright/test and spread a profile into a project or test.use, for example use: { ...devices['Pixel 7'] }. This sets viewport, user agent, device scale factor, touch support and isMobile. It emulates the browser, not a real phone, so it is good for responsive layout tests but not a replacement for real-device testing.
21
What is the difference between page.route and context.route?
Show answer
page.route applies only to requests from that page. context.route applies to every page in the browser context, including pop-ups and new tabs opened later. Use context.route when a flow opens new windows, such as a payment pop-up, or when you set up mocks in a fixture before the page exists. Page routes take priority over context routes.
22
CI runners have 2 CPU cores and workers is set to 8. Tests start timing out randomly. Why?
Show answer
Eight browsers compete for two cores and limited memory, so pages render slowly, actions hit timeouts and the app under test may also be overloaded. More workers than cores rarely helps. Set workers to match the runner, such as 2, and scale out with shards on more machines instead. Watch CPU and memory metrics in CI to confirm.
23
How do you change the default assertion timeout?
Show answer
Web-first assertions wait 5 seconds by default. Change it globally in playwright.config with expect: { timeout: 10000 }, or for one assertion with await expect(locator).toBeVisible({ timeout: 15000 }). Raise it only for genuinely slow steps like report generation. Raising it everywhere hides performance problems and makes failing tests slower to report.
24
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.
25
What is UI mode and how is it different from --debug?
Show answer
UI mode, opened with npx playwright test --ui, is a dashboard to run, filter and watch tests, with a trace-like timeline for each one and a watch mode that reruns on file changes. --debug opens the Inspector to step through a single run live. Use UI mode for daily development and --debug for stepping through a specific action.
26
How do you override options like baseURL or viewport for one file?
Show answer
Call test.use at the top of the file or inside a describe block, for example test.use({ viewport: { width: 375, height: 812 }, locale: 'hi-IN' }). The options apply only to tests in that scope. Options you can set this way include baseURL, storageState, colorScheme and extraHTTPHeaders. Global defaults stay in the use block of playwright.config.
27
A third-party analytics script makes tests slow and flaky. What do you do?
Show answer
Block it in tests with context.route on its domain and route.abort, or fulfill it with an empty script. Analytics is not what you are testing, and blocking it removes delays and random network errors. If tracking events matter, write a few separate tests that capture the requests with waitForRequest and assert their parameters.
28
What is the difference between page.goto and page.waitForURL?
Show answer
page.goto starts a navigation to a URL and waits for the load state you choose. page.waitForURL does not navigate; it waits until the current page reaches a URL that matches a string, glob or regular expression, which is useful after a click that redirects, such as a login followed by a jump to the dashboard. Pair it with the click instead of adding fixed sleeps.
29
Your mocked route never fires. What do you check?
Show answer
Check that the route is registered before the request is sent, usually before goto. Compare the pattern with the real URL in the trace network tab, including query strings and host. Make sure a service worker is not handling the request, and set serviceWorkers: 'block' if it is. Also check that another handler is not matching first or the route was not removed.
30
How do you handle errors in async code?
Show answer
Use try-catch with await, or .catch() on promises, and make sure rejected promises are never left unhandled.
31
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.
32
How do you filter a list of locators by text or by a child element?
Show answer
// pick one product card from many
const card = page.getByRole('listitem')
.filter({ hasText: 'Wireless Mouse' })
.filter({ has: page.getByRole('button', { name: 'Add to cart' }) });
await card.getByRole('button', { name: 'Add to cart' }).click();
// hasNotText and hasNot exclude matches
33
What is the difference between toHaveScreenshot and toMatchSnapshot?
Show answer
toHaveScreenshot is for images of a page or locator. It waits for the page to become visually stable, retries the capture until two shots match, and supports options like mask and animations. toMatchSnapshot compares any value you pass in, such as a string, a buffer or text output, against a stored file, without waiting or retrying. Use toHaveScreenshot for UI and toMatchSnapshot for generated text or file content.
34
Write code to fill a login form using label-based locators.
Show answer
test('login form', async ({ page }) => {
await page.goto('/login');
await page.getByLabel('Email').fill('user@test.in');
await page.getByLabel('Password').fill('Pass@123');
await page.getByRole('button', { name: 'Sign in' }).click();
await expect(page).toHaveURL(/dashboard/);
});
35
How do you attach axe results to the Playwright HTML report?
Show answer
test('cart is accessible', async ({ page }, testInfo) => {
await page.goto('/cart');
const results = await new AxeBuilder({ page }).analyze();
await testInfo.attach('axe-results', {
body: JSON.stringify(results.violations, null, 2),
contentType: 'application/json',
});
expect(results.violations).toEqual([]);
});
36
How do you update screenshot baselines after an intended UI change?
Show answer
Run the tests with npx playwright test --update-snapshots, optionally filtered to the affected files or a tag. Playwright rewrites the baselines with the new images. Newer versions also accept modes such as --update-snapshots=changed or missing so only the needed files are touched. Always look at the diff in the pull request before merging, because blindly updating hides real regressions.
37
What is a Promise and what states can it have?
Show answer
A Promise represents a value that will be available later, such as an API response. It is pending at first, then either fulfilled with a value or rejected with an error, and it never changes after that. You consume it with await or then and catch. Almost every Playwright call returns a Promise, which is why tests use await so much.
38
What is the playwright/index.tsx file used for?
Show answer
It is the entry file bundled into the component test page, so it runs in the browser before every mount. You import global CSS, fonts and theme files there, and register beforeMount and afterMount hooks to wrap components in providers such as a router, theme or state store. Keeping this setup in one place means individual tests can mount components without repeating boilerplate.
39
A trace shows the click landed on an overlay instead of the button. How do you fix it?
Show answer
The call log will say another element intercepts pointer events. Find what the overlay is, such as a loading mask, cookie banner or chat widget. Wait for it to disappear with expect(overlay).toBeHidden(), or close it in a fixture. Do not use force: true, because it hides a real issue: a user would also be blocked by that overlay.
40
What are template literals?
Show answer
Strings in backticks that allow embedded expressions like `Hello ${name}` and multi-line text, useful for building dynamic locators and URLs.
Tips to crack the Zensar Technologies Playwright Testing interview
- Practise aptitude and basic programming questions for the online test, along with simple SQL queries.
- Read about the RPG Group and Zensar's focus on digital experience and engineering services.
- Prepare to explain your projects clearly, including tools used and testing done, in a short structured answer.
- 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; Zensar Technologies interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Zensar Technologies Playwright Testing interview?
Candidates usually go through 4 stages: Online assessment (aptitude + reasoning); Coding test; Technical interview; 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 Zensar Technologies Playwright Testing interview?
This practice set leans on Debugging and Trace Viewer (6), JavaScript and TypeScript (5), Network Mocking (5), Parallel Runs, Sharding & Reporting (5). Revise those first, then practise explaining one or two of your own projects end to end, because most Zensar Technologies interviewers ask you to walk through real work.
Are these the exact questions asked at Zensar Technologies?
No. These are curated practice questions that match the skills and difficulty usually tested in it services interviews like Zensar Technologies's. They are not a leaked or verified list of past questions.
Where does Zensar Technologies hire Playwright Testing professionals in India?
Zensar Technologies has large teams in Pune, Hyderabad, Bengaluru. Openings and locations change often, so check the Zensar Technologies careers page and filter by city and experience.
Playwright Testing questions for similar companies
IT services
Mphasis
Playwright Testing interview questions
Bengaluru, Pune, Chennai
View questionsIT services
Nagarro
Playwright Testing interview questions
Gurugram, Jaipur
View questionsIT services
Coforge
Playwright Testing interview questions
Noida, Greater Noida, Bengaluru +2
View questionsIT services
Hexaware
Playwright Testing interview questions
Navi Mumbai, Chennai, Pune +2
View questionsIT services
Infosys
Playwright Testing interview questions
Bengaluru, Mysuru, Pune +2
View questionsIT services
TCS
Playwright Testing interview questions
Mumbai, Chennai, Pune +2
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