ISTQB Foundation Level Sample Questions and Answers

TL;DR

Use these original ISTQB Foundation sample questions to practice concept recognition and reasoning. For every answer, explain why the correct option fits the question and why each distractor fails, then revisit the relevant official syllabus learning objective instead of memorizing letters.

Key Takeaways

• Answer from the terminology and learning objective being tested, not from a favorite local team convention.
• Eliminate options that use absolute claims, confuse related terms, or solve a different problem than the stem asks.
• Practice should include explanation, distractor analysis, and mapping back to the syllabus, not answer-letter memorization.
• Test techniques become easier when you derive partitions, boundaries, decisions, states, and coverage from a small model.
• Use timed mixed sets only after concept-focused practice reveals and repairs weak areas.
• These questions are original study material, not official exam questions or a prediction of a live examination.

These ISTQB Foundation sample questions are original practice material designed to build exam reasoning, not reproduce official or live exam content. They cover testing principles, lifecycle context, static testing, test analysis and design, management, defect work, and tool support at a foundation level.

The explanations matter more than the answer letters. Work each question without looking ahead, state the concept in your own words, eliminate distractors, and only then compare your reasoning. Always use the current official syllabus and exam-provider instructions as the authority for your examination.

TL;DR

Do not infer actual exam distribution, wording, duration, or pass rules from this article. Those details can vary by current scheme, language, accommodations, and provider.

1. How to Use These ISTQB Foundation Sample Questions

Start with a closed-book attempt. For each stem, underline the decision word: best, most likely, primary, difference, or example. Identify the topic before reading the options. A question about the purpose of regression testing should not be answered with the definition of confirmation testing, even if that option describes a real activity.

Use a four-part review record: chosen answer, correct answer, concept, and error cause. Error causes might be terminology confusion, missed qualifier, weak technique application, invented assumption, rushed arithmetic, or knowledge gap. Got it wrong is not diagnostic enough.

Explain every distractor. If the correct answer is B, say why A, C, and D are weaker or false in the context of the stem. This protects against lucky guesses. Then locate the learning objective in the current official syllabus and review its terms, examples, and level of expected understanding.

Keep two scores: first-attempt accuracy and explained mastery. A question is mastered only when you can solve a varied version and teach the reasoning. Repeating the identical set can inflate recall without improving transfer. The software testing fundamentals guide is a useful refresher before mixed practice.

2. Testing Fundamentals Practice Questions

Question 1. Which statement best describes a testing objective?

A. Prove that the software contains no defects. B. Provide information that supports decisions about quality and risk. C. Demonstrate that every possible input has been executed. D. Transfer responsibility for product quality to the test team.

Answer: B. Testing can reveal failures, evaluate work products, reduce uncertainty, and provide decision information. It cannot prove defect absence for a nontrivial system, exhaustive input execution is normally impossible, and quality remains a shared responsibility.

Question 2. Why can testing show the presence of defects but not their absence?

A. Testers are not allowed to inspect source code. B. Defects exist only after release. C. Testing samples conditions and can expose failures, but unexecuted conditions may still contain defects. D. Automated tests cannot verify expected results.

Answer: C. A passing selected set provides evidence for those modeled conditions, not a mathematical guarantee over every possible state and interaction. Static and dynamic techniques, including source review, can both contribute.

Question 3. A test set has been repeated unchanged for many releases and finds fewer new defects. Which principle is most relevant?

A. Defect clustering. B. Pesticide paradox. C. Absence-of-errors fallacy. D. Early testing.

Answer: B. Repeating the same checks can make them less effective at finding new problems. Refresh tests using changed risks, incidents, new data, and other techniques. This does not imply deleting stable regression checks that still protect important behavior.

Question 4. A product meets its written specifications but users cannot complete their main task. Which principle does this illustrate?

A. Exhaustive testing is impossible. B. Defects cluster together. C. Absence-of-errors fallacy. D. Tests wear out.

Answer: C. Correctness against a specification does not guarantee usefulness or satisfaction of actual user needs. Validation and early stakeholder examples help expose the gap.

3. Lifecycle and Test-Level Questions

Question 5. Which activity is an example of shift-left testing?

A. Waiting for system test to review ambiguous acceptance rules. B. Reviewing examples and testability during refinement. C. Running all regression tests only after production deployment. D. Moving every test to the user interface.

Answer: B. Shift left means performing suitable test activities earlier, such as reviews, examples, static analysis, unit testing, and contract discussion. It does not mean that later validation, monitoring, or production learning disappears.

