Software Testing Interview Questions for Top Product Companies (₹50+ LPA)

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

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

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.

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

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

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

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

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.

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

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

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.

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

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

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

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

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.

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.

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

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.

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

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.

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

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

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.

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

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

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

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

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

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

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

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 development model where each development phase has a matching testing phase, such as requirements with acceptance tests and design with integration tests.

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

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

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

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.

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

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

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

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.

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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.

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

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

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

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.

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

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

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

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

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