Skip to content

Software Testing Interview Questions for IT services Companies

40 questions weighted to the interview style of it services companies — 14 easy, 25 medium, 1 hard.

How it services companies interview for Software Testing

IT services companies hire in large numbers, often in campus or bulk drives. Interviews usually start with an online aptitude and coding test, then one or two technical rounds on fundamentals and your projects, then HR. Clear basics and good communication matter more than rare, advanced topics.

This set focuses on Agile, SQL and API Testing (7), Testing Types (7), STLC and Test Planning (5), Test Case Design (5).

Technical interview HR round Managerial round Coding test Online assessment (aptitude + reasoning)
Solved — it services companiesStart 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
01

What is a sprint retrospective?

Save to ▾
Show answer
A team meeting at the end of a sprint to discuss what went well, what did not and what to improve next.
02

What is Agile testing?

Save to ▾
Show answer
Testing that is continuous and collaborative within each sprint, with testers working alongside developers and product owners from the start.
03

How do you convert existing manual test cases into automated scripts?

Save to ▾
Show answer
Pick a small set of stable, high-value regression cases first. Review each one: make steps precise, remove judgement-based checks and define clear expected results. Prepare test data that the script can create and clean up. Build reusable page objects and helpers for common steps like login. Automate, run several times to confirm stability, then link each script to its manual case ID and mark the manual case as automated.
04

How do you decide the priority of test cases?

Save to ▾
Show answer
By business criticality, usage frequency, defect history, risk and dependencies, running high-priority cases first.
05

How do you capture logs from an Android device for a bug report?

Save to ▾
Show answer
Enable developer options and USB debugging, connect the phone and confirm it is visible with adb devices. Clear old logs with adb logcat -c, reproduce the bug, then save logs with adb logcat -d > crash_log.txt, filtering by the app package or error level if needed. For a crash, search for FATAL EXCEPTION. Attach the log, device model, OS version, app version and a screen recording to the bug.
06

What are stubs and drivers?

Save to ▾
Show answer
Both are temporary pieces of code used in integration testing when some modules are not ready. A stub replaces a called lower-level module and returns fixed responses, used in top-down testing; for example, a stub payment service that always returns success. A driver replaces a calling higher-level module and sends inputs to the module under test, used in bottom-up testing. In API testing, mock servers play the role of stubs.
07

What is a test plan and what does it contain?

Save to ▾
Show answer
A document defining scope, approach, resources, schedule, entry and exit criteria, risks and deliverables of testing.
08

What do you check during UI or visual testing?

Save to ▾
Show answer
Check alignment, spacing, fonts, colours and images against the design. Verify text is not cut off or overlapping, buttons and links look clickable and show hover and disabled states, and error messages appear in the right place. Check responsive behaviour on different screen widths and zoom levels. Confirm icons and images load and have alt text. Compare with the design file and take screenshots for any differences.
09

How do you test password policy and account lockout?

Save to ▾
Show answer
Try passwords that break each rule: too short, no digit, no special character and common passwords, and check clear messages. Verify the password is masked and not shown in the URL or logs. Enter the wrong password up to the limit and confirm the account locks for the defined time or until reset. Check that the error message does not reveal whether the username exists and that the lockout counter resets after a successful login.
10

SQL: find the second highest salary from an employees table.

Save to ▾
Show answer
SELECT MAX(salary) AS second_highest FROM employees WHERE salary < (SELECT MAX(salary) FROM employees); -- alternative using DENSE_RANK SELECT DISTINCT salary FROM ( SELECT salary, DENSE_RANK() OVER (ORDER BY salary DESC) AS rnk FROM employees ) t WHERE rnk = 2;
11

How do you test a country dropdown that controls a dependent state dropdown?

Save to ▾
Show answer
Check the state list is empty or disabled until a country is selected. Select a country and verify the correct states load. Change the country and confirm the old state selection is cleared and the new list loads. Test countries with no states, a long list with scrolling and search, and default values on page load. Submit the form and verify the saved values, then reload and check both dropdowns keep the saved selection.
12

How do you do cross-browser testing and choose which browsers to cover?

Save to ▾
Show answer
Use analytics to pick browsers and versions that most real users have, plus the ones listed in the requirement, usually the latest two versions of major desktop and mobile browsers. Run the main flows on each and check layout, fonts, forms, date pickers, file upload and JavaScript errors in the console. Use responsive mode for screen sizes, and real devices or a cloud device lab for mobile browsers.
13

Which basic Git commands should a manual tester learn before working on automation?

Save to ▾
Show answer
Start with: git clone to copy the test repository; git pull to get the latest changes; git checkout -b feature/login-tests to create a branch; git status and git diff to see changes; git add and git commit -m to save work with a message; and git push to send the branch so you can raise a pull request for review. Also learn to resolve simple merge conflicts and never commit passwords.
14