Question 6. What is the primary focus of component testing?

A. Interfaces among complete external organizations. B. Individual components in isolation or with controlled collaborators. C. User acceptance of the full business process. D. Production incident response.

Answer: B. Component testing examines the smallest testable software parts according to the architecture, often using stubs, fakes, or mocks for dependencies. System and acceptance testing address broader outcomes.

Question 7. A fixed defect is tested using the original failing case. Which activity is this?

A. Regression testing. B. Confirmation testing. C. Exploratory testing. D. Maintenance testing.

Answer: B. Confirmation testing checks that the specific defect was corrected. Regression testing looks for unintended effects elsewhere. A fix often calls for both.

Question 8. Which is a maintenance-testing trigger?

A. Only a new product launch. B. A platform migration, operational change, or retirement decision. C. Only the first execution of a component test. D. A tester joining the team.

Answer: B. Changes, migrations, production fixes, environment updates, and retirement can all create maintenance-testing needs. Scope is chosen from change impact and risk.

4. Static Testing and Review Questions

Question 9. What distinguishes static testing from dynamic testing?

A. Static testing never uses tools. B. Static testing evaluates work products without executing the software under test. C. Static testing is performed only by developers. D. Static testing cannot identify requirement defects.

Answer: B. Reviews and static analysis evaluate artifacts without executing the tested software. Tools can support both, multiple roles can participate, and early requirement defects are an important target.

Question 10. Which is a benefit of early reviews?

A. They guarantee no dynamic testing is required. B. They can find ambiguity and inconsistency before implementation makes correction more disruptive. C. They prove every user need is known. D. They make defect reporting unnecessary.

Answer: B. Early feedback can reduce rework and improve shared understanding. It does not guarantee completeness or replace executable evidence.

Question 11. In a formal review, who typically ensures the meeting is run effectively and participants remain focused?

A. The author acting as sole decision maker. B. The moderator or facilitator. C. The database administrator in every review. D. The customer who reported the last defect.

Answer: B. Review roles and formality depend on the review type, but facilitation is the role associated with effective conduct. Avoid assuming one person must hold every role.

Question 12. Which review finding is most actionable?

A. This requirement is bad. B. The word quickly is unclear. C. AC-4 says the transfer completes quickly, but no response threshold or measurement point is defined. D. Developers should understand this.

Answer: C. It identifies location, ambiguity, and missing information without blame. A useful review comment helps the author and stakeholders make a decision.

5. Equivalence, Boundary, and Decision Questions

Question 13. An integer field accepts values 10 through 20 inclusive. Which set represents the three basic equivalence partitions?

A. Less than 10, 10 through 20, greater than 20. B. 10, 15, and 20 only. C. Even, odd, and missing. D. 9, 10, 11, 19, 20, and 21.

Answer: A. Those predicates define invalid-low, valid, and invalid-high regions for the range rule. Option D is a boundary-focused set. Missing and wrong type may be additional contract partitions but are not stated in the range alone. Review equivalence partitioning with examples for deeper practice.

Question 14. For the same inclusive range, which values provide robust boundary coverage around both endpoints?

A. 10 and 20. B. 9, 10, 11, 19, 20, and 21. C. 1, 15, and 100. D. Every integer from 10 through 20.

Answer: B. The set includes each boundary, a valid neighbor inside, and an invalid neighbor outside. A nominal value may also be added depending on the chosen boundary convention.

Question 15. Which technique is most suitable for a discount outcome determined by customer type, coupon state, and order threshold?

A. Statement testing. B. Decision-table testing. C. Only error guessing. D. Only random input generation.

Answer: B. A decision table makes interacting conditions, combinations, and actions visible. Boundaries can then be applied to the order threshold.

Question 16. Which technique best models allowed and forbidden changes among draft, approved, shipped, and canceled orders?

A. State-transition testing. B. Equivalence partitioning only. C. Checklist-based review only. D. Statement coverage only.

Answer: A. The result depends on current state and event history. A state model supports valid transitions, invalid transitions, and transition sequences.

6. White-Box and Coverage Questions

Question 17. What does 100 percent statement coverage mean?

A. Every possible path has executed. B. Every executable statement in the measured scope has executed at least once. C. Every defect has been found. D. Every decision outcome has occurred.

Answer: B. Statement coverage says nothing by itself about every branch, path, requirement, data class, or defect. Its value depends on the measured scope and test oracles.

