Manual Testing Interview Questions and Answers
Last updated 2026-11-19
Manual testing interviews check how you think about quality: how you derive test cases from a requirement, how you report a defect so a developer can fix it, and how you decide what to test when time is short. Strong candidates give concrete examples rather than definitions. This page has 16 worked questions with real test-case tables, boundary value calculations and a defect report template.
The answers are written for freshers and early-career testers. When you want to move into automation, continue with the automation testing questions and Selenium questions. For interview strategy see how to crack a QA testing interview.
| Core topics | SDLC and STLC, test design, defect management, test levels and types, exploratory testing |
|---|---|
| Techniques to know | Equivalence partitioning, boundary value analysis, decision tables, state transition |
| Tools commonly named | Jira, TestRail, Zephyr, Postman, browser developer tools |
A defect report that gets fixed
Interviewers often ask you to write a bug report on the spot. Use a precise title, environment, numbered steps, expected result, actual result, evidence and severity. The example below reports a real kind of defect so you can copy the structure.
Title: Order total ignores coupon SAVE10 when cart has exactly 1 item
Environment: Staging build 2.8.1, Chrome 130, Windows 11
Steps:
1. Add one item priced Rs 1,000 to the cart
2. Open the cart and apply coupon SAVE10
3. Observe the order summary
Expected: Discount of Rs 100 shown, total Rs 900
Actual: Message 'Coupon applied' but total remains Rs 1,000
Frequency: 3 of 3 attempts; works with 2 or more items
Severity: Major (money impact). Priority: High
Attachment: screen recording, network log showing discount=0 in /cart responseManual Testing Interview Questions and Answers: questions with worked answers
1 What is the difference between verification and validation?
easyVerification asks whether we are building the product right: it checks work products against specifications through reviews, walkthroughs, inspections and static analysis, without running the software. Validation asks whether we are building the right product: it checks that the software meets the user's actual needs by executing it, through functional and acceptance testing. A requirements review is verification; user acceptance testing is validation. A product can pass verification, matching a flawed specification perfectly, and still fail validation because the specification was wrong.
2 Explain the software testing life cycle and its entry and exit criteria.
easyThe STLC phases are requirement analysis (identify testable requirements), test planning (scope, strategy, effort, resources, risks), test case design, test environment setup, test execution, and test closure (reports, metrics, lessons). Each phase has entry criteria, the conditions that must be true to start, and exit criteria, the conditions that let it finish. For execution, entry criteria might be approved test cases, a stable build that passes a smoke test and a ready environment with test data; exit criteria might be all planned tests run, no open critical or high defects, and a required pass rate. Defining them upfront prevents arguments about when testing is done.
3 Describe the defect life cycle and who does what.
easyA tester logs a defect as New. A lead or triage meeting reviews it and marks it Assigned to a developer, or Rejected if invalid, Duplicate if already logged, or Deferred if it will be fixed later. The developer sets it to Open or In Progress and then Fixed. The tester retests on a new build: if the fix works, the defect is Verified and then Closed; if not, it is Reopened with details. Good practice includes a clear reproduction, linking to the requirement or test case, and giving priority based on business need and severity based on technical impact.
4 What is the difference between severity and priority? Give examples of all four combinations.
easySeverity is the impact of the defect on the system; priority is the urgency of fixing it from the business point of view. High severity with high priority: the payment page crashes at checkout. High severity with low priority: a crash in a rarely used admin export that only happens with a 2 GB file. Low severity with high priority: the company name is misspelled on the home page before a launch. Low severity with low priority: a minor alignment difference in a seldom visited help page. Testers usually propose severity; product owners or managers set priority.
5 Apply equivalence partitioning and boundary value analysis to an age field that accepts 18 to 60.
mediumEquivalence partitioning divides inputs into classes expected to behave the same, so one value represents each class: invalid below (for example 10), valid (30) and invalid above (70), plus non-numeric and empty input as separate invalid classes. Boundary value analysis tests the edges, where defects cluster: with two-value boundaries that is 17, 18, 60, 61; with three-value it adds 19 and 59. So the compact test set is 17, 18, 19, 59, 60, 61 plus one mid value such as 30, and the invalid types. Expected results are rejection for 17 and 61, and acceptance for 18, 19, 59 and 60.
textInput Partition Expected 17 invalid (low) rejected with message 18 boundary valid accepted 19 valid accepted 30 valid (typical) accepted 59 valid accepted 60 boundary valid accepted 61 invalid (high) rejected with message abc invalid type rejected (empty) missing rejected 18.5 decimal rejected or per spec6 Write test cases for a login page.
mediumCover positive, negative, boundary, usability and security cases, and write each with an ID, steps, test data, expected result and priority. Positive: valid username and password logs in and lands on the dashboard. Negative: wrong password, unknown user, blank fields, spaces only, case sensitivity of password. Boundary: minimum and maximum length of fields. Security: password masked, no credentials in the URL, lockout or delay after repeated failures, SQL injection text rejected, session expires after logout, HTTPS used. Usability: Enter key submits, tab order, Forgot password link works, error messages do not reveal whether the user exists. Compatibility: major browsers and mobile viewports.
textTC_01 Valid login user=asha@example.com / correct password -> dashboard shown TC_02 Wrong password valid user / wrong password -> generic error, stay on page TC_03 Empty fields both blank -> inline validation messages TC_04 Password masked type password -> characters hidden TC_05 Lockout 5 wrong attempts -> temporary lock or captcha TC_06 SQL injection text user=' OR '1'='1 / any -> rejected, no login TC_07 Session after logout logout then browser Back -> redirected to login7 What is the difference between smoke, sanity and regression testing?
easySmoke testing is a shallow, broad check on a new build to decide whether it is stable enough for further testing: can the app start, log in and open the main screens. Sanity testing is a narrow, deep check on a specific area after a small change or fix, confirming it works and nothing obvious nearby broke. Regression testing re-runs a wider set of existing tests to make sure recent changes did not break working features; it is the best candidate for automation. A build that fails smoke is returned to development without further testing.
8 What is the difference between functional and non-functional testing? Give types of each.
easyFunctional testing verifies what the system does against requirements: unit, integration, system and acceptance testing, plus API and database checks. Non-functional testing verifies how well it does it: performance (load, stress, spike, endurance), security, usability, compatibility, accessibility, reliability, recovery and localisation. A report can function correctly yet take two minutes to load, which is a non-functional failure. Non-functional requirements need measurable targets, such as the page responds in under 2 seconds for 500 concurrent users, otherwise they cannot be tested.
9 Explain black box, white box and grey box testing.
easyBlack box testing checks behaviour from the outside using inputs and expected outputs, without looking at code; techniques include equivalence partitioning, boundary analysis and decision tables. White box testing uses knowledge of internal structure to design tests for code coverage, such as statement, branch and path coverage, typically done by developers in unit tests. Grey box combines both: the tester knows some internals such as the database schema or API contract and uses them to design better black-box tests, for example verifying a database row after a UI action.
10 What is exploratory testing and when is it better than scripted testing?
mediumExploratory testing is simultaneous learning, test design and execution, guided by a charter such as explore the refund flow with expired cards for 45 minutes, with notes taken as you go. It finds unexpected defects, suits new or poorly documented features, and is valuable when time is short. Scripted testing is repeatable and good for regression and compliance. Use session-based test management to keep exploratory work accountable: time-boxed sessions, a charter, notes, bugs found and questions raised.
11 How do you decide what to test when there is not enough time?
mediumUse risk-based prioritisation: rank features by likelihood of failure and business impact, and test the high-risk areas first. Factors include new or heavily changed code, complexity, past defect density, money or data impact, and usage frequency. Run smoke tests, then the critical user journeys such as sign-up, search and payment, then regression around changed areas, then lower-risk items as time allows. Communicate clearly to stakeholders what was and was not covered and the residual risk, so the release decision is informed.
12 What goes into a test plan versus a test strategy?
easyA test strategy is a high-level, often organisation-wide document describing the approach: test levels, types, tools, defect process and standards; it changes rarely. A test plan is project-specific: scope and out of scope, features to test, schedule, resources and roles, environments, entry and exit criteria, risks and mitigations, deliverables and approvals. The plan implements the strategy for one release. In agile teams both are lightweight, often one page held in a wiki.
13 What is a requirements traceability matrix and why use it?
easyAn RTM maps each requirement to the test cases that cover it and to defects raised, usually in a table. It shows coverage gaps: any requirement without a test case is untested. It supports impact analysis when a requirement changes, because you can see which tests to update and rerun, and it gives auditors evidence that requirements were verified. Tools such as Jira with TestRail or Zephyr maintain the links automatically.
14 A developer says a reported bug is not reproducible. What do you do?
mediumCheck what differs: build version, environment, test data, browser, user role and timing. Reproduce again yourself and note the exact steps, then add evidence: screenshots, a screen recording, console and network logs, server logs with timestamps and the user ID. Look for intermittent causes such as race conditions, caching, stale sessions or data dependencies, and give the frequency. Offer a joint debugging session. If it truly cannot be reproduced, keep it open with the details and observe whether it recurs, rather than closing it silently.
15 Explain test levels: unit, integration, system and user acceptance testing.
easyUnit testing checks individual functions or classes in isolation, usually by developers. Integration testing verifies that modules and services interact correctly, including APIs and database calls; approaches include top-down, bottom-up and big bang. System testing validates the complete integrated application against requirements in a production-like environment. User acceptance testing is performed by business users or clients to confirm the system meets their needs before go-live, in alpha (internal) and beta (limited external) forms. Each level catches defects the previous cannot, and defects are cheaper to fix earlier.
16 What is the difference between a test scenario, a test case and a test script?
easyA test scenario is a high-level statement of what to test, such as verify the checkout process. A test case is a detailed set of preconditions, steps, data and expected results for one condition within that scenario, such as checkout with an expired card. A test script is the automation code implementing a test case, or in older usage a written step-by-step procedure. One scenario generates many test cases, and each test case may or may not be automated.
17 How do you test a web form that uploads a file?
mediumTest valid types and sizes, the exact size limit and one byte over, empty files, wrong extension with valid content and valid extension with wrong content (a renamed executable), very long file names and special characters, duplicate names, multiple files, cancel mid-upload, network interruption and large files on slow connections. Check security: server-side validation, no execution of uploaded files, virus scanning, and that links are not guessable. Verify the file is stored, can be downloaded intact and is deleted when expected. Also test accessibility with keyboard-only use and clear error messages.
Frequently asked questions
Is manual testing still a good career in 2026?
Yes, but pure click-through testing is shrinking. Testers who understand risk, exploratory techniques, APIs, SQL and basic automation have the strongest prospects.
What should I learn alongside manual testing?
SQL for data checks, Postman for API testing, browser developer tools, one test management tool and a basic programming language such as Python or Java to move toward automation.
How many test cases should a tester write per day?
There is no universal number, and interviewers distrust quotas. Quality, coverage of requirements and finding real defects matter more than counts.
What is the difference between QA and QC?
Quality assurance is process-oriented and preventive: defining standards and practices so defects are avoided. Quality control is product-oriented and detective: testing the product to find defects.
Related guides
More in Role-wise Interview Questions by Job and Tech Stack
- MERN Stack Interview Questions and Answers
- Next.js Interview Questions and Answers (Next.js 15)
- NLP Interview Questions and Answers
- Node.js Interview Questions and Answers (Node 22)
- NumPy Interview Questions and Answers
- Pandas Interview Questions and Answers
- Performance Testing and JMeter Interview Questions
- Power BI Interview Questions and Answers
- Probability for Data Science Interview Questions and Answers
- Product Analyst Interview Questions and Answers
- PySpark Interview Questions and Answers
- React Hooks Interview Questions and Answers