PayPal Software Testing Interview Questions & Answers

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

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

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

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

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

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

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.

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

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

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.

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

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

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

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

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.

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

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

A set of steps with inputs and expected results. Components: ID, title, preconditions, steps, test data, expected result, actual result and status.

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

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

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

Status code, response body and schema, headers, response time, error messages for invalid input, authentication (401/403) and that data is saved in the database.

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.

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.

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

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

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.

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.

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

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

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.

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.

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

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

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

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

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.

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

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 execution rate, pass percentage, defect density, defect leakage, defect rejection ratio, requirement coverage and automation coverage.

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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