Question 18. If tests achieve 100 percent branch coverage, which statement is true?

A. Every identified branch outcome in scope has executed. B. All combinations of conditions have executed. C. No additional black-box testing is useful. D. The software is ready for release.

Answer: A. Branch coverage is stronger than statement coverage for decision outcomes, but it does not imply all paths, combinations, or requirements are covered. Release readiness needs broader evidence.

Question 19. Why can structural coverage reveal missing tests?

A. It measures which selected code structures executed and exposes unexecuted elements. B. It automatically supplies correct business expected results. C. It replaces risk analysis. D. It verifies user satisfaction directly.

Answer: A. Coverage highlights structural gaps. Testers still need meaningful data, oracles, black-box techniques, and risk reasoning to decide whether and how to cover them.

Question 20. Which statement about code coverage is best?

A. Higher coverage always means better testing. B. Coverage is useless unless it is 100 percent. C. Coverage is one evidence source and must be interpreted with test quality, risk, and scope. D. Coverage measures the number of defects prevented.

Answer: C. A high number can come from weak assertions or low-value execution. A lower number can also hide important omissions. Interpret the measure, do not worship it.

7. Test Management and Risk Questions

Question 21. Which statement best describes product risk?

A. The possibility that a work estimate is late. B. The possibility that a product characteristic causes negative consequences. C. The number of test cases not executed. D. The salary cost of the test team.

Answer: B. Product risk concerns potential product failure and impact. Project risks threaten delivery activities, resources, schedule, or organization. One can influence the other, but the categories support different responses.

Question 22. Testing time is reduced. What is the most appropriate response?

A. Execute tests in alphabetical order. B. Hide the omitted scope to avoid concern. C. Reprioritize using risk, critical journeys, change impact, and available evidence, then communicate residual risk. D. Run every test with no expected-result checks.

Answer: C. Risk-based selection makes the tradeoff visible. Removing or weakening oracles only creates misleading activity.

Question 23. Which is a useful exit criterion?

A. The tester feels confident. B. Every conceivable input has passed. C. Release-critical scenarios have trustworthy results, failures are dispositioned, and unresolved high risks have accountable decisions. D. No one has reported a defect today.

Answer: C. It connects evidence, risk, and decision ownership. Exit criteria guide a stopping decision and do not prove perfection.

Question 24. Why is independent testing sometimes beneficial?

A. Independent testers are always more skilled than authors. B. Different perspectives and assumptions can reveal different defects. C. Developers should never test their own code. D. Independence guarantees unbiased decisions.

Answer: B. Distance can introduce useful perspective, while too much distance can slow feedback or reduce context. Use an appropriate degree of independence and collaboration.

8. Defects, Tools, and ISTQB Foundation Sample Questions

Question 25. Which defect report title is most useful?

A. It does not work. B. Checkout bug urgent. C. Stored-card checkout returns an error after authorization and no order is created. D. Developer broke payment.

Answer: C. It states scope and observed outcome without blame. The report still needs build, data, reproduction, expected result, impact, and evidence.

Question 26. What is a common risk of test automation?

A. Tools always find more defects than people. B. Unrealistic expectations about benefits and underestimated maintenance. C. Automation cannot compare actual and expected results. D. Automated checks cannot run repeatedly.

Answer: B. Tools can accelerate repeatable work and provide consistent evidence, but require design, integration, trustworthy oracles, maintenance, and skilled interpretation.

Question 27. Which activity is most suitable for a test management tool?

A. Deciding product quality without human judgment. B. Linking test conditions, executions, defects, and evidence. C. Proving missing requirements do not exist. D. Generating a release decision from raw pass percentage alone.

Answer: B. Tools support organization and traceability. Accountable people interpret evidence and risk.

Question 28. A defect is fixed, but a related existing function now fails. What testing concept is demonstrated?

A. Confirmation testing found the original issue. B. Regression testing revealed an unintended effect. C. Static analysis proved the release safe. D. Acceptance criteria replaced test design.

Answer: B. The new failure is an unintended effect in existing behavior, which is the target of regression testing.

9. Scenario-Based Practice Set

Use the following scenarios to practice combining concepts rather than recalling isolated definitions.

Scenario A: A bank transfer form allows amounts from 1.00 through 10,000.00, but transfers above 5,000.00 require additional approval. Basic range partitions alone are insufficient because the accepted domain has two business outcomes. Model invalid low, standard accepted, approval-required accepted, and invalid high, then apply cent-level boundaries at 1.00, 5,000.00, and 10,000.00. A decision table may add role and account status.

