Capgemini Software Testing Interview Questions & Answers

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

Static testing reviews documents and code without executing; dynamic testing executes the software to observe behaviour.

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

GET retrieves data and has parameters in the URL; POST sends data in the body to create or process something.

Check access with valid, expired and missing tokens, role-based permissions, error codes and that sensitive data is never exposed.

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.

A clear title, steps to reproduce, expected vs actual result, environment/build, severity and priority, and evidence (screenshot, video, logs).

200 OK, 201 Created, 204 No Content, 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 500 Internal Server Error.

Valid keyword, partial match, no results, special characters, very long text, empty search, case sensitivity, spelling errors, suggestions and speed of results.

Code is built and tested automatically on each change; tests are quality gates that stop faulty builds from moving forward.

A human error causes a defect in the code, and when that defect is executed it produces a failure visible to users.

An urgent patch released outside the normal schedule to fix a critical production defect, followed by regression testing and merge back to the main branch.

Success, failure and pending flows, timeouts, refunds, double-click payments, every method (UPI, cards, net banking), rounding, security (no card data stored) and reconciliation with bank reports.

Moves to the chosen floor, doors open and close, door sensor stops closing on obstruction, overload alarm, emergency button, behaviour in a power cut, max capacity and the floor display.

Shift left with early reviews, improve test design, automate regression, use better test data, add monitoring and learn from escaped defects.

A scenario is a high-level thing to test (user logs in); test cases are the detailed steps and data that verify it.

Entry criteria are conditions that must be met to start testing (build ready, environment set); exit criteria define when testing can stop (pass rate, no critical defects).

DELETE removes selected rows and can be rolled back; TRUNCATE quickly removes all rows and resets the table.

Break the work into modules and test cases, use past velocity or three-point estimation (optimistic, likely, pessimistic), add time for test data, environment issues, retesting and regression, and keep a risk buffer.

Add, remove, update quantity, price and tax calculation, coupon codes, stock limits, cart persistence after login and checkout navigation.

Log and track bugs, link them to stories, build dashboards and filters with JQL, manage sprints and generate reports.

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

An epic is a large body of work; stories are user-facing slices of it; tasks are technical work items; bugs are defects.

Prioritising tests by the likelihood and impact of failure, so critical areas get the most coverage when time is limited.

Assess impact and risk, discuss with product and dev, decide to fix, defer with a workaround or delay release, and document the decision.

INNER returns matching rows, LEFT keeps all left rows, RIGHT keeps all right rows and FULL keeps all rows from both tables.

Test 17, 18, 19, 59, 60 and 61.

Alpha is done in-house by internal teams before release; beta is done by a limited group of real users in their own environment.

A regular review where QA, development and product assess new bugs and decide severity, priority, owner and target release.

Verification: are we building the product right? (reviews, walkthroughs — no code run). Validation: are we building the right product? (actual testing against user needs).

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.

Clear, concise, independent, repeatable, traceable to a requirement, with precise expected results and tested data.

The extent of requirements or code exercised by tests. Measure requirement coverage with a traceability matrix and code coverage with tools.

Checking that people with disabilities can use the product, using screen readers, keyboard navigation, colour contrast and WCAG guidelines.

Send page, size, sort and filter parameters, then verify counts, order, boundaries (first, last, empty page) and invalid parameter handling.

Measuring speed and stability: load (expected users), stress (beyond limits), spike (sudden surge), endurance (long duration) and scalability testing.

Create a request with method, URL, headers and body, send it, check status and body, add test scripts and save it in a collection.

Re-check the requirement, reproduce with clear steps and evidence (screenshots, logs), discuss with the BA/PO and record the final decision.

User Acceptance Testing — end users or the client verify that the system meets business needs in a production-like environment before go-live.

A shared checklist for when a story is complete, usually including code review, tests passing, no open critical bugs and documentation updated.

Valid login, invalid login, forgot password, locked account and session handling are the main scenarios to cover.

Functional testing checks what the system does (login, checkout). Non-functional testing checks how well it does it (performance, security, usability, compatibility).

Severity = impact on the system. Priority = urgency to fix. Logo misspelt on the homepage → low severity, high priority. Crash in a rarely used report → high severity, low priority.

The observation that a small number of modules contain most defects, so testing should focus on those areas.

Statuses like To Do, In Progress, In Review, Ready for QA, Done and Reopened, with transitions that depend on the team's configuration.

They let testers verify totals and counts per category, such as the number of orders per customer, and compare them with the UI or reports.

Testing services directly without the UI, checking status codes, responses, security and performance. It finds issues early and is faster than UI tests.

Severity is impact on the system; priority is urgency of the fix. A crash in a rare report is high severity, low priority; a spelling mistake in the logo is low severity, high priority.

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

Positive cases use valid inputs to confirm expected behaviour; negative cases use invalid inputs to confirm the system handles errors gracefully.

Re-check environment, data, browser and steps; check the logs; try the reporter's setup; add video and console logs; mark it 'cannot reproduce' only after discussing with the developer, and keep monitoring.

Smoke tests run on every build for quick feedback; full regression runs less often, such as nightly or before release.

For a field accepting 1–100: valid class 1–100 (test 50), invalid below 1 (test −5), invalid above 100 (test 150). One value represents each class.

Check SQL injection, brute-force lockout, password masking, session timeout, HTTPS, cookie flags, error messages not revealing users and password reset flow.

Mandatory fields, email format, password rules, duplicate email, terms checkbox, captcha, confirmation email and field length limits.

A suite is a collection of related test cases; a run is one execution of a set of tests against a build.

A grid mapping requirements to test cases and defects, proving every requirement is tested.