Skip to content

Capgemini Software Testing Interview Questions & Answers

Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.

About Capgemini hiring for Software Testing roles

Capgemini is a French multinational IT services and consulting group providing technology, engineering, cloud and data services. India is its largest employee base, supporting projects in testing, application development, SAP, data engineering and analytics for global clients. It hires freshers as analysts and software engineers, and experienced professionals in QA automation, data and cloud roles.

For Software Testing roles, this Capgemini practice set focuses most on Manual Testing Basics (10), STLC and Test Planning (5), Database Testing (4), Automation Basics for Manual Testers (4). It has 15 easy, 24 medium, 1 hard questions, so you can start easy and work up to the harder ones.

Company type
IT services
Headquarters
Paris, France
Main India offices
Mumbai, Bengaluru, Pune, Chennai, Hyderabad

Capgemini Software Testing interview process

  1. Online assessment (pseudocode + English)
  2. Game-based aptitude test
  3. Technical interview
  4. HR round

Typical pattern based on public candidate experiences. Rounds vary by role, team and year.

Solved for CapgeminiStart 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
Save to ▾
Show answer
JIRA Query Language, used to search issues, for example project = ABC AND status = Open AND priority = High.
02

What is a test closure report?

Save to ▾
Show answer
A final document summarising what was tested, defects found and open, metrics, lessons learned and the recommendation for release.
03

SQL: verify that row counts and totals match between a source table and a target table after a data load.

Save to ▾
Show answer
-- Compare counts and sums side by side; both columns must match SELECT (SELECT COUNT(*) FROM staging_orders) AS src_count, (SELECT COUNT(*) FROM dw_orders) AS tgt_count, (SELECT SUM(amount) FROM staging_orders) AS src_amount, (SELECT SUM(amount) FROM dw_orders) AS tgt_amount;
04

What is the V-model?

Save to ▾
Show answer
A development model where each development phase has a matching testing phase, such as requirements with acceptance tests and design with integration tests.
05

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.
06

What is the OWASP Top 10 and why should testers know it?

Save to ▾
Show answer
The OWASP Top 10 is a widely used list of the most critical web application security risks, published by an open community project. It includes broken access control, cryptographic failures, injection, insecure design, security misconfiguration, vulnerable components and authentication failures. Testers use it as a checklist to include basic security checks in their testing and to speak the same language as security teams.
07

What are ACID properties and how can a tester check them?

Save to ▾
Show answer
ACID means Atomicity, Consistency, Isolation and Durability. Atomicity: a transfer that debits one account must also credit the other, or neither happens; test by forcing a failure midway. Consistency: constraints still hold after the transaction. Isolation: two users updating together do not see each other's half-done work; test with two sessions. Durability: committed data survives a restart; test by committing, restarting the service and querying again.
08

Tell me about a time you found an important bug that others missed.

Save to ▾
Show answer
Model answer: Situation: before a release of an insurance app, all regression tests had passed. Task: I was doing a final exploratory round. Action: I renewed a policy on the last day of the month and saw that the premium was calculated for 31 days in a 30-day month. I logged it with exact data and the formula difference. Result: the date logic was fixed before release, and I added month-end cases to the suite.
09

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.
10

Smoke vs sanity testing?

Save to ▾
Show answer
Smoke testing checks that the critical features of a new build work (broad and shallow). Sanity testing checks that a specific fix or area works after a change (narrow and deep).
11

Tell me about a time you pushed for an accessibility fix the team wanted to postpone.

Save to ▾
Show answer
Situation: before a release, I found the payment form errors were not announced by screen readers and not reachable by keyboard. Task: the team wanted to defer it. Action: I recorded a short NVDA video showing a user could not finish payment, linked it to WCAG and our customer commitments, and proposed a small fix. Result: the fix took half a day, shipped in the release and we added keyboard checks to our definition of done.
12

A page loads slowly only for some users. How do you investigate as a manual tester?

Save to ▾
Show answer
Collect details from affected users: location, device, browser, network and time. Try to reproduce with similar conditions using browser network throttling. Use the browser developer tools network tab to find slow requests, large files or failing calls, and compare with a fast user. Check whether those users have more data, like a long order history. Share the slow request, timing and conditions in the bug for the developers.
13

What are suspension and resumption criteria in a test plan?

Save to ▾
Show answer
Suspension criteria define when testing should be paused because continuing would waste effort, for example when a blocker bug stops the main flow, the build fails smoke testing or the environment is down. Resumption criteria define what must happen to restart, such as a new build that passes smoke testing or the environment restored. Writing these down avoids arguments and shows clearly why testing time was lost.
14

Why are hard-coded sleeps bad in automated tests?

