Deloitte Software Testing Interview Questions & Answers

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

Evaluating how easy and pleasant a product is to use by observing real users complete tasks and noting confusion.

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

An API style using HTTP methods on resources identified by URLs, usually exchanging JSON and staying stateless.

A language to query databases. Testers use it to verify data saved by the application, prepare test data and check backend results.

A development model where each development phase has a matching testing phase, such as requirements with acceptance tests and design with integration tests.

Sprint planning (estimate test effort), daily stand-up (status and blockers), sprint review (demo) and retrospective (improve). Testers clarify acceptance criteria early and test within the sprint.

Using experience to guess where defects likely hide, such as empty fields, special characters or unexpected sequences, and designing tests for them.

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

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

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

Use mocks or stubs from the API contract such as Swagger, write test cases early and validate again when the real service is available.

Testing that is continuous and collaborative within each sprint, with testers working alongside developers and product owners from the start.

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

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

The team selects stories for the sprint. QA helps estimate testing effort, clarifies acceptance criteria and flags dependencies and risks.

Basic operations, division by zero, decimals, large numbers, order of operations, clear and backspace, repeated operations and memory keys.

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

Re-testing existing features after a change. Automate stable, repetitive, high-value flows that run every release.

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

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.

Test execution rate, pass percentage, defect density, defect leakage, defect rejection ratio, requirement coverage and automation coverage.

Allowed and disallowed formats, size limits, empty file, duplicate names, special-character names, cancel upload, slow network and multiple files.

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

A defect that stops testing or release of a feature because no workaround exists, so it is highest priority.

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

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 grid mapping requirements to test cases and defects, proving every requirement is tested.

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

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.

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

Verify inserted, updated and deleted rows match UI actions, check constraints, duplicates, NULLs and totals with COUNT and SUM queries.

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.

New → Assigned → Open → Fixed → Retest → Verified → Closed, with Reopened, Rejected, Deferred and Duplicate as side paths.

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

Designing tests from user flows described in use cases to verify complete real-world interactions.

Valid card and PIN, wrong PIN, three failed attempts, amount above balance, amount above daily limit, invalid denomination, machine out of cash, network failure and receipt printing.

Checking the application works across browsers, devices, operating systems, screen sizes and network conditions.

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

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

Finding why a defect was introduced, such as unclear requirements or missed reviews, to prevent similar defects in future.

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

Peer review for clarity, coverage of requirements, correct expected results, test data and traceability, then update and baseline them.

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.

Keep tests modular, prioritise by risk, use exploratory testing, automate stable parts and keep close contact with product owners.

A bug is behaviour that deviates from agreed requirements; an enhancement is a new or improved capability beyond the current requirements.

Reproduce and assess impact, inform stakeholders, help developers fix and verify in staging, run regression and check monitoring after the hotfix, then do a post-mortem.

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

Valid transfer, insufficient balance, daily limit, wrong beneficiary, OTP failure, network drop mid-transaction, duplicate click and statement update.

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

Verifying the application works across different hardware, software and settings combinations.

Risk-based testing: cover critical user flows, recent changes and high-defect areas first. Clearly communicate the untested risks and get stakeholder sign-off.

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

Black box tests behaviour without code knowledge; white box tests internal logic and paths; grey box uses partial knowledge of the internals.

Rules such as NOT NULL, UNIQUE, PRIMARY KEY, FOREIGN KEY and CHECK that keep data valid and consistent.

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

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

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

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

Evaluating software to find defects and confirm it meets requirements. It reduces risk, protects users and saves the cost of fixing bugs after 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.

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

Defects found after release that testing should have caught; leakage % = defects in production / total defects x 100.

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

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.