01
How do you run tests in Docker?
Show answer
Use the official Playwright image which contains browsers and dependencies, mount the project and run npx playwright test for consistent CI environments.
ICICI Bank Playwright Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About ICICI Bank hiring for Playwright Testing roles
ICICI Bank is a large Indian private sector bank offering retail, corporate, digital and international banking. Its technology, analytics and operations teams work on products like iMobile Pay, credit decisioning, fraud detection and customer analytics. It hires for data analysts, risk analysts, testers, software engineers and management trainees.
For Playwright Testing roles, this ICICI Bank practice set focuses most on Framework Design and CI/CD (6), Fixtures and Hooks (5), JavaScript and TypeScript (5), Network Mocking (5). It has 2 easy, 33 medium, 5 hard questions, so you can start easy and work up to the harder ones.
- Company type
- Banking & finance
- Headquarters
- Mumbai, India
- Main India offices
- Mumbai, Hyderabad, Chennai, Bengaluru
ICICI Bank Playwright Testing interview process
- Online assessment (aptitude + domain)
- Technical or functional interview
- Managerial round
- HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for ICICI BankStart 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 does the webServer option do?
Show answer
webServer tells Playwright to start your app with a command, such as npm run start, and wait until a URL or port responds before running tests. reuseExistingServer: !process.env.CI lets you use an already running dev server locally. You can define several servers, for example frontend and a mock API. It shuts them down after the run.
03
What do maxDiffPixels, maxDiffPixelRatio and threshold control in a screenshot comparison?
Show answer
threshold sets how different two pixels can be in colour, from 0 to 1, before they count as different; the default is 0.2. maxDiffPixels allows a fixed number of differing pixels, and maxDiffPixelRatio allows a fraction of the total image. Keep them tight so real regressions fail, and set them in the expect section of the config rather than loosening single tests one by one.
04
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.
05
How does visual testing work in Playwright?
Show answer
await expect(page).toHaveScreenshot('home.png') compares against a baseline image; tune maxDiffPixels and mask dynamic areas like dates.
06
Describe a time strict TypeScript types caught a bug in your test code.
Show answer
Situation: our API helpers returned loosely typed objects and tests often read fields that no longer existed. Task: make helpers safer. Action: I added response interfaces, turned on strict mode and replaced any with unknown plus type guards. Result: the compiler immediately showed eleven tests reading a renamed field, which had been passing because they compared undefined with undefined. We fixed them before the next release.
07
How does Playwright's trace viewer help?
Show answer
It records screenshots, DOM snapshots, network calls and actions per step so you can replay a failed run and see exactly what happened.
08
When should you use getByTestId?
Show answer
Use getByTestId when no user-facing locator is stable or unique, for example icon-only buttons, dynamic grids or canvas wrappers. It matches the data-testid attribute by default, and you can change the attribute name with testIdAttribute in the config. Test ids are very stable but users never see them, so prefer role, label or text first and keep test ids as a fallback.
09
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.
10
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.
11
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.
12
What is async/await?
Show answer
Syntax over Promises: an async function returns a Promise and await pauses until it resolves. Every Playwright action returns a Promise, so you await each step.
13
How do you send authentication headers?
Show answer
Set extraHTTPHeaders in the config or pass headers per request, for example Authorization: Bearer token fetched in a setup step.
14
How do you structure environment-specific configs in Playwright?
Show answer
Use dotenv files per environment, read them in playwright.config and set baseURL and credentials from variables, selecting with an ENV flag.
15
How do you change part of a real API response?
Show answer
await page.route('**/api/profile', async route => {
const response = await route.fetch();
const json = await response.json();
json.plan = 'premium';
await route.fulfill({ response, json });
});
await page.goto('/account');
await expect(page.getByText('Premium plan')).toBeVisible();
16
Why choose Playwright over Selenium?
Show answer
Auto-waiting, a built-in test runner, Chromium/Firefox/WebKit with one API, network interception, the trace viewer and parallel runs out of the box — usually faster and less flaky.
17
How do you test a component that reads from a global state store?
Show answer
Wrap the mounted component in the store provider inside beforeMount, and use hooksConfig to choose the initial state for each test, such as a logged-in user or an empty cart. Build the store in the browser side of index.tsx, not in the test file. Then interact with the component and assert on the rendered output rather than reading store internals.
18
Component tests fail because imports like @/utils cannot be resolved, though the app builds fine. How do you fix it?
Show answer
The app uses a bundler alias that the component test bundle does not know. Add the same alias in ctViteConfig under resolve.alias, or reuse the project's Vite config by importing it. Also make sure tsconfig paths match, so editors and type checks agree. After that, clear the cache folder that the component bundler writes under playwright/.cache so the bundle rebuilds.
19
What does fullyParallel change?
Show answer
By default Playwright runs test files in parallel but tests within one file in order in a single worker. fullyParallel: true lets tests inside a file run in parallel across workers too. It speeds up suites with big files, but every test must be independent. You can also enable it per file with test.describe.configure({ mode: 'parallel' }).
20
How do you use test.step and test annotations?
Show answer
test.step groups actions into named steps in reports; annotations such as test.skip, test.fixme and test.slow communicate intent and adjust behaviour.
21
How do you validate response headers?
Show answer
Use response.headers() for an object of lower-cased header names, or headersArray() for duplicates. Assert content-type contains application/json, cache-control matches the policy, and security headers such as strict-transport-security are present. Also check that sensitive headers like server version are not exposed. Header checks catch configuration bugs that body checks miss.
22
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.
23
Write a test that checks keyboard Tab order through a login form.
Show answer
test('login form is keyboard friendly', async ({ page }) => {
await page.goto('/login');
await page.getByLabel('Email').focus();
await page.keyboard.press('Tab');
await expect(page.getByLabel('Password')).toBeFocused();
await page.keyboard.press('Tab');
await expect(page.getByRole('button', { name: 'Sign in' })).toBeFocused();
await page.keyboard.press('Enter');
});
24
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.
25
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' } });
26
How do you verify that an API returns consistent data across two versions of an endpoint?
Show answer
Call both versions, for example /v1/orders/42 and /v2/orders/42, with the same test data. Map the fields that should match, since names may differ, and compare them with toEqual. Also assert that fields removed in v2 are really absent and new ones have correct types. Running this during a migration catches breaking changes before clients switch.
27
One shard finishes in 4 minutes and another takes 15. How do you balance them?
Show answer
Check whether fullyParallel is off, because file-level sharding puts big files together. Turn it on if tests are independent, or split the largest files. Use reportSlowTests and the merged report's durations to find heavy files, and move slow setup into API calls or shared storage state. Also check that one shard is not getting all the tests of a slow project such as WebKit.
28
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.
29
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.
30
How do you handle rate limits or slow APIs in tests?
Show answer
Add retries with backoff for the API step, set a suitable timeout, and use mocks for non-critical dependencies.
31
Why turn on strict mode in tsconfig for a test project?
Show answer
strict enables checks such as strictNullChecks and noImplicitAny. They catch bugs like using a value that may be undefined, missing parameters or wrong property names before tests run. In a large suite this saves debugging time and makes page objects safer to refactor. Pair it with the no-floating-promises lint rule to catch missing awaits.
32
What is the difference between page, context and browser?
Show answer
A browser is the engine instance; a context is an isolated session (cookies, storage); a page is a tab inside a context.
33
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.
34
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.
35
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.
36
What are global setup and teardown?
Show answer
Scripts that run once before or after the whole run, for seeding data, starting services or creating authentication state.
37
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.
38
What does eslint-plugin-playwright help with?
Show answer
It is a lint plugin with rules for common Playwright mistakes, such as missing await on assertions, leftover test.only or page.pause, forced clicks, fixed waits with waitForTimeout and element handles instead of locators. Running it in pull requests stops bad patterns before review. Teams usually enable the recommended rule set and add a few stricter rules over time.
39
What is ctViteConfig and when do you need it?
Show answer
ctViteConfig is an option in the use block of playwright-ct.config.ts that passes extra Vite settings to the component bundle. You need it when the app relies on path aliases, plugins, environment defines or special asset handling that Playwright's default Vite setup does not know about. A typical case is adding resolve.alias so imports like @/components work in tests.
40
What happens before and after await use() in a fixture?
Show answer
Code before await use(value) is setup and runs before the test. use hands the value to the test and waits while the test runs. Code after it is teardown and runs when the test finishes, even if it failed. This keeps setup and cleanup for one resource in one place, which is cleaner than a separate beforeEach and afterEach pair.
Tips to crack the ICICI Bank Playwright Testing interview
- Learn Indian banking basics such as loan types, NPAs, CASA ratio and RBI regulations for interviews.
- Use iMobile Pay and think about features you would test or improve as a QA or analyst candidate.
- Revise SQL and Excel with examples on customer segmentation, credit risk or campaign analysis.
- 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; ICICI Bank interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the ICICI Bank Playwright Testing interview?
Candidates usually go through 4 stages: Online assessment (aptitude + domain); Technical or functional interview; 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 ICICI Bank Playwright Testing interview?
This practice set leans on Framework Design and CI/CD (6), Fixtures and Hooks (5), JavaScript and TypeScript (5), Network Mocking (5). Revise those first, then practise explaining one or two of your own projects end to end, because most ICICI Bank interviewers ask you to walk through real work.
Are these the exact questions asked at ICICI Bank?
No. These are curated practice questions that match the skills and difficulty usually tested in banking & finance interviews like ICICI Bank's. They are not a leaked or verified list of past questions.
Where does ICICI Bank hire Playwright Testing professionals in India?
ICICI Bank has large teams in Mumbai, Hyderabad, Chennai, Bengaluru. Openings and locations change often, so check the ICICI Bank careers page and filter by city and experience.
Playwright Testing questions for similar companies
Banking & finance
HSBC
Playwright Testing interview questions
Hyderabad, Pune, Bengaluru
View questionsBanking & finance
Deutsche Bank
Playwright Testing interview questions
Pune, Bengaluru, Mumbai +1
View questionsBanking & finance
HDFC Bank
Playwright Testing interview questions
Mumbai, Chennai, Bengaluru
View questionsBanking & finance
Citi
Playwright Testing interview questions
Pune, Chennai, Mumbai +2
View questionsBanking & finance
Barclays
Playwright Testing interview questions
Pune, Chennai, Noida +1
View questionsBanking & finance
Wells Fargo
Playwright Testing interview questions
Hyderabad, Bengaluru, Chennai
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