Zepto Software Testing Interview Questions & Answers

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.

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

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

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.

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.

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.

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

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

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.

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

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

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

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

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

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

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

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.

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

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

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 set of steps with inputs and expected results. Components: ID, title, preconditions, steps, test data, expected result, actual result and status.

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

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

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.

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

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.

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

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

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

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

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.

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

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

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

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

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

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.

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

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.

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

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

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

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

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

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

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.

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

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

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

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

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

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.

A technique that tests all pairs of input values instead of every combination, greatly reducing test cases while catching most defects.

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

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.

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

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.

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

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.

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.

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

Testing at the edges of input ranges, such as 17, 18 and 19 for an age limit of 18, since errors cluster at boundaries.

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

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

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

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

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