Software Testing Interview Questions for Managers (₹30–40 LPA)

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.

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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 software to find defects and confirm it meets requirements. It reduces risk, protects users and saves the cost of fixing bugs after release.

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

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

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

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

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.

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

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

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.

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 extent of requirements or code exercised by tests. Measure requirement coverage with a traceability matrix and code coverage with tools.

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

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

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

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.

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

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

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

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

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.

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

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

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

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.

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

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

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

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.

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

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

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

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

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

Valid login, invalid login, forgot password, locked account and session handling are the main scenarios to cover.

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.

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