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

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

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

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

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

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

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

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

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.

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

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

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

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 access with valid, expired and missing tokens, role-based permissions, error codes and that sensitive data is never exposed.

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 on real devices and OS versions, interrupts such as calls, battery, network changes, gestures, permissions and app store guidelines.

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

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.

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

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

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

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

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

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

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.

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

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

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

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

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

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

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.

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.

A suite is a collection of related test cases; a run is one execution of a set of tests against a build.

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