01
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.
Thoughtworks Playwright Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Thoughtworks hiring for Playwright Testing roles
Thoughtworks is a global technology consultancy known for agile software delivery, continuous delivery and its Technology Radar publication. It works on custom software, data platforms and digital transformation for enterprise clients. In India it hires for developers, quality analysts, data engineers and data scientists. Teams usually work closely with client engineers.
For Playwright Testing roles, this Thoughtworks practice set focuses most on API Testing (8), Visual & Accessibility Testing (7), Playwright Core (6), Debugging and Trace Viewer (5). It has 1 easy, 33 medium, 6 hard questions, so you can start easy and work up to the harder ones.
- Company type
- Consulting
- Headquarters
- Chicago, Illinois, USA
- Main India offices
- Pune, Bengaluru, Chennai, Gurugram, Hyderabad
Thoughtworks Playwright Testing interview process
- Online coding assessment
- Code pairing round
- Technical interview
- Cultural fit or social change round
- Leadership round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for ThoughtworksStart 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
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 },
});
});
03
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.
04
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' } });
05
Explain the event loop.
Show answer
JavaScript runs one call stack and uses queues for async work; the event loop pushes callbacks from the microtask (promises) and task queues when the stack is empty.
06
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.
07
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.
08
A test checks a price that is formatted differently per locale. How do you make the assertion robust?
Show answer
Fix the locale for the test with the locale and timezoneId options so the format is predictable. Build the expected string with Intl.NumberFormat using the same locale, rather than hard-coding it. If you test several locales, run them as projects or parameterised tests. For business logic, also assert the raw number through the API response.
09
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([]);
});
10
How do you add or change request headers for only some requests?
Show answer
Register a route for the matching URLs and call route.continue({ headers: { ...route.request().headers(), 'x-test-mode': 'true' } }). Other requests are untouched. For headers on every request, use extraHTTPHeaders in the config instead. This is useful for feature toggles, tenant ids or bypass tokens that only certain endpoints accept.
11
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.
12
How do you send a POST request with a JSON body?
Show answer
await request.post('/api/users', { data: { name: 'Asha' } }) automatically sets JSON headers and serialises the payload.
13
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
14
Describe a time an API changed without notice and broke your tests.
Show answer
Situation: dozens of tests failed after a field was renamed from user_name to username. Task: fix quickly and prevent repeats. Action: I updated the shared types and helper, so the fix touched two files, and proposed schema checks on key endpoints plus a heads-up in release notes. Result: the next breaking change was caught in the pull request.
15
Show a config with a setup project and a browser project that reuses its login.
Show answer
projects: [
{ name: 'setup', testMatch: /auth\.setup\.ts/ },
{
name: 'chromium',
use: { ...devices['Desktop Chrome'], storageState: '.auth/user.json' },
dependencies: ['setup'],
},
],
16
What actionability checks does Playwright run before a click?
Show answer
Before clicking, Playwright waits until the element is attached, visible, stable (not animating), enabled and able to receive events (not covered by another element). It also scrolls it into view. fill checks for an editable element. If the checks are not met before the timeout, the action fails with a log of what was missing.
17
What is the difference between click and dispatchEvent?
Show answer
click simulates a real user click with actionability checks; dispatchEvent fires a DOM event directly without those checks.
18
Why should you start waitForResponse before the action that triggers it?
Show answer
If you click first and then wait, the response may already have arrived, so the wait misses it and times out. Create the promise first, then act, then await it: const resp = page.waitForResponse('**/api/cart'); await addButton.click(); await resp. waitForRequest works the same way for outgoing requests.
19
What are the trade-offs of trace 'on' versus 'retain-on-failure' in CI?
Show answer
'on' records and keeps every trace, which costs time, disk space and artifact storage for thousands of passing tests. 'retain-on-failure' still records everything but deletes traces of passing tests, so cost is mainly runtime. 'on-first-retry' is cheapest but gives no trace for a first failure without retries. Most teams use on-first-retry with retries in CI.
20
A designer changes the primary button colour and 300 visual tests fail at once. How do you handle it?
Show answer
First confirm the change is intended and check a sample of diffs to make sure nothing else moved. Then regenerate baselines in the CI Docker environment in a separate commit, so reviewers can see only image changes. Longer term, reduce the count: most of those tests should not snapshot full pages. Keep a few page-level shots and move detail checks to component-level screenshots of key states.
21
Write an API test with the request fixture.
Show answer
test('get user', async ({ request }) => {
const res = await request.get('/api/users/1');
expect(res.ok()).toBeTruthy();
expect((await res.json()).id).toBe(1);
});
22
An API returns 200 but the body contains an error field. How should your test catch this?
Show answer
Never trust status alone. Assert the body structure, for example that error is absent and data has the expected fields, ideally with a schema check. Report the issue, because returning 200 for errors breaks clients and monitoring. Add a helper that validates both status and body shape so every test checks it consistently.
23
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.
24
What do toHaveAccessibleName and toHaveAccessibleDescription check?
Show answer
They assert the name and description that assistive technology computes for an element, using the accessibility tree rather than raw attributes. The name may come from a label, aria-label, aria-labelledby or inner text, and the description often from aria-describedby. For example an icon-only close button should have the name Close. These checks catch problems that a plain text assertion would miss.
25
How do you set test timeouts?
Show answer
Use timeout and expect.timeout in config, test.setTimeout() for one test and test.slow() for known slower tests.
26
What is a generic type parameter constraint, such as T extends object?
Show answer
A constraint limits what types a generic can accept. function pick<T extends object, K extends keyof T>(obj: T, key: K) only accepts objects and keys that exist on them, so pick(user, 'emial') fails at compile time. In test helpers this catches typos in field names and keeps return types precise without using any.
27
Your test clicks a button before the page's JavaScript has attached its handler, so nothing happens. What do you do?
Show answer
This is a hydration problem: the button is visible and enabled but not yet interactive. Wait for a signal that the app is ready, such as a loaded data request or a visible element that only appears after hydration, then click. A better fix is to report it to developers, because real users hit the same issue. Avoid fixed waitForTimeout calls.
28
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.
29
What is an ARIA snapshot and how does toMatchAriaSnapshot work?
Show answer
An ARIA snapshot is a YAML description of the accessibility tree for a part of the page: roles, names and states such as checked or level. toMatchAriaSnapshot compares the live tree of a locator against that template, and partial templates or regular expressions can be used for changing text. It tests structure and semantics, so it survives styling changes that would break a pixel screenshot.
30
The app logs in through a third-party OAuth pop-up. How do you automate it?
Show answer
For most tests, avoid the pop-up: get a session through a test login API or a test identity provider and save it with storageState. Keep one test for the real flow, using const popup = page.waitForEvent('popup') before clicking, then fill the provider's form inside popup. Third-party pages can change and add captchas, so limit how often you depend on them.
31
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.
32
How do you handle date pickers and custom dropdowns?
Show answer
Click to open the control, then use getByRole('option') or a text locator for the target item, instead of relying on fragile index-based selectors.
33
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.
34
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.
35
How do you test pagination or chained API calls?
Show answer
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.
36
What are the options for the trace setting in playwright.config?
Show answer
Values are 'off', 'on', 'retain-on-failure', 'on-first-retry' and 'on-all-retries'. 'on-first-retry' records only when a failed test is retried, which keeps the normal run fast and gives a trace for flaky failures. 'retain-on-failure' records every test but keeps only failed ones. 'on' records everything and is mainly for local investigation.
37
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.
38
How do you write data-driven API tests with many inputs?
Show answer
const cases = [
{ email: '', status: 400 },
{ email: 'bad', status: 400 },
{ email: 'ok@test.in', status: 201 },
];
for (const c of cases) {
test(`signup with '${c.email}'`, async ({ request }) => {
const res = await request.post('/api/signup', { data: { email: c.email } });
expect(res.status()).toBe(c.status);
});
}
39
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.
40
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([]);
});
Tips to crack the Thoughtworks Playwright Testing interview
- Practise pair programming with test-driven development, since Thoughtworks interviews often include coding together with an interviewer.
- Read the latest Thoughtworks Technology Radar and form opinions on a few tools or techniques it lists.
- Prepare to discuss social and economic justice values, which Thoughtworks openly includes in its culture discussions.
- 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; Thoughtworks interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Thoughtworks Playwright Testing interview?
Candidates usually go through 5 stages: Online coding assessment; Code pairing round; Technical interview; Cultural fit or social change round; Leadership 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 Thoughtworks Playwright Testing interview?
This practice set leans on API Testing (8), Visual & Accessibility Testing (7), Playwright Core (6), Debugging and Trace Viewer (5). Revise those first, then practise explaining one or two of your own projects end to end, because most Thoughtworks interviewers ask you to walk through real work.
Are these the exact questions asked at Thoughtworks?
No. These are curated practice questions that match the skills and difficulty usually tested in consulting interviews like Thoughtworks's. They are not a leaked or verified list of past questions.
Where does Thoughtworks hire Playwright Testing professionals in India?
Thoughtworks has large teams in Pune, Bengaluru, Chennai, Gurugram, Hyderabad. Openings and locations change often, so check the Thoughtworks careers page and filter by city and experience.
Playwright Testing questions for similar companies
Consulting
Grant Thornton Bharat
Playwright Testing interview questions
Gurugram, Mumbai, Bengaluru +3
View questionsConsulting
PwC
Playwright Testing interview questions
Kolkata, Bengaluru, Mumbai +2
View questionsConsulting
ZS Associates
Playwright Testing interview questions
Pune, Gurugram, Bengaluru
View questionsConsulting
Deloitte
Playwright Testing interview questions
Hyderabad, Bengaluru, Mumbai +2
View questionsConsulting
KPMG
Playwright Testing interview questions
Gurugram, Bengaluru, Mumbai +2
View questionsConsulting
EY
Playwright Testing interview questions
Bengaluru, Kolkata, Gurugram +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