Software Testing Interview Questions for Senior Specialists (₹15–20 LPA)

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

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

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

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

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

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

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

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.

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

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.

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

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.

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

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.

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

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.

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.

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

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

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

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

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

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

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.

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

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

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

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.

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

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.

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

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

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.

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 technique that tests all pairs of input values instead of every combination, greatly reducing test cases while catching most 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.

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.

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

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

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

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

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

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

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.

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

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

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

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

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.

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

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