Practice manual testing interview questions on boundary values, exploratory testing, regression and defect reporting, with a coupon-rule test exercise. Start with the question, explain the mechanism, and then state an assumption or tradeoff. The scenarios below are original practice examples, not questions supplied by an employer.
How do you turn a requirement into tests?
Identify the intended behavior, inputs, states and consequences of failure. Ask about unclear rules before generating many cases. Partition inputs into meaningful groups and select boundaries where behavior changes. Trace each important test to a risk or requirement. A hundred similar happy-path tests can provide less confidence than a small set covering the real decision points and failure behavior.
What is boundary-value testing?
It checks values around the limits where a rule changes. For an inclusive age range of 18 to 60, consider 17, 18, 60 and 61, then cover a normal value and invalid input types where relevant. State whether the boundaries are inclusive; guessing that detail can make an otherwise careful test plan wrong. Include the visible result and stored result if both matter to the application.
How do exploratory and scripted testing work together?
Scripted tests provide repeatable checks of known behavior. Exploratory testing combines learning, investigation and test design while examining unfamiliar or risky areas. Use a focused charter, a time box and notes about what you covered. Exploration should produce evidence and follow-up tests, not just unrecorded clicking. Explain a case where a discovery changed your understanding of the product.
What makes a useful bug report?
Provide the environment, relevant data, concise reproduction steps, expected behavior and actual behavior. Include evidence that helps the developer isolate the problem without exposing private information. State frequency and business impact separately from your proposed cause. A report that says 'checkout is broken' is harder to act on than one identifying which customer state and action trigger the failure.
How do you select regression tests under time pressure?
Use the change scope, dependencies, critical user journeys and previous defect history to choose checks. Explain what is included, what is omitted and the remaining risk. Verify the fix directly and test neighboring behavior that might have changed. Do not imply that every release can receive a complete rerun. A clear risk-based recommendation helps the release owner make an informed decision.
Worked example
Original rule: a coupon gives 10% off an eligible subtotal of at least 100, with a maximum discount of 25. Check 99.99, 100, 249.99, 250 and 250.01, and clarify rounding rules. At 100 the discount is 10; at 250 it reaches 25. At 300 it remains 25 rather than increasing to 30.
Add an ineligible product, an expired coupon and a second attempt to apply the same code. Ask whether shipping contributes to eligibility. Write expected results before executing tests so an unexpected display does not silently redefine the requirement.
Practice plan
Turn the coupon rule into a short test table with input, expected discount and the risk covered. Write one bug report for an uncapped discount. Then propose the smallest regression set you would run after that defect is fixed and explain what remains untested.
Use Cluegent during preparation to review your own answer: ask for one incorrect assumption and one follow-up question, then respond again without suggestions. Check current plans before choosing a subscription. Follow the employer's rules during the actual interview.
Sources checked
These official references support the guide. Product details and technical documentation can change; check the linked source for current information.
Where Cluegent helps
Cluegent supports permitted live workflows with transcript context, typed prompts, screenshot-aware answers, resume context, custom response behavior, quick action buttons, and a private desktop overlay. It is most useful when you already understand the subject and need help staying structured under pressure.
Frequently asked questions
Do manual testers need programming?
Requirements vary by role. Test design, investigation and clear reporting remain useful even when automation or scripting is also expected.
How many test cases should I propose?
Choose cases that cover important behavior and risks, and explain the coverage. A raw count does not establish quality.