Scenario B: A password-reset link can be unused, expired, already used, or revoked after a security event. This is a state problem, not only an input partition. Test transitions from issued to used or expired, repeated use, concurrent requests, and session invalidation. Static review can examine the state rules before code exists.

Scenario C: A regression suite is green after repeated reruns, but the first run contained six unknown infrastructure failures and a critical new workflow has no test. A green dashboard does not establish adequate exit. Investigate unknowns, obtain credible evidence for the new risk, and report the limitation.

For each scenario, name the test objective, technique, test basis, oracle, risk, and completion evidence. That structure turns memorized definitions into decisions, which improves both certification practice and job interviews.

10. Build a Study and Mock-Test Plan

Create a syllabus map with learning objectives, confidence, first-attempt results, and last reviewed date. Study in short loops: concept, personal example, focused questions, explanation, and correction. Mix topics only after each has a base level of understanding. Spaced review is more useful than one long cramming session.

A practical cycle can be:

1. Read a small official syllabus section.
2. Write one product example and one non-example.
3. Solve five to ten original questions.
4. Explain every option without notes.
5. Classify mistakes and revisit the source.
6. Solve a changed scenario after a delay.

Later, use timed mock sets under the conditions specified by your examination provider. Do not spend so long on one uncertain question that you abandon easier items. Mark it, eliminate options, choose the best supported answer, and return if the interface and time allow.

Keep vocabulary precise. Confirmation is not regression. Error, defect, failure, and root cause are related but distinct. Test basis, test condition, test case, test procedure, and testware have different purposes. A personal glossary with examples is more durable than copied definitions.

11. Score Practice Without Memorizing Answers

A simple tool can randomize options and track concept tags, but it should not pretend to be an official exam simulator. Preserve the answer explanation and source topic. This runnable Node.js example scores a local practice set. Save it as practice.mjs and run node practice.mjs:

const questions = [
  { id: 1, topic: 'principles', correct: 'B', chosen: 'B' },
  { id: 2, topic: 'techniques', correct: 'C', chosen: 'A' },
  { id: 3, topic: 'management', correct: 'A', chosen: 'A' },
  { id: 4, topic: 'techniques', correct: 'D', chosen: 'D' }
];

const summary = questions.reduce((acc, question) => {
  const topic = acc[question.topic] ?? { correct: 0, total: 0 };
  topic.total += 1;
  topic.correct += Number(question.chosen === question.correct);
  acc[question.topic] = topic;
  return acc;
}, {});

const correct = questions.filter((question) => question.chosen === question.correct).length;
console.log(`Score: ${correct}/${questions.length}`);
console.table(summary);

Use topic results to choose review, not to predict an official score from four items. Add an error-reason field and an explanation check. If you guessed correctly, mark it for review. Avoid sharing recalled live questions, and use authorized official sample material alongside original practice.

12. Prepare for Certification and QA Interviews

Certification questions usually test a defined body of knowledge, while job interviews test application, communication, and experience. The same vocabulary helps, but a job answer should include context and judgment. Regression testing checks unintended effects is correct. A stronger interview answer adds how you select scope from change impact, critical paths, dependencies, and defect history.

Build examples around a familiar product: ecommerce, banking, booking, or a public demo app. Apply partitions, boundaries, decisions, states, reviews, risk, entry and exit criteria, defects, and tools to the same product. This creates connected understanding instead of isolated flashcards.

Be honest about experience. Passing a certification does not equal production delivery experience, and a tutorial project should be labeled accurately. Explain what you practiced, the artifact you created, the evidence you collected, and what you would do differently.

For broader preparation, use the manual QA tester interview questions guide to practice scenarios, SQL, APIs, Agile collaboration, and behavioral examples. Certification can strengthen vocabulary, but interview credibility comes from applying it to decisions.

Interview Questions and Answers

Q: What are the seven testing principles used for?

They are general observations that shape realistic test strategy, such as recognizing that exhaustive testing is impossible and that context matters. I use them to challenge claims and choose better approaches, not as rigid procedures.

Q: What is the difference between an error, defect, failure, and root cause?

An error is a human action that produces an incorrect result. A defect is an imperfection in a work product, and a failure is observed incorrect behavior during execution. Root cause is the fundamental reason the defect or escape occurred and can include technical and process factors.

Q: How are verification and validation different?

