Flipkart Software Testing Interview Questions & Answers

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

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.

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

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

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

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.

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

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

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

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

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

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

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

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

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

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.

Talk to developers and users, explore the product, review similar systems, create notes and mind maps, confirm assumptions and write test cases as you learn.

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

Alpha is done in-house by internal teams before release; beta is done by a limited group of real users in their own environment.

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

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

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

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.

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

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

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

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

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.

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

Smoke tests run on every build for quick feedback; full regression runs less often, such as nightly or before 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.

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

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

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

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

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

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

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

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

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

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.

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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.

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

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.

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

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

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

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

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.

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.

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

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

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

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

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

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

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

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

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

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

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.