Manual testing interview questions, with sample answers

Fifteen common manual testing interview questions

1. What is the difference between verification and validation?
2. Explain unit, integration, system and acceptance testing.
3. Functional versus non-functional testing?
4. Smoke, sanity and regression testing — differences?
5. What makes a good test case?
6. Explain boundary value analysis and equivalence partitioning.
7. Write test cases for a login page.
8. What goes into a good bug report?
9. Severity versus priority — give an example of each combination.
10. Describe the defect life cycle.
11. What is exploratory testing, and when is it most useful?
12. What is the software testing life cycle?
13. What would you do if a developer rejected your bug?
14. How do you test with incomplete requirements?
15. When should a test be automated rather than run manually?

Testing types

Test design techniques

• Equivalence partitioning: divide inputs into groups expected to behave the same and test one value from each — for an age field accepting 18–60: below 18, 18–60, above 60.
• Boundary value analysis: test at and around the edges — 17, 18, 19, 59, 60, 61 — where defects cluster.
• Decision tables for combinations of conditions; state transition testing for workflows such as order status.
• Error guessing uses experience: empty inputs, special characters, very long strings, double submissions.

Login page test cases

Valid credentials log in; invalid password shows an error without revealing which field was wrong; empty fields are validated; password is masked; account locks after repeated failures; “forgot password” works; leading and trailing spaces are handled; very long inputs and special characters don't break the page; the session expires appropriately; the page works with keyboard only and with a screen reader; login over insecure HTTP is not possible; and behaviour is consistent across supported browsers and devices.

Bug reports, severity and priority

• A good bug report: clear title, environment, steps to reproduce, expected versus actual result, evidence such as screenshots or logs, and severity.
• Severity is technical impact; priority is how urgently to fix it. A crash in a rarely used admin report: high severity, lower priority. A misspelt company name on the home page: low severity, high priority.
• Defect life cycle: new, assigned, open, fixed, retest, closed — or reopened, rejected, deferred or duplicate along the way.
• When a bug is rejected, reproduce it again, add evidence, check the requirement, and discuss calmly — the goal is a shared understanding, not winning.

Exploratory testing and automation

Exploratory testing combines learning, test design and execution at once, guided by a charter such as “explore checkout with saved cards for 45 minutes”. It finds issues scripted tests miss, especially in new features and with unclear requirements. Automate tests that are repetitive, stable and run often, such as regression suites; keep manual testing for exploration, usability and one-off checks. See Selenium interview questions and QA engineer interview questions.

Practising

Reading answers is not the same as saying them. Pick ten of the questions above and answer them aloud against a timer; a free AI interview assistant like CoPilot Interview can ask software testing questions in a mock interview and flag answers that ran long or lacked an example. Practise writing test cases for everyday objects and simple screens out loud — it's the most common practical question.

Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly. Everything else on this page applies whichever tool you use, or none.

Frequently asked questions

What are common manual testing interview questions?

Testing levels and types, smoke versus sanity versus regression, test case writing, equivalence partitioning and boundary value analysis, bug reports, severity versus priority, the defect life cycle, exploratory testing and the STLC.

What is the difference between severity and priority?

Severity is the technical impact of a defect; priority is how soon it should be fixed. They can differ — a severe bug in a rarely used feature may be low priority.

What is boundary value analysis?

A technique that tests values at and around the edges of valid input ranges, where defects are most likely.

Smoke testing or sanity testing?

Smoke testing broadly checks that a new build's critical functions work; sanity testing narrowly checks that a specific change or fix works.