50 Manual Testing Interview Questions and Answers (2026)

Last updated: October 2026

"Is manual testing still a career?" We hear this a lot. The honest answer: pure click-through testing jobs are shrinking, but the thinking behind manual testing, knowing what to test, finding the edge cases developers missed, and writing a bug report that gets fixed the same day, is what every QA role is built on. Automation engineers who can't think like manual testers write automated tests for the wrong things.

That's why manual testing questions show up in almost every QA interview, from freshers to automation leads. This guide covers 50 of them, from SDLC basics to the scenario questions ("test this pen", "test a login page") that decide most rounds.

Manual testing interview questions: the quick answer

• What gets tested: SDLC and STLC, verification vs validation, test plans, test cases and scenarios, test design techniques (boundary value, equivalence partitioning), types of testing, bug life cycle, severity vs priority, and Agile QA.
• Typical format: a theory round, then live scenario questions: write test cases for a login page, an ATM, a payment flow or an everyday object.
• What wins: structured thinking. Cover functional, negative, boundary, UI, security and performance angles, not just the happy path.
• Tools to mention: Jira for bugs, TestRail, Zephyr or Xray for test management, Postman for API checks, and browser DevTools.

Testing basics (1–12)

1. What is software testing?

Checking whether software works as expected and finding defects before users do. It covers both "does it do what the requirements say" and "does it fail gracefully when something unexpected happens".

2. What is manual testing?

Testing performed by a person without automation scripts: executing test cases, exploring the app and comparing actual results to expected results. It's best for exploratory, usability and ad-hoc testing, and for features that change too often to automate yet.

3. Manual vs automation testing?

4. What are the seven principles of testing?

1. Testing shows the presence of defects, not their absence.
2. Exhaustive testing is impossible.
3. Early testing saves time and money (shift left).
4. Defects cluster together in a few modules.
5. The pesticide paradox: repeating the same tests stops finding new bugs.
6. Testing depends on context.
7. The absence-of-errors fallacy: bug-free software that doesn't meet user needs is still a failure.

5. What is the SDLC?

The Software Development Life Cycle: requirements → design → development → testing → deployment → maintenance. Models include Waterfall, V-model, Iterative, Spiral and Agile.

6. What is the STLC?

The Software Testing Life Cycle: requirement analysis → test planning → test case design → test environment setup → test execution → test closure. Each phase has entry and exit criteria.

7. What is the V-model?

An SDLC model where each development phase has a matching test phase: requirements ↔ acceptance testing, system design ↔ system testing, architecture ↔ integration testing, module design ↔ unit testing. Test planning starts early, alongside development.

8. What is the difference between verification and validation?

Verification: "are we building the product right?" Reviews, walkthroughs and inspections of documents and code, without running it. Validation: "are we building the right product?" Running the software to check it meets user needs.

9. What is the difference between an error, a defect, a bug and a failure?

An error is a human mistake (a developer misreads a requirement). It produces a defect, also called a bug, in the code. When the defective code runs and the system behaves wrongly, that's a failure.

10. What is quality assurance vs quality control?

QA is process-focused and preventive: defining standards, reviews and processes so defects don't happen. QC is product-focused and detective: testing the product to find defects. Testing is part of QC.

11. What is static vs dynamic testing?

Static testing checks work products without running code: requirement reviews, code reviews, walkthroughs. Dynamic testing runs the software. Static testing finds problems earlier, when they're cheaper to fix.

12. What is shift-left testing?

Moving testing earlier in the cycle: testers join requirement discussions, review designs and write test cases before development ends. It catches ambiguous requirements before they become bugs.

Test levels and types (13–24)

13. What are the levels of testing?

Unit testing (individual functions, usually by developers) → integration testing (modules working together) → system testing (the complete application) → acceptance testing (business or users confirm it meets their needs).

14. What is the difference between functional and non-functional testing?

Functional testing checks what the system does: login, search, payments. Non-functional testing checks how well it does it: performance, security, usability, compatibility and reliability.

15. What is smoke testing vs sanity testing?

Smoke testing is a quick, broad check of critical features on a new build to decide whether it's stable enough to test further ("does the app launch, can you log in, can you place an order?"). Sanity testing is a narrow, focused check that a specific fix or change works, usually on a stable build.

16. What is regression testing?

Re-testing existing features after a change to make sure nothing that used to work is now broken. It's the best candidate for automation because it repeats every release.

17. What is retesting vs regression testing?

Retesting checks that a specific bug that was fixed is really fixed, using the same steps. Regression testing checks that the fix (or any change) didn't break other things.

18. What is black box, white box and grey box testing?

Black box: test from the outside, based on requirements, with no knowledge of the code. White box: test with knowledge of the internal code and logic (statement and branch coverage). Grey box: partial knowledge, for example knowing the database schema while testing through the UI.

