Razorpay Software Testing Interview Questions & Answers

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

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

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

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

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.

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.

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

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

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

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

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

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 keyword, partial match, no results, special characters, very long text, empty search, case sensitivity, spelling errors, suggestions and speed of results.

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.

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

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

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.

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

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

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

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-check the requirement, reproduce with clear steps and evidence (screenshots, logs), discuss with the BA/PO and record the final decision.

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

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

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

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

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

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.

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

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 development model where each development phase has a matching testing phase, such as requirements with acceptance tests and design with integration tests.

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.

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

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

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

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

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

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 clear title, steps to reproduce, expected vs actual result, environment/build, severity and priority, and evidence (screenshot, video, logs).

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

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

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

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

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.

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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