Walmart Software Testing Interview Questions & Answers

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

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

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.

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

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.

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

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.

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.

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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.

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

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

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.

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

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

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

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

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.

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.

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

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

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

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

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

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

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

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.

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

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.

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.

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

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