19. What is exploratory testing?

Simultaneous learning, test design and execution without predefined test cases. It's usually time-boxed (say, a 60-minute session) with a goal, or charter, like "explore the checkout flow with coupon codes". It finds bugs that scripted tests miss.

20. What is ad-hoc testing?

Informal testing without any planning or documentation, often by trying random inputs and actions. Unlike exploratory testing, it has no charter. It's useful for quickly breaking things, but it's hard to reproduce or measure.

21. What is user acceptance testing (UAT)?

Testing done by business users or clients to confirm the system meets their needs before go-live. Alpha testing happens in-house with internal users; beta testing happens with real users in their own environment.

22. What is compatibility testing?

Checking that the app works across browsers (Chrome, Safari, Firefox, Edge), operating systems, devices, screen sizes and network conditions. In India, testing on budget Android phones and slow 4G is especially important.

23. What is usability testing?

Checking how easy and intuitive the app is for real users: can they finish tasks without help, are error messages clear, is navigation obvious? Often done by observing users trying out tasks.

24. What is end-to-end testing?

Testing a complete user flow across all systems involved, for example sign up → browse → add to cart → pay → get the confirmation email → see the order in history, including third-party integrations like payment gateways.

Test design and documentation (25–36)

25. What is a test plan?

A document that defines the scope, approach, resources, schedule, environments, entry and exit criteria, risks and deliverables of testing. It answers what will be tested, how, by whom and when.

26. What is a test strategy vs a test plan?

A test strategy is a high-level, often organisation-wide approach: testing types, tools and standards. A test plan is specific to one project or release and follows the strategy.

27. What is a test scenario vs a test case?

A test scenario is a high-level "what to test", such as "verify login functionality". A test case is a detailed "how to test" with steps, data and expected results, such as "login with a valid email and wrong password shows an 'Invalid credentials' error". One scenario has many test cases.

28. What are the components of a good test case?

Test case ID, title, module, preconditions, test steps, test data, expected result, actual result, status (pass/fail) and priority. Good test cases are clear enough for someone new to run without asking questions.

29. What is boundary value analysis?

Testing at the edges of valid ranges, because bugs cluster there. For an age field that accepts 18–60, test 17, 18, 19, 59, 60 and 61.

30. What is equivalence partitioning?

Dividing inputs into groups that should behave the same way and testing one value from each. For the 18–60 age field: one valid partition (say 30) and two invalid ones (below 18, say 10, and above 60, say 75). It reduces the number of test cases without losing coverage.

31. What is decision table testing?

A table of input-condition combinations and their expected outcomes, used when business rules depend on several conditions. For example, a loan approved only if salary > ₹50,000 AND credit score > 750 AND age < 60: list every combination and its result.

32. What is state transition testing?

Testing how a system moves between states based on events. An ATM card: active → (3 wrong PINs) → blocked; or an order: placed → shipped → delivered → returned. You test valid and invalid transitions.

33. What is error guessing?

Using experience to guess where bugs are likely: empty fields, special characters, very long inputs, double-clicking submit, going back after payment, uploading a 0 KB file. Experienced testers are very good at this.

34. What is a requirement traceability matrix (RTM)?

A table mapping each requirement to its test cases (and often to defects). It ensures every requirement is tested and shows what's affected when a requirement changes.

35. What is test coverage?

A measure of how much of the requirements, features or code is exercised by tests. Requirement coverage comes from the RTM; code coverage (statement, branch) comes from tools developers run.

36. What are entry and exit criteria?

Entry criteria must be true before testing starts: the build is deployed, smoke tests pass, test data is ready. Exit criteria must be true before testing ends: all critical test cases executed, no open critical or high bugs, and the pass rate meets the target.

Defects (37–43)

37. What is the bug (defect) life cycle?