Save to ▾
Show answer
A fixed sleep, such as waiting five seconds, is either too long, which makes the suite slow when the page loads in one second, or too short, which makes the test fail when the server is slow. Both waste time and cause flaky results. Instead, wait for a real condition: an element to appear, a network response to finish or a loading spinner to disappear. Modern tools do much of this automatically.
15

What is SDLC and STLC?

Save to ▾
Show answer
SDLC is the full software development life cycle; STLC is the testing life cycle: requirement analysis, test planning, test design, environment setup, execution and closure.
16

What is a test basis?

Save to ▾
Show answer
The test basis is the set of documents and knowledge from which test cases are derived. It includes requirement specifications, user stories with acceptance criteria, design documents, wireframes, API contracts, business rules and even existing system behaviour. A good test basis lets you trace each test case back to a requirement. If the test basis is weak or missing, testers must clarify it before or while testing.
17

You join a project in the middle of a release. How do you plan your testing?

Save to ▾
Show answer
Spend the first day learning the scope: read the release notes, user stories and test plan, and ask the lead what is at risk. Get access to the environment, tracker and test repository. Pick up a clearly defined module, run its existing test cases to learn the application and note gaps. Ask questions early in stand-up. Within a few days, take ownership of retesting and regression for that module.
18

What are test data and how do you prepare them?

Save to ▾
Show answer
The inputs used in tests. Prepare using valid, invalid and boundary values from production-like but masked data, spreadsheets or generators.
19

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.
20

What is end-to-end testing?

Save to ▾
Show answer
End-to-end testing checks a complete business flow from the user's first action to the final result, across all connected parts: UI, APIs, database, third-party services and notifications. For example, in online shopping: search a product, add to cart, pay, receive the confirmation email and see the order in the account. It finds integration issues that module-level testing misses, but it is slower and needs stable environments.
21

A developer marks your bug as fixed, but it still fails. What do you do?

Save to ▾
Show answer
First confirm you are testing the right build, which contains the fix, and clear the cache. Repeat the exact steps and data from the bug. If it still fails, reopen the bug with a comment stating the build number, what you did and the actual result, with a fresh screenshot or video. Talk to the developer directly if the steps differ from what they tested, so the fix is not tested on a different scenario.
22

What is the difference between UI automation and API automation, and which gives faster feedback?

Save to ▾
Show answer
UI automation drives the browser or app like a user, so it checks the full experience but is slower and breaks more often with design changes. API automation sends requests directly to services and checks responses, which is much faster, more stable and can run before the UI exists. API tests give faster feedback, so teams place most business rule checks at the API level and keep a smaller set of UI journeys.
23

SQL: find rows where mandatory columns are NULL or empty in a customers table.

Save to ▾
Show answer
-- Mandatory fields: name, email, phone SELECT id, name, email, phone FROM customers WHERE name IS NULL OR TRIM(name) = '' OR email IS NULL OR TRIM(email) = '' OR phone IS NULL OR TRIM(phone) = ''; -- Expected result: no rows
24

SQL: find duplicate emails.

Save to ▾
Show answer
SELECT email, COUNT(*) FROM users GROUP BY email HAVING COUNT(*) > 1;
25

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.
26

What is data integrity and what are its main types?

Save to ▾
Show answer
Data integrity means data stays accurate and consistent through its life. Entity integrity: every row has a unique, non-null primary key. Referential integrity: a foreign key always points to an existing parent row, such as every order pointing to a real customer. Domain integrity: values stay within allowed types and ranges, enforced by data types, CHECK and NOT NULL constraints. User-defined integrity covers business rules, such as an order total never being negative.
27

What is JMeter and what does a basic test plan in it contain?

Save to ▾
Show answer
Apache JMeter is an open-source load testing tool, mainly for HTTP APIs and web pages. A basic test plan has a Thread Group that sets the number of virtual users, ramp-up time and loop count; samplers such as HTTP Requests; config elements like headers and CSV data; timers for think time; assertions on responses; and listeners or reports showing response times, throughput and errors. Run real load in non-GUI mode.
28

Why do you want to start your career in manual testing?

Save to ▾
Show answer
Model answer: I enjoy finding how things break and thinking like a user. During my internship I tested a college fee portal and found that a refund was shown twice on the receipt, which the team fixed before launch. Manual testing gives me a strong base in requirements, test design and bug reporting. I plan to add SQL, API and automation skills on top of it as I grow.
29

How do you test database integrity using SQL?

Save to ▾
Show answer
Verify inserted, updated and deleted rows match UI actions, check constraints, duplicates, NULLs and totals with COUNT and SUM queries.
30

What are the seven principles of testing?

Save to ▾
Show answer
Testing shows presence of defects, exhaustive testing is impossible, test early, defects cluster, the pesticide paradox, testing is context-dependent and absence-of-errors is a fallacy.
31

What is the difference between accessibility testing and usability testing?

