01
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.
Chargebee Playwright Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Chargebee hiring for Playwright Testing roles
Chargebee is a subscription billing and revenue management software company founded in Chennai. Its platform helps SaaS and subscription businesses manage recurring billing, invoicing, payments, revenue recognition and retention. It has major engineering and operations teams in India and hires software engineers, quality engineers, product managers, solutions consultants and customer support roles.
For Playwright Testing roles, this Chargebee practice set focuses most on Playwright Core (7), Locators and Assertions (5), Network Mocking (5), API Testing (5). It has 2 easy, 29 medium, 9 hard questions, so you can start easy and work up to the harder ones.
- Company type
- Product
- Headquarters
- San Francisco, USA
- Main India offices
- Chennai, Bengaluru
Chargebee Playwright Testing interview process
- Online coding assessment
- Technical round 1 (DSA)
- Technical round 2 (design or practical coding)
- Hiring manager and culture round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for ChargebeeStart 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 is hoisting?
Show answer
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.
03
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');
});
04
A toast message disappears after two seconds and the assertion on it is flaky. How do you test it reliably?
Show answer
Assert immediately after the action that triggers it, using a web-first assertion like toBeVisible and toHaveText, which start checking at once. Do not add sleeps before the check. If the toast is still missed, control time with page.clock so it does not auto-hide, or verify the result through the data it confirms, such as the saved record.
05
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 },
});
});
06
A product list uses infinite scroll. How do you test that more items load?
Show answer
Count the items, then scroll the last item into view with lastItem.scrollIntoViewIfNeeded() or page.mouse.wheel. Assert with expect(items).toHaveCount greater than before, for example using expect.poll on items.count(). Repeat until an end-of-list message appears. Also check no duplicates appear and that a loading indicator shows while fetching.
07
How do you test file upload via API?
Show answer
Use request.post with multipart: { file: { name, mimeType, buffer } } and assert the response and stored file details.
08
How do you simulate a slow API to test a loading spinner?
Show answer
await page.route('**/api/report', async route => {
await new Promise(r => setTimeout(r, 3000));
await route.continue();
});
await page.getByRole('button', { name: 'Generate' }).click();
await expect(page.getByRole('progressbar')).toBeVisible();
await expect(page.getByRole('progressbar')).toBeHidden();
09
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.
10
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.
11
How do you combine API and UI tests?
Show answer
Create test data through API calls, verify it in the UI and clean up via API, which makes UI tests faster and more reliable.
12
A component under test needs a complex class instance as a prop and the test fails to serialise it. What do you do?
Show answer
Create a small test story component in a separate file that builds the class instance inside the browser and renders the real component with it. The test then mounts the story with simple props, such as an id or a scenario name. This keeps the data creation on the browser side of the boundary and also documents test scenarios as reusable stories.
13
A test uses forEach with an async callback and the checks inside never seem to run. Why?
Show answer
forEach does not wait for async callbacks, so it starts each callback and returns at once. The test may finish before the assertions run, or their errors are lost. Use for...of with await to run steps in order, or Promise.all with map when the steps can safely run in parallel. A lint rule can flag this pattern.
14
How do you capture browser console messages and page errors?
Show answer
Listen with page.on('console', msg => ...) for console.log, warnings and errors, and page.on('pageerror', err => ...) for uncaught exceptions. Collect them in an array and attach them to the report on failure. Traces also show console output. Uncaught page errors often explain why a button did nothing or a page stayed blank.
15
How do you run tests against a preview deployment created for each pull request?
Show answer
Make baseURL come from an environment variable, such as process.env.BASE_URL, with a default for local runs. In the pipeline, wait for the preview deployment to be ready, read its URL from the deployment step and pass it to the test job. Add a quick health check request first, so a failed deployment is reported clearly instead of as hundreds of test failures.
16
How do you reproduce a flaky test locally?
Show answer
Run it many times in isolation: npx playwright test cart.spec.ts -g 'apply coupon' --repeat-each=30 --workers=4 --trace=on. Repeating it with several workers creates the timing pressure CI has. Add --retries=0 so failures are not hidden. Once it fails, open the trace for that run and compare it with a passing run.
17
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.
18
What is the difference between getByText and getByLabel?
Show answer
getByText matches visible text anywhere on the page, so it suits paragraphs, links and messages. getByLabel finds a form control through its associated label element, aria-label or aria-labelledby, so it is the right choice for inputs such as Email or Password. Using getByLabel for inputs also checks that labels are wired correctly, which getByText cannot do.
19
How do you mock a paginated endpoint that returns different data per page?
Show answer
await page.route('**/api/products?*', route => {
const url = new URL(route.request().url());
const p = Number(url.searchParams.get('page') ?? 1);
const items = Array.from({ length: 10 }, (_, i) => ({ id: (p - 1) * 10 + i }));
return route.fulfill({ json: { items, hasNext: p < 3 } });
});
20
How can you apply extra CSS only while a screenshot is taken?
Show answer
Pass the stylePath option to toHaveScreenshot or set it in the expect.toHaveScreenshot section of the config. The stylesheet is injected just for the capture, so you can hide scrollbars, freeze a carousel, or set visibility hidden on dynamic widgets without changing the app. It is cleaner than adding test-only classes and also works when a mask box would cover too much of the layout.
21
A feature is controlled by a flag served from a config API. How do you test both states?
Show answer
Mock the config endpoint in a fixture option so each test chooses the flag value, for example featureFlags: { newCheckout: true }. Run the flow with the flag on and off and assert the different UI. Mocking avoids changing shared environment settings that would affect other testers. Also keep one test against the real config to catch wiring mistakes.
22
How can you run only the tests affected by a code change?
Show answer
Use npx playwright test --only-changed=origin/main. It looks at files changed against that git reference and runs the test files that changed or that import changed files. It suits fast pull request feedback in a large suite. It cannot see backend or config changes that tests do not import, so still run the full suite before release.
23
How do you handle dialogs such as alerts?
Show answer
Register page.on('dialog', d => d.accept()) before the action triggers the dialog.
24
Describe a time a test passed but the feature was actually broken.
Show answer
Situation: a checkout test passed, but users saw a blank order summary. Task: find why. Action: I found the test only asserted that the summary container was visible, not its contents. I added assertions on item names, totals and the order id. Result: the test caught the regression, and I reviewed other tests for similar weak assertions.
25
Why are screenshot baselines specific to browser and operating system?
Show answer
Each browser engine lays out and paints text, shadows and form controls slightly differently, and each operating system has its own fonts and smoothing. A Chromium image on Linux will rarely match WebKit on macOS pixel for pixel. That is why Playwright includes project and platform in the file name and why teams fix one rendering environment for baselines.
26
What does the reportSlowTests option do?
Show answer
reportSlowTests makes Playwright list test files that took longer than a threshold at the end of the run. You set max, the number of files to show, and threshold in milliseconds, for example { max: 5, threshold: 60000 }. It is a cheap way to find files worth splitting, because one slow file can hold up a worker or a whole shard.
27
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.
28
How do you use keyboard shortcuts in Playwright?
Show answer
Use locator.press('Enter') for a key on a focused element, or page.keyboard.press('Control+A') for page-level shortcuts. Modifiers combine with a plus sign, and ControlOrMeta picks Ctrl on Windows and Linux and Cmd on macOS. keyboard.down and keyboard.up hold keys. Use pressSequentially only when the app needs real keystrokes, such as autocomplete.
29
What do locator.and() and locator.or() do?
Show answer
and() returns a locator that matches elements satisfying both locators, for example a button that also has a certain title. or() matches either locator, which helps when the UI may show one of two states, such as a New email button or a security dialog. With or(), wrap the assertion carefully, because if both appear the strict check fails.
30
What are the risks of relying on an experimental testing feature in a large codebase?
Show answer
APIs may change between minor versions, so upgrades can break many tests at once, and documentation or community examples are thinner. To reduce risk, pin versions, wrap mount setup in shared helpers, keep stories simple and read release notes before upgrading. Also keep the end-to-end suite healthy so you are not dependent on one tool for all UI confidence.
31
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.
32
How do you handle multiple tabs or pop-ups?
Show answer
Wait for the popup event with const [popup] = await Promise.all([page.waitForEvent('popup'), page.click('a')]), then interact with popup.
33
How do you check that a product list on the page is sorted by price?
Show answer
const texts = await page.getByTestId('price').allTextContents();
const prices = texts.map(t => Number(t.replace(/[^0-9.]/g, '')));
const sorted = [...prices].sort((a, b) => a - b);
expect(prices).toEqual(sorted);
// wait for the list first with toHaveCount
34
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.
35
How do you test API error scenarios?
Show answer
Send invalid payloads or missing auth and assert 400, 401 or 404 codes and the error message bodies.
36
How do you perform drag and drop and hover?
Show answer
locator.hover() and locator.dragTo(target) perform these actions, with auto-waiting for actionability.
37
How do you manage flaky tests without hiding real failures?
Show answer
Use retries in CI so one-off failures do not block merges, but treat any test marked flaky in the report as a defect. Track flaky tests on a dashboard, quarantine repeat offenders with a tag and an owner, and set a deadline to fix or delete them. Never retry without investigating, or real intermittent bugs will be missed.
38
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.
39
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.
40
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.
Tips to crack the Chargebee Playwright Testing interview
- Practise DSA problems and object-oriented design, and be ready to write clean, readable code with proper edge case handling.
- Learn basic subscription business concepts like recurring billing, proration, invoices and churn to show interest in the product domain.
- Prepare examples of ownership and learning from mistakes, since product companies like Chargebee value strong culture fit.
- 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; Chargebee interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Chargebee Playwright Testing interview?
Candidates usually go through 4 stages: Online coding assessment; Technical round 1 (DSA); Technical round 2 (design or practical coding); Hiring manager and culture 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 Chargebee Playwright Testing interview?
This practice set leans on Playwright Core (7), Locators and Assertions (5), Network Mocking (5), API Testing (5). Revise those first, then practise explaining one or two of your own projects end to end, because most Chargebee interviewers ask you to walk through real work.
Are these the exact questions asked at Chargebee?
No. These are curated practice questions that match the skills and difficulty usually tested in product interviews like Chargebee's. They are not a leaked or verified list of past questions.
Where does Chargebee hire Playwright Testing professionals in India?
Chargebee has large teams in Chennai, Bengaluru. Openings and locations change often, so check the Chargebee careers page and filter by city and experience.
Playwright Testing questions for similar companies
Product
Playwright Testing interview questions
Bengaluru, Hyderabad, Gurugram +2
View questionsProduct
Meta
Playwright Testing interview questions
Gurugram, Bengaluru, Hyderabad +1
View questionsProduct
Dream11
Playwright Testing interview questions
Mumbai
View questionsProduct
ServiceNow
Playwright Testing interview questions
Hyderabad, Bengaluru
View questionsProduct
ThoughtSpot
Playwright Testing interview questions
Bengaluru
View questionsProduct
Uber
Playwright Testing interview questions
Bengaluru, Hyderabad, Gurugram
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