New → Assigned → Open → Fixed → Retest → Verified → Closed. Side paths: Rejected (not a bug), Duplicate, Deferred (fix later), Not reproducible, and Reopened (the fix didn't work).

38. What is severity vs priority?

Severity is how badly the bug affects the system, and is usually set by the tester. Priority is how soon it should be fixed, and is usually set by the product owner or lead.

The "logo misspelt" and "rare admin crash" examples are what interviewers want to hear.

39. What should a good bug report contain?

A clear title, environment (build, browser or device, OS), preconditions, numbered steps to reproduce, expected vs actual result, severity and priority, and evidence: screenshots, screen recordings, console or network logs. A good title names the problem and where it happens: "Checkout: 'Pay' button stays disabled after applying a valid coupon on iOS Safari".

40. What do you do if a developer says "it's not a bug"?

Re-check the requirement and reproduce the issue. Then discuss with evidence: steps, a video, the requirement reference. If the requirement is unclear, involve the product owner or business analyst to decide. Keep it about the product, not about being right.

41. What do you do with a bug you can't reproduce consistently?

Note the exact conditions when it happened (time, data, device, network), check logs, try variations (different data, slower network, multiple tabs), and log it with all the details and a frequency, such as "3 out of 10 attempts". Intermittent bugs often point to race conditions or caching.

42. What is defect leakage?

Defects found by users in production that testing missed. Defect leakage % = (bugs found after release ÷ total bugs found) × 100. Low leakage is a key quality metric.

43. What is a defect triage meeting?

A regular meeting where QA, developers and the product owner review new bugs, confirm whether they're valid, set severity and priority, and assign owners. It keeps the bug backlog under control.

Agile QA and scenario questions (44–50)

44. What is the role of a tester in Agile?

Testers work inside the sprint team: they refine user stories, clarify acceptance criteria, write test cases early, test as soon as a story is ready, automate regression where possible, and take part in stand-ups, sprint reviews and retrospectives. Quality is the whole team's responsibility.

45. What is the definition of done, and what are acceptance criteria?

Acceptance criteria are conditions a specific user story must meet, often written as Given/When/Then. The definition of done is a team-wide checklist every story must meet before it's "done": code reviewed, tested, no open critical bugs, documentation updated.

46. How would you test a login page?

Group your answer:

• Functional: valid login, wrong password, unregistered email, empty fields, "remember me", logout, "forgot password" flow.
• Validation: email format, password masking, maximum length, leading and trailing spaces, case sensitivity.
• Security: account lockout after N failed attempts, SQL injection and script inputs, HTTPS, session timeout, no password in URLs or logs, the back button after logout.
• UI and usability: tab order, Enter to submit, clear error messages, mobile layout.
• Compatibility and performance: different browsers and devices, response time under load.

47. How would you test an ATM?

Valid and invalid card, correct and wrong PIN (and blocking after 3 tries), withdrawal within and above balance and daily limit, amounts not in multiples of ₹100, insufficient cash in the machine, receipt printing, a timeout if the user walks away, card retention, a network failure mid-transaction (the account shouldn't be debited without cash), and language selection.

48. How would you test a pen?

Interviewers ask this to see how you think. Clarify the requirements first: what type of pen, and who uses it? Then cover functional checks (writes smoothly, ink colour, cap fits, click mechanism works), boundaries (writes at different angles, on different paper, how many pages before the ink runs out), durability (dropping it, extreme temperatures), usability (grip comfort) and safety (non-toxic ink, the cap doesn't pose a choking hazard).

49. You have limited time and a release tomorrow. How do you decide what to test?

Use risk-based testing. Prioritise critical business flows (login, payment, checkout), recently changed areas, modules with a history of bugs, and features with the most users. Run smoke and sanity tests first, then high-priority regression. Communicate clearly what was not tested so the team can make an informed release decision.

50. How would you move from manual testing to automation?

Strengthen your testing basics first, then learn one language (Java or Python), Selenium or Playwright for UI, Postman and REST Assured for APIs, Git, and a CI tool. Start by automating the stable regression cases you already run manually. See our Selenium interview questions and API testing interview questions for the next step.

Common mistakes candidates make

• Testing only the happy path in scenario questions.
• Confusing severity and priority, or giving examples where both are always the same.
• Writing vague test cases like "check login works".
• Mixing up smoke and sanity testing.
• Saying "manual testing is dead". It signals you don't understand QA.

A 5-day manual testing prep plan

Which roles ask manual testing, and what to read next

Manual testing questions come up for QA engineers, software testers, test analysts, QA leads and automation engineers. Prepare your resume with our QA engineer resume examples and software test engineer resume examples. For pay, see Weekday's salary pages.

Related prep: quality engineer interview questions, Selenium interview questions, API testing interview questions and SQL interview questions. SQL is increasingly expected of testers.

Frequently asked questions

Is manual testing a good career in 2026?

As a starting point, yes. Pure manual roles are fewer and pay less than automation roles, so plan to add API testing, SQL and one automation tool within your first one or two years.

What are the most asked manual testing interview questions for freshers?

STLC, smoke vs sanity, severity vs priority with examples, the bug life cycle, test case vs test scenario, boundary value analysis, and "write test cases for a login page".

Do testers need to know coding?

For manual roles, not deeply, but SQL and basic API testing with Postman are now expected. For automation roles, yes: Java, Python or JavaScript.

Is the ISTQB certification useful?

ISTQB Foundation Level helps with shortlisting, especially at IT services companies and for freshers. It standardises your terminology, which helps in theory rounds.

How do I answer "test this object" questions?

Ask clarifying questions first, then organise your answer by category: functional, negative and boundary, usability, performance and durability, safety and security. Structure matters more than the number of test cases.

Ready to apply? Find QA and testing jobs on Weekday, and check your resume with our free ATS resume checker before you send it.