Uber Software Testing Interview Questions & Answers

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.

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

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

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

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

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

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.

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

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

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

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

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

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.

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.

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

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

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.

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

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

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

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

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

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

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 that is continuous and collaborative within each sprint, with testers working alongside developers and product owners from the start.

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

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

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.

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

The extent of requirements or code exercised by tests. Measure requirement coverage with a traceability matrix and code coverage with tools.

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.

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

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

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

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

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

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

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

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

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

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

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.

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.

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

Sprint planning (estimate test effort), daily stand-up (status and blockers), sprint review (demo) and retrospective (improve). Testers clarify acceptance criteria early and test within the sprint.

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

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.

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

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.

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

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

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

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