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

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.

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

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

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

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

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

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.

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

Create a request with method, URL, headers and body, send it, check status and body, add test scripts and save it in a collection.

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

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

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

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.

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.

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

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

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.

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

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

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

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

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.

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

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

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

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

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

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

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.

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

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

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

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

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

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

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.

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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.

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

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

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

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 team meeting at the end of a sprint to discuss what went well, what did not and what to improve next.

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

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.

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.

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

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.