Wipro Software Testing Interview Questions & Answers

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.

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

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

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.

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

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.

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

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 regular review where QA, development and product assess new bugs and decide severity, priority, owner and target release.

Shift left with early reviews, improve test design, automate regression, use better test data, add monitoring and learn from escaped 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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.

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

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

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

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

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.

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.

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

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

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

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

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

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

Log and track bugs, link them to stories, build dashboards and filters with JQL, manage sprints and generate 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.

A team meeting at the end of a sprint to discuss what went well, what did not and what to improve next.

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

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

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.

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

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

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

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

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

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

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

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

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

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

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