Swiggy Software Testing Interview Questions & Answers

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

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

By business criticality, usage frequency, defect history, risk and dependencies, running high-priority cases first.

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

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

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.

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

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

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

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

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.

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

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

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

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

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

The hardware, software, data and configuration where testing happens, set up to mirror production as closely as practical.

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

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

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

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

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

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

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

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

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.

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

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.

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

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 login, invalid login, forgot password, locked account and session handling are the main scenarios to cover.

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

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

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.

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

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.

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

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

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

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

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.

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

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

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

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

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

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.

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.

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.

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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