What does the absence-of-errors fallacy mean?

Save to ▾
Show answer
It means that finding and fixing many defects does not guarantee success if the system itself does not meet user needs. A bug-free product built on wrong or misunderstood requirements is still a failure. For example, a perfectly working report that shows the wrong business metric is useless to the client. This is why testers validate against real user expectations, not just the written specification.
15

What is the difference between a Deferred bug and a Rejected bug?

Save to ▾
Show answer
A deferred bug is valid, but the team decides to fix it in a later release because of low priority, time limits or low impact. It stays in the backlog with a target version. A rejected bug is one the developer or triage team considers invalid: working as designed, not reproducible, a duplicate or caused by wrong test data. Testers should check the reason for rejection and challenge it with evidence if they disagree.
16

What is a regression bug and how do you track it in Jira?

Save to ▾
Show answer
A regression bug is a feature that worked before but broke after a new change, such as login failing after a profile page update. It is usually treated with higher priority because it affects existing users. In Jira, add a label such as regression, set the affected version and link it to the story or change that caused it. Tracking these labels over time shows where regression coverage is weak.
17

What is Appium at a high level?

Save to ▾
Show answer
Appium is an open-source tool for automating native, hybrid and mobile web apps on Android and iOS using the WebDriver protocol. Tests can be written in Java, Python, JavaScript and other languages, and it uses platform drivers such as UiAutomator2 for Android and XCUITest for iOS. It can run on emulators, simulators, real devices and cloud device farms. Stable accessibility IDs make the best locators for it.
18

What is the classification tree method?

Save to ▾
Show answer
The classification tree method breaks the input domain into classifications (aspects like payment type, user type, device) and classes (values like card, UPI, wallet). These are drawn as a tree, and test cases are formed by picking one class from each classification in a combination table. It makes coverage visible, helps reviewers spot missing classes and combines well with pairwise selection to keep the number of test cases manageable.
19

What is a bug triage meeting?

Save to ▾
Show answer
A regular review where QA, development and product assess new bugs and decide severity, priority, owner and target release.
20

What is compliance testing?

Save to ▾
Show answer
Compliance testing checks that software meets external laws, standards or internal policies, not just functional requirements. Examples include payment security standards for card data, data protection rules for personal data, accessibility guidelines and RBI rules for banking apps. Testers verify items such as consent capture, data retention, audit logs and masking. Findings are usually documented as evidence for auditors, so traceability and clear records matter as much as the tests.
21

What is shift-left testing and why is it cheaper?

Save to ▾
Show answer
Shift-left means starting testing activities earlier in the life cycle: reviewing requirements, joining design discussions and writing tests before code is complete. A defect found in requirements may cost a short conversation to fix, while the same defect found in production may need a hotfix, data correction and customer support. Testers shift left by asking questions in grooming, defining acceptance criteria and reviewing designs.
22

What is a Three Amigos session?

Save to ▾
Show answer
Three Amigos is a short meeting where a business person or product owner, a developer and a tester discuss a story before development. The business explains the need, the developer considers how to build it and the tester asks what could go wrong and how it will be verified. The output is clear acceptance criteria and example scenarios. It prevents misunderstandings and reduces bugs found late.
23

How do you review test cases?

Save to ▾
Show answer
Peer review for clarity, coverage of requirements, correct expected results, test data and traceability, then update and baseline them.
24

How do you test a web page with a screen reader?

Save to ▾
Show answer
Turn on the screen reader, for example NVDA with a browser, and listen rather than look. Navigate by headings to check the structure is logical, by landmarks to find main regions and by Tab through controls. Each control should announce a clear name, role and state, such as 'Subscribe, checkbox, not checked'. Check images, form errors, dynamic updates like cart counts and dialogs. Note exactly what was announced in bug reports.
25

The test environment is down for two days just before release. What do you do?

Save to ▾
Show answer
Escalate immediately with the impact on the schedule. While it is down, prepare test data, review and update test cases, and test what you can elsewhere: API tests against another environment, UI on a developer machine or a staging copy. Track the lost hours in the status report. When the environment returns, run smoke first, then the prioritised list, and ask whether the release date or scope needs to change.
26

What are positive and negative test cases?

Save to ▾
Show answer
Positive cases use valid inputs to confirm expected behaviour; negative cases use invalid inputs to confirm the system handles errors gracefully.
27

What is localisation and internationalisation testing?

Save to ▾
Show answer
Internationalisation tests that the product can support many languages and formats; localisation tests that a specific locale is correct for text, currency, date and layout.
28

What is colour contrast ratio and what values does WCAG require?

Save to ▾
Show answer
Contrast ratio compares the brightness of text and its background, from 1:1 to 21:1. WCAG AA requires at least 4.5:1 for normal text and 3:1 for large text, which is about 18 point or 14 point bold. User interface parts such as input borders and icons need 3:1. AAA raises text to 7:1. Testers check this with a contrast checker or browser developer tools, including placeholder, disabled and hover states.
29

