Visa Software Testing Interview Questions & Answers

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

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

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.

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

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.

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

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

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

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

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.

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.

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

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

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

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 extent of requirements or code exercised by tests. Measure requirement coverage with a traceability matrix and code coverage with tools.

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

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

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

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

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

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

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

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

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.

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

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

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.

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

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.

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.

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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.

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

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

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

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.