Manual Testing Interview Questions

Manual testing interview questions#

Manual testing interviews mix definitions with "how would you test this?" scenarios. For scenarios, think out loud: clarify requirements, then cover positive, negative, boundary, UI, security and performance angles.

1. What is the difference between a test scenario and a test case?#

A scenario is a one-line statement of what to test ("user can reset password"). A test case is the detailed how: preconditions, steps, data and expected result. One scenario usually becomes several test cases.

2. What fields does a good test case have?#

ID, title, priority, preconditions, test data, steps, expected result, actual result and status — written so someone else can run it without help.

3. Explain equivalence partitioning and boundary value analysis.#

EP splits inputs into groups the system treats the same and tests one value per group. BVA tests at and just around each boundary, because off-by-one errors cluster there. For an 18–60 age range: EP tests 10, 35, 75; BVA tests 17, 18, 19, 59, 60, 61.

4. When would you use a decision table?#

When the outcome depends on combinations of conditions — discounts, shipping rules, eligibility. It ensures every combination is covered and often exposes gaps in requirements.

5. What is state transition testing?#

Testing how a system moves between states based on events — e.g. an account locking after three failed logins and a correct password resetting the counter.

6. What is exploratory testing? Is it the same as ad-hoc testing?#

Exploratory testing is structured: a charter, a time-box, notes and a debrief, with test design happening during execution. Ad-hoc testing is informal and unstructured.

7. What should a bug report contain?#

A clear title, environment and build, preconditions, numbered steps, expected vs actual result, severity, priority, frequency and evidence (screenshots, video, logs).

8. Severity vs priority — give examples where they differ.#

High severity/low priority: a crash in a rarely used admin report. Low severity/high priority: a misspelled brand name on the homepage before a launch.

9. Describe the defect life cycle.#

New → Assigned → Open → Fixed → Retest → Verified → Closed, with side paths for Rejected, Duplicate, Deferred, Cannot reproduce and Reopened.

10. What is the difference between retesting and regression testing?#

Retesting re-runs the failed test to confirm a fix. Regression testing checks that the change didn't break other, previously working features.

11. Smoke vs sanity testing?#

Smoke testing is a broad, shallow check that a new build is stable enough to test. Sanity testing is a narrow check that a specific fix or change works.

12. How would you test a login page?#

Valid login; wrong password; unregistered email (generic error, no account enumeration); empty fields; invalid email format; case-insensitive email; password masking; "show password" toggle; lockout after repeated failures; "remember me"; session timeout; back button after logout; SQL/script injection in fields; HTTPS only; keyboard navigation and screen-reader labels; behaviour on mobile and slow networks.

13. How would you test a pen?#

Clarify the purpose first, then cover functional (it writes, ink flows, cap fits), boundary (writing on different surfaces, temperatures), durability (how many metres of ink, drops), usability (grip, comfort), safety (non-toxic ink, cap choking hazard) and appearance. The point is structured thinking, not the pen.

14. You found a bug but the developer says it's not reproducible. What do you do?#

Check environment differences (data, role, browser, build), add a screen recording and logs, try to reproduce on their machine together, and note the exact frequency. If it's intermittent, say so and capture as much evidence as possible.

15. What do you do when there's no time to test everything?#

Prioritise by risk: critical business flows, changed areas and historically buggy modules first. Run smoke and high-priority regression, explore the riskiest areas, and clearly report what wasn't tested.

16. What is the difference between alpha and beta testing?#

Alpha testing is done internally before release; beta testing is done by a limited group of real users in a production-like setting.

17. What is UAT and who performs it?#

User Acceptance Testing confirms the system meets business needs. It's done by business users, clients or the product owner, often with QA support.

18. Why do testers still matter when developers write automated tests?#

Developers test that the code does what they intended. Testers question whether it does what users need, explore unexpected behaviour, and think about risk across the whole system.