What are common HTTP status codes?

Save to ▾
Show answer
200 OK, 201 Created, 204 No Content, 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 500 Internal Server Error.
30

What is a locator and what types of locators exist?

Save to ▾
Show answer
A locator tells the automation tool how to find an element on the page so it can click, type or check it. Common types are ID, name, CSS selector, XPath, link text, and in modern tools role-based locators such as a button with name Login, plus label, placeholder and test ID locators. A good locator is unique, readable and unlikely to change when the page design changes.
31

What does INVEST mean for user stories?

Save to ▾
Show answer
INVEST is a checklist for good user stories: Independent, Negotiable, Valuable, Estimable, Small and Testable. For testers, testable is the most important: a story must have clear acceptance criteria so you can say pass or fail. Small stories are easier to test within a sprint. If a story fails INVEST, raise it in refinement rather than discovering the gaps during testing.
32

What is a traceability matrix?

Save to ▾
Show answer
A grid mapping requirements to test cases and defects, proving every requirement is tested.
33

What is the difference between quality assurance and quality control?

Save to ▾
Show answer
Quality assurance is process-oriented and preventive: it sets standards, reviews and checklists so defects are not introduced in the first place. Quality control is product-oriented and detective: it checks the actual build through testing and inspection to find defects. For example, introducing a requirement review checklist is QA, while executing test cases on a release build is QC. Software testing is one activity inside quality control.
34

What are the levels of testing?

Save to ▾
Show answer
Unit, integration, system and acceptance testing, moving from individual components to the complete product in front of users.
35

A dashboard shows pass or fail status only with red and green dots. What is the issue?

Save to ▾
Show answer
This relies on colour alone to give information, which fails WCAG criterion 1.4.1. Users with red-green colour blindness, which affects a noticeable share of men, cannot tell the states apart, and screen readers announce nothing. Recommend adding text or icons such as a tick and a cross with labels like 'Passed' and 'Failed', and accessible names for the dots. Test with a colour blindness simulator in browser developer tools.
36

What is the testing pyramid?

Save to ▾
Show answer
A model with many fast unit tests at the base, fewer API or integration tests in the middle and a small number of UI tests at the top.
37

What is visual regression testing in automation?

Save to ▾
Show answer
Visual regression testing takes screenshots of pages or components and compares them with approved baseline images to detect unexpected layout, font, colour or spacing changes that functional assertions miss. When a difference crosses a threshold, a person reviews it and either accepts the new baseline or logs a bug. Dynamic content like dates and ads must be masked, and the same browser and screen size must be used to avoid noise.
38

What is test monitoring and control?

Save to ▾
Show answer
Test monitoring compares actual testing progress with the plan, using metrics like test cases executed, pass rate, open defects and effort spent. Test control is the action taken when monitoring shows a gap, such as re-prioritising tests, adding testers, changing the schedule or tightening entry criteria. For example, if half the time has passed but only a quarter of cases are executed, the lead must act and inform stakeholders.
39

What is the difference between HTTP 401 and 403?

Save to ▾
Show answer
401 Unauthorized means the request has no valid authentication, such as a missing, expired or wrong token, so the client should log in again. 403 Forbidden means the user is authenticated but does not have permission for that resource, such as a normal user calling an admin API. Testers verify both: call without a token to expect 401, and call with a low-privilege token to expect 403.
40

How would you test a pen?

Save to ▾
Show answer
First ask what type of pen and who the users are. Functional: it writes smoothly, ink flows without leaking, the cap or click mechanism works and the ink colour matches the label. Non-functional: comfort of grip, writing length before ink runs out, performance at different temperatures and on different paper. Negative: dropping it, pressing hard, leaving it uncapped. Safety: the cap is non-toxic and has an air hole. This shows structured thinking, not just a list.

IT services companies (33)

IT services

TCS

Software Testing interview questions

  • 40 questions
  • 4 rounds

Mumbai, Chennai, Pune +2

View questions
IT services

Infosys

Software Testing interview questions

  • 40 questions
  • 4 rounds

Bengaluru, Mysuru, Pune +2

View questions
IT services

Wipro

Software Testing interview questions

  • 40 questions
  • 4 rounds

Bengaluru, Hyderabad, Pune +2

View questions
IT services

Cognizant

Software Testing interview questions

  • 40 questions
  • 4 rounds

Chennai, Bengaluru, Pune +2

View questions
IT services

Capgemini

Software Testing interview questions

  • 40 questions
  • 4 rounds

Mumbai, Bengaluru, Pune +2

View questions
IT services

HCLTech

Software Testing interview questions

  • 40 questions
  • 4 rounds

