Software Testing Interview Questions for Mid-Level Roles (₹8–10 LPA)

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.

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

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

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

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.

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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.

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

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

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

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.

Checking the application works across browsers, devices, operating systems, screen sizes and network conditions.

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

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

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

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

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.

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

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

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.

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

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.

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

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

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

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

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

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.

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

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

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

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

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.

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

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

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.

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

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

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