Save to ▾
Show answer
Accessibility testing checks that people with disabilities can use the product, often against WCAG criteria, using keyboards, screen readers, zoom and contrast tools. Usability testing checks how easily typical users complete tasks, by watching real users and measuring success, time and errors. They overlap, since clear labels help everyone, but a page can pass WCAG and still be confusing, or be easy for most users yet unusable with a screen reader.
32

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.
33

How do you break a requirement into testable conditions?

Save to ▾
Show answer
Read the requirement and identify inputs, outputs, business rules, user roles and states. Turn each rule into a condition with an expected result, then add negative and boundary conditions. For example, 'users can withdraw up to 10,000 per day' becomes: withdraw below the limit, exactly at the limit, above the limit, multiple withdrawals adding up to the limit, and the limit resetting the next day. Each condition then becomes one or more test cases.
34

What is the pesticide paradox and how do you counter it?

Save to ▾
Show answer
The pesticide paradox says that if you run the same tests again and again, they stop finding new defects, just as pests become resistant to the same pesticide. To counter it, regularly review and update test cases, add new scenarios from recent production bugs, vary test data, and mix scripted runs with exploratory sessions. Rotating testers across modules also brings fresh eyes and new ideas.
35

What is the difference between ad hoc testing and monkey testing?

Save to ▾
Show answer
Ad hoc testing is informal testing without test cases, done by a tester who understands the application and tries likely weak areas based on experience. Monkey testing gives random inputs and actions, often without knowing the application, to see if it crashes. Ad hoc testing is targeted and good at finding logical bugs, while monkey testing is good at finding stability issues and is often automated.
36

What is a test condition?

Save to ▾
Show answer
A test condition is an item or event of the system that can be verified by one or more test cases, derived from the test basis. For example, for a login requirement, conditions include valid login, wrong password, locked account and remember me. Test conditions answer what to test, while test cases describe how to test it with steps, data and expected results. Listing conditions first helps check coverage before writing detailed cases.
37

What do testers look for during a requirement review?

Save to ▾
Show answer
Check that each requirement is clear, complete, consistent and testable. Look for vague words like fast or user-friendly, missing error handling, undefined limits, conflicting rules and missing roles or states. For each requirement ask how you would test it and what the expected result is. Record questions in a review log and get answers from the business analyst before writing test cases, so ambiguity does not turn into defects later.
38
Save to ▾
Show answer
A keyboard trap is when focus moves into a component and the user cannot move out using the keyboard, for example an embedded video player or date picker that captures Tab forever. Mouse users never notice, but keyboard and screen reader users are stuck and must reload the page. It fails WCAG criterion 2.1.2. Test every widget by tabbing in and out, and check that Escape closes popups and returns focus.
39

Describe a time an automated test caught a regression that manual testing would have missed.

Save to ▾
Show answer
Situation: a small tax rounding change was made late on a Friday. Task: no manual regression was planned for pricing. Action: our nightly API suite failed one data-driven case where a 3-item cart was off by one rupee; I checked the trace, reproduced it manually and logged it with the failing input. Result: it was fixed before release, and the team agreed to keep pricing tests in the pull request suite.
40

What is the difference between an emulator, a simulator and a real device?

Save to ▾
Show answer
An emulator imitates both the hardware and software of a device, as with the Android emulator, so it behaves close to a real phone. A simulator imitates only the software environment, as with the iOS simulator, and does not reproduce the hardware. Both are free and fast for early testing. Real devices are needed for camera, battery, sensors, actual performance, network behaviour and final sign-off.

Tips to crack the Capgemini Software Testing interview

  • Practise game-based cognitive tests and pseudocode questions, which are commonly part of Capgemini's online assessment.
  • Prepare a short explanation of your projects, focusing on your role, tools used and what you would improve.
  • Learn about Capgemini's engineering arm and its work in sectors like automotive and financial services to show interest.
  • 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; Capgemini interviewers usually ask follow-ups on your first answer.

Frequently asked questions

How many rounds are there in the Capgemini Software Testing interview?

Candidates usually go through 4 stages: Online assessment (pseudocode + English); Game-based aptitude test; Technical interview; 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 Capgemini Software Testing interview?

This practice set leans on Manual Testing Basics (10), STLC and Test Planning (5), Database Testing (4), Automation Basics for Manual Testers (4). Revise those first, then practise explaining one or two of your own projects end to end, because most Capgemini interviewers ask you to walk through real work.

Are these the exact questions asked at Capgemini?

No. These are curated practice questions that match the skills and difficulty usually tested in it services interviews like Capgemini's. They are not a leaked or verified list of past questions.

Where does Capgemini hire Software Testing professionals in India?

Capgemini has large teams in Mumbai, Bengaluru, Pune, Chennai, Hyderabad. Openings and locations change often, so check the Capgemini careers page and filter by city and experience.

Software Testing questions for similar companies