Noida, Chennai, Bengaluru +2

View questions
IT services

Tech Mahindra

Software Testing interview questions

  • 40 questions
  • 4 rounds

Pune, Hyderabad, Bengaluru +2

View questions
IT services

IBM

Software Testing interview questions

  • 40 questions
  • 4 rounds

Bengaluru, Pune, Hyderabad +2

View questions
IT services

Mphasis

Software Testing interview questions

  • 40 questions
  • 4 rounds

Bengaluru, Pune, Chennai

View questions
IT services

LTIMindtree

Software Testing interview questions

  • 40 questions
  • 4 rounds

Mumbai, Pune, Bengaluru +2

View questions
IT services

Persistent Systems

Software Testing interview questions

  • 40 questions
  • 4 rounds

Pune, Nagpur, Bengaluru +2

View questions
IT services

Hexaware

Software Testing interview questions

  • 40 questions
  • 4 rounds

Navi Mumbai, Chennai, Pune +2

View questions
IT services

Coforge

Software Testing interview questions

  • 40 questions
  • 4 rounds

Noida, Greater Noida, Bengaluru +2

View questions
IT services

Zensar Technologies

Software Testing interview questions

  • 40 questions
  • 4 rounds

Pune, Hyderabad, Bengaluru

View questions
IT services

Birlasoft

Software Testing interview questions

  • 40 questions
  • 4 rounds

Pune, Noida, Bengaluru +1

View questions
IT services

Nagarro

Software Testing interview questions

  • 40 questions
  • 4 rounds

Gurugram, Jaipur

View questions
IT services

EPAM Systems

Software Testing interview questions

  • 40 questions
  • 4 rounds

Hyderabad, Bengaluru, Pune +2

View questions
IT services

GlobalLogic

Software Testing interview questions

  • 40 questions
  • 4 rounds

Noida, Bengaluru, Gurugram +2

View questions
IT services

Virtusa

Software Testing interview questions

  • 40 questions
  • 4 rounds

Hyderabad, Chennai, Bengaluru

View questions
IT services

UST

Software Testing interview questions

  • 40 questions
  • 4 rounds

Thiruvananthapuram, Kochi, Bengaluru +2

View questions
IT services

CGI

Software Testing interview questions

  • 40 questions
  • 4 rounds

Bengaluru, Hyderabad, Chennai +1

View questions
IT services

NTT DATA

Software Testing interview questions

  • 40 questions
  • 4 rounds

Bengaluru, Pune, Noida +2

View questions
IT services

Genpact

Software Testing interview questions

  • 40 questions
  • 4 rounds

Gurugram, Hyderabad, Bengaluru +2

View questions
IT services

L&T Technology Services

Software Testing interview questions

  • 40 questions
  • 4 rounds

Vadodara, Bengaluru, Chennai +2

View questions
IT services

Cyient

Software Testing interview questions

  • 40 questions
  • 4 rounds

Hyderabad, Bengaluru, Noida

View questions
IT services

Sonata Software

Software Testing interview questions

  • 40 questions
  • 4 rounds

Bengaluru, Hyderabad

View questions
IT services

Mastek

Software Testing interview questions

  • 40 questions
  • 4 rounds

Mumbai, Pune

View questions
IT services

Happiest Minds Technologies

Software Testing interview questions

  • 40 questions
  • 4 rounds

Bengaluru, Noida

View questions
IT services

KPIT Technologies

Software Testing interview questions

  • 40 questions
  • 4 rounds

Pune, Bengaluru

View questions
IT services

Tata Elxsi

Software Testing interview questions

  • 40 questions
  • 4 rounds

Bengaluru, Thiruvananthapuram, Chennai +1

View questions
IT services

Quest Global

Software Testing interview questions

  • 40 questions
  • 4 rounds

Bengaluru, Thiruvananthapuram, Belagavi +1

View questions
IT services

Infogain

Software Testing interview questions

  • 40 questions
  • 4 rounds

Noida, Gurugram, Pune +1

View questions
IT services

YASH Technologies

Software Testing interview questions

  • 40 questions
  • 4 rounds

Indore, Pune, Hyderabad

View questions

Frequently asked questions

How are Software Testing interviews at it services companies different?

IT services companies hire in large numbers, often in campus or bulk drives. Interviews usually start with an online aptitude and coding test, then one or two technical rounds on fundamentals and your projects, then HR. Clear basics and good communication matter more than rare, advanced topics.

Which it services companies are covered?

This page links to 33 it services companies, including TCS, Infosys, Wipro, Cognizant, Capgemini, HCLTech, Tech Mahindra, IBM. Each has its own page with rounds and a separate practice set.

What rounds should I expect?

Common rounds at these companies include: Technical interview; HR round; Managerial round; Coding test; Online assessment (aptitude + reasoning). The exact process varies by company and role.