PhonePe Software Testing Interview Questions & Answers

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.

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.

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

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

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

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

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 suite is a collection of related test cases; a run is one execution of a set of tests against a build.

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

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 final document summarising what was tested, defects found and open, metrics, lessons learned and the recommendation for release.

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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 language to query databases. Testers use it to verify data saved by the application, prepare test data and check backend results.

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

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

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

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

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

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

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

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.

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.

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

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.

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

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

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 observation that a small number of modules contain most defects, so testing should focus on those areas.

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

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

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 shared checklist for when a story is complete, usually including code review, tests passing, no open critical bugs and documentation updated.

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

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

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

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

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

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

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

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.