Verification evaluates whether specified requirements or work-product expectations are met. Validation evaluates whether the product fulfills intended use and stakeholder needs. Reviews and executable tests can contribute according to the artifact and objective.

Q: What is the difference between confirmation and regression testing?

Confirmation testing checks that a particular defect has been fixed. Regression testing looks for unintended effects of change on existing behavior. A defect fix usually receives targeted confirmation plus change-informed regression.

Q: What is test basis?

The test basis is the body of knowledge used for test analysis and design, such as requirements, user stories, architecture, contracts, regulations, or risk analysis. Its gaps and contradictions can themselves be findings.

Q: Explain equivalence partitioning.

It divides a domain into classes expected to receive the same relevant treatment. I select representatives from each important valid and invalid class, then challenge transitions with boundary analysis. Classes are based on behavior, not convenient appearance.

Q: Explain boundary value analysis.

It targets values at and immediately around transitions because comparison, precision, and endpoint errors often occur there. I identify partitions first, define inclusivity and increment, then select boundary neighbors with expected outcomes.

Q: When would you use a decision table?

I use one when outcomes depend on combinations of conditions, such as customer type, coupon state, and order threshold. It exposes missing, impossible, and conflicting rules and supports representative combination tests.

Q: What is state-transition testing?

It models system states, events, allowed transitions, forbidden transitions, and sequences. It is useful when history changes the result, such as order cancellation, account locking, or token reuse.

Q: What does 100 percent branch coverage prove?

It shows that every identified branch outcome in the measured scope executed. It does not prove every path, condition combination, requirement, data class, or defect was covered. Oracle quality and risk remain important.

Q: How do you prioritize tests when time is limited?

I prioritize by consequence, exposure, recent change, critical usage, dependencies, defect history, detectability, and recovery. I preserve strong oracles on the highest risks and communicate omitted scope plus residual risk.

Q: What makes a good defect report?

It has a concise observed-versus-expected title, exact build and environment, minimal reproduction, sanitized data, observed and expected outcomes, frequency, impact, and focused evidence. It enables a decision or next experiment without blame.

Q: What are entry and exit criteria?

Entry criteria describe prerequisites that make a test activity ready and its evidence valid. Exit criteria describe when evidence is sufficient for transition or decision. Both should be measurable, owned, risk-based, and paired with an exception path.

Q: What are benefits and risks of test automation?

Automation can provide fast repeatable feedback, broader data execution, and consistent collection. Risks include unrealistic expectations, weak oracles, maintenance burden, flaky results, and overreliance on what is easy to automate. Tooling supports judgment rather than replacing it.

Q: Why is independent testing useful?

A different perspective can expose assumptions and defects the author misses. Independence has tradeoffs, including slower feedback and less context, so I combine appropriate independence with close collaboration and early testing.

Q: How do you know when testing is complete?

Testing is sufficient for a decision when planned priority risk coverage has trustworthy results, important failures are understood, and residual risk is explicit. Exit criteria and context guide the stop decision. Testing does not prove that no defect remains.

Common Mistakes

• Memorizing answer letters instead of concepts and distractor reasoning.
• Treating local team vocabulary as the official definition without checking context.
• Missing qualifiers such as best, primary, or most likely.
• Assuming 100 percent structural coverage proves complete testing.
• Confusing confirmation testing with regression testing.
• Applying boundaries before defining the behavioral partitions.
• Selecting a true statement that does not answer the stem.
• Inventing requirements that are not present in the scenario.
• Repeating one mock set until recall inflates the score.
• Sharing or seeking recalled live examination content.
• Using unofficial practice instead of checking the current official syllabus and provider rules.

Conclusion

These ISTQB Foundation sample questions build useful skill only when you explain the concepts, distractors, and scenario assumptions. Use original practice to expose gaps, then return to the official syllabus as the authority. Mix technique application with terminology so you can recognize concepts in unfamiliar wording.

Complete the questions once without notes, classify every error, and create a changed example for each weak topic. Then repeat with a timed mixed set and practice the interview answers aloud. That sequence builds certification readiness and practical QA reasoning together.

Interview Questions and Answers

Frequently Asked Questions

Related Guides

• AI in Software Testing Interview Questions and Answers
• API Test Engineer Interview Questions and Answers (2026)
• API testing Scenario-Based Interview Questions and Answers (2026)
• Appium Interview Questions and Answers (2026)
• Appium Scenario-Based Interview Questions and Answers (2026)
• Cypress Scenario-Based Interview Questions and Answers (2026)