Tech Mahindra Software Testing Interview Questions & Answers

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.

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

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

Scope (in and out), objectives, approach, environments, schedule, roles, entry/exit criteria, risks and mitigation, deliverables and tools.

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

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

A final document summarising what was tested, defects found and open, metrics, lessons learned and the recommendation for release.

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

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.

List conditions and actions in a table and cover every combination of conditions (rules) — ideal for business rules like loan approval: salary > X AND credit score > Y → approve.

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.

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

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

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

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

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.

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

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

Learning, test design and execution at the same time, without scripted cases — time-boxed sessions with a charter (e.g. 'explore checkout with coupons'), noting bugs and ideas. Great for finding edge cases.

Test on real devices and OS versions, interrupts such as calls, battery, network changes, gestures, permissions and app store guidelines.

Testing how a system moves between states based on events, for example an order going from placed to paid to shipped to delivered.

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

Evaluating software to find defects and confirm it meets requirements. It reduces risk, protects users and saves the cost of fixing bugs after release.

A set of steps with inputs and expected results. Components: ID, title, preconditions, steps, test data, expected result, actual result and status.

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

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

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.

Status code, response body and schema, headers, response time, error messages for invalid input, authentication (401/403) and that data is saved in the database.

TDD writes unit tests before code to drive design; BDD describes behaviour in business language scenarios that become automated acceptance tests.

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

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

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

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

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

State the problem, location and condition briefly, for example 'Checkout button disabled after applying a coupon on the cart page'.

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.

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

A document defining scope, approach, resources, schedule, entry and exit criteria, risks and deliverables of testing.

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

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

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

JIRA Query Language, used to search issues, for example project = ABC AND status = Open AND priority = High.

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

The number of defects per size of software, for example defects per thousand lines of code or per module, used to compare quality.

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

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

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.

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.