Zomato Software Testing Interview Questions & Answers

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

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

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

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

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

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.

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

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

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

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

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

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

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

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.

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

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

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

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

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.

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

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

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

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

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

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

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

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

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.

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

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.

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

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

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

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

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

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

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

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

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

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 human error causes a defect in the code, and when that defect is executed it produces a failure visible to users.

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

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

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.

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

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

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.

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

Valid login, wrong password, empty fields, case sensitivity, max length, SQL-injection strings, password masking, 'remember me', lock-out after N attempts and the forgot-password link.

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

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.

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.

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

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

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

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.

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

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.

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

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

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

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.

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

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

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

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

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.