01
How do you mock third-party APIs in UI tests?
Show answer
Use page.route to intercept the call and fulfil it with fixed JSON so tests do not depend on external systems.
Ola Playwright Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Ola hiring for Playwright Testing roles
Ola, operated by ANI Technologies, is an Indian ride-hailing platform offering cabs, auto-rickshaws and bike taxis, and it is part of a group that also includes Ola Electric and Krutrim. Its technology and analytics teams work on pricing, dispatch, maps and driver supply. It hires for software engineers, SDETs, business analysts and data scientists.
For Playwright Testing roles, this Ola practice set focuses most on Network Mocking (7), API Testing (5), Framework Design and CI/CD (5), Locators and Assertions (5). It has 2 easy, 28 medium, 10 hard questions, so you can start easy and work up to the harder ones.
- Company type
- Product
- Headquarters
- Bengaluru, India
- Main India offices
- Bengaluru
Ola Playwright Testing interview process
- Online coding assessment
- Technical round 1 (DSA)
- Technical round 2 (design or case)
- Hiring manager round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for OlaStart 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 test API error scenarios?
Show answer
Send invalid payloads or missing auth and assert 400, 401 or 404 codes and the error message bodies.
03
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.
04
How do you handle secrets such as passwords and tokens in CI?
Show answer
Store them in the CI system's secret store and pass them as environment variables, never in the repository or config files. Read them through process.env and fail fast if they are missing. Use dedicated test accounts with limited rights. Avoid printing them in logs, and make sure traces and screenshots do not expose them in reports.
05
How do you reduce the execution time of a 2000-test suite?
Show answer
Run in parallel with sharding, reuse authentication state, set up data through APIs, avoid unnecessary waits, run smoke on every commit and the full suite nightly.
06
How do you provide page objects as fixtures?
Show answer
type Pages = { loginPage: LoginPage; cartPage: CartPage };
export const test = base.extend<Pages>({
loginPage: async ({ page }, use) => {
await use(new LoginPage(page));
},
cartPage: async ({ page }, use) => {
await use(new CartPage(page));
},
});
// test('x', async ({ loginPage }) => { ... })
07
How do you test geolocation, permissions and time zones?
Show answer
Set them in the context options (geolocation, permissions, timezoneId, locale) to simulate users from other regions.
08
What does the DEBUG=pw:api environment variable do?
Show answer
Setting DEBUG=pw:api prints detailed logs of every Playwright API call to the terminal, including waits and retries inside actions. It helps when a test hangs and you need to see exactly which step is waiting and why. Other channels such as pw:browser show browser process output. It is noisy, so use it only while investigating.
09
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.
10
How do you verify a page's URL and title after navigation?
Show answer
await page.getByRole('link', { name: 'Orders' }).click();
await expect(page).toHaveURL(/\/orders$/);
await expect(page).toHaveTitle('My Orders | Shop');
// both retry, so no need to wait for navigation manually
11
How do you share cookies between API login and UI?
Show answer
Log in with request.post, call request.storageState(), and create a browser context using that state.
12
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.
13
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.
14
How do you run a single test or file in Playwright?
Show answer
npx playwright test tests/login.spec.ts, add -g "test title" to match a name, or use test.only while debugging.
15
The team wants to replace all end-to-end tests with component tests to save time. What do you advise?
Show answer
Agree to move detailed UI checks down to component tests, because they are faster and more precise. But keep a thin layer of end-to-end tests for critical journeys like signup, checkout and payment, since component tests use mocked data and cannot catch broken APIs, routing or deployment issues. Decide per risk, measure runtime savings, and track escaped defects after the change.
16
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.
17
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.
18
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.
19
How would you handle a very flaky element that appears after an animation?
Show answer
Rely on auto-waiting plus a web-first assertion on the final state, disable animations in config for tests and avoid fixed timeouts.
20
Two test files edit the same global settings page and break each other when run in parallel. How do you handle it?
Show answer
The best fix is to remove the shared resource, for example by giving each test its own tenant or user whose settings it can change. If that is impossible, put those tests in one file with test.describe.configure({ mode: 'serial' }), or in a separate project that runs with one worker after the main project. Document why, so the exception does not quietly spread.
21
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.
22
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.
23
How would you design a visual testing strategy for a large web application?
Show answer
Snapshot stable, high-value screens and shared components, not every page. Render baselines only in a pinned Docker image, mask or mock dynamic data, and disable animations. Keep visual tests in their own project or tag so they can run on pull requests touching UI code. Define owners for baseline reviews and keep thresholds strict in config. Combine with functional assertions, because pictures alone do not tell you why something broke.
24
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.
25
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.
26
How do you test how the UI handles a 500 error from the orders API?
Show answer
Mock the endpoint with route.fulfill({ status: 500, json: { message: 'Server error' } }), then open the page. Assert the user sees a friendly error message and a retry button, and that no broken half-rendered table appears. Then make the retry return 200 and check the data loads. This covers a path that is hard to trigger on a real server.
27
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.
28
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.
29
Mocked responses drift from the real API and tests pass while production breaks. How do you prevent this?
Show answer
Generate mock data from the API schema or real recorded responses instead of hand-writing it. Validate mocks against the OpenAPI schema in a unit test. Add contract tests on the backend side and re-record HAR files on a schedule. Keep a few unmocked end-to-end tests that run after each deploy. Treat mock files as code with owners and reviews.
30
How do you mock network traffic using a HAR file?
Show answer
Record once with page.routeFromHAR('data/orders.har', { url: '**/api/**', update: true }) while running against a real server. Later runs replay the saved responses from the HAR instead of hitting the backend. You can edit the stored JSON to create edge cases. Re-record when the API changes, otherwise the replay drifts from reality.
31
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.
32
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
33
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.
34
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.
35
How do you test a flow that needs two user roles, such as an admin and a customer, in one test?
Show answer
Create two browser contexts in the same test, each with its own storageState file, for example admin.json and user.json made by a setup project. Wrap them in fixtures like adminPage and userPage so tests stay short. The admin approves an order in one context and the customer sees the update in the other, with fully separate cookies.
36
What does the JSON reporter output and how would you use it?
Show answer
The JSON reporter writes the full suite tree with every test, its status, retries, duration, errors and attachment paths into one file. Teams parse it in scripts to post a summary to chat, to collect flaky tests that passed on retry, or to push results to a database for trends. Set outputFile so the JSON does not mix with console output.
37
Component and end-to-end tests run together and slow down every commit. How do you separate them?
Show answer
Give them separate configs, such as playwright-ct.config.ts with its own testDir for component specs and playwright.config.ts for end-to-end tests, because component tests also need the bundler options and framework test import. In CI, run component tests on every commit as a fast job and end-to-end tests later or in parallel. Shared settings like reporters can live in a common module both configs import.
38
Ten engineers write tests and quality varies a lot. How do you keep the framework consistent?
Show answer
Write a short contribution guide with examples. Add ESLint with the Playwright plugin and the no-floating-promises rule, plus Prettier, enforced in CI. Require reviews from framework owners for shared fixtures and page objects. Provide generators or templates for new page objects, and run regular sessions to review flaky tests together.
39
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.
40
How do you handle token refresh in long API test runs?
Show answer
Fetch tokens in a fixture with expiry tracking and refresh it when it is about to expire, keeping tests unaware of the details.
Tips to crack the Ola Playwright Testing interview
- Prepare marketplace cases on driver supply, rider demand and surge pricing in Indian cities.
- Practise DSA problems on graphs and heaps, which relate to dispatch and route optimisation.
- Read about Ola Maps and Krutrim AI efforts, which are recent technology focus areas for the group.
- 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; Ola interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Ola Playwright Testing interview?
Candidates usually go through 4 stages: Online coding assessment; Technical round 1 (DSA); Technical round 2 (design or case); Hiring manager 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 Ola Playwright Testing interview?
This practice set leans on Network Mocking (7), API Testing (5), Framework Design and CI/CD (5), Locators and Assertions (5). Revise those first, then practise explaining one or two of your own projects end to end, because most Ola interviewers ask you to walk through real work.
Are these the exact questions asked at Ola?
No. These are curated practice questions that match the skills and difficulty usually tested in product interviews like Ola's. They are not a leaked or verified list of past questions.
Where does Ola hire Playwright Testing professionals in India?
Ola has large teams in Bengaluru. Openings and locations change often, so check the Ola careers page and filter by city and experience.
Playwright Testing questions for similar companies
Product
InMobi
Playwright Testing interview questions
Bengaluru
View questionsProduct
Red Hat
Playwright Testing interview questions
Pune, Bengaluru
View questionsProduct
Rapido
Playwright Testing interview questions
Bengaluru
View questionsProduct
Salesforce
Playwright Testing interview questions
Hyderabad, Bengaluru, Mumbai +1
View questionsProduct
Nutanix
Playwright Testing interview questions
Bengaluru, Pune
View questionsProduct
Druva
Playwright Testing interview questions
Pune
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