ISTQB Foundation Level (CTFL) V4.0 + Practice Exams - 2025

Testing uncovers defects before they cause failures, ensuring software quality and protecting users. It involves all stakeholders and aligns testing with scope, time, budget, and quality constraints.

Outline the objectives of testing, evaluating requirements, designs, and code, triggering defects, ensuring test coverage, reducing risk, verifying compliance, and informing stakeholders.

Identify typical testing objectives and distinguish validation from verification to build confidence in quality and reduce risk in the testing process.

Differentiate errors, defects, and failures, and apply root cause analysis to reduce defects. Learn how testing reports defects to measure quality, while distinguishing false positives and false negatives.

Distinguish root cause, error, defect, and failure using examples. Distraction yields defect and invalid input (failure); time pressure identifies root cause, with missing exception handling for bonus calculations as defect.

Explore static and dynamic testing to reduce defects by reviewing requirements and design documents and executing tests with test data, while balancing effectiveness and efficiency in the software lifecycle.

Apply verification and validation to ensure the software meets requirements and user needs. Do the right thing in the right way, and avoid spaghetti code by producing readable, maintainable software.

Learn how software testing discovers defects and evaluates quality through activities, test objects, and artifacts. Explore static and dynamic testing, verification and validation, and how planning and tools shape testing.

Exemplify why testing is necessary by showing testers' involvement across the SDLC to detect defects. Highlight collaboration with developers and debunk myths about end users and static analysis.

Differentiate testing from debugging; dynamic testing reveals failures, while debugging reproduces, diagnoses, and fixes root causes, followed by confirmation and regression testing, with static testing under ISO 29119-1 finds defects.

Differentiates testing from debugging by showing that testing identifies failures and defects, while debugging finds root causes and fixes defects, with dynamic testing revealing failures and static testing identifying defects.

Explore how testing reduces risk and supports decision making by providing cost-effective defect detection, quality measures, and alignment with user needs throughout the software development lifecycle.

Understand how quality assurance focuses on process improvements and defect prevention to deliver high-quality software, while quality control uses testing to identify and fix defects.

Clarify the relation between testing and quality assurance, showing testing as a product-oriented form of quality control and QA as a preventive, process-oriented approach that uses test results as feedback.

Learn how test coverage, a key metric, measures how much of an application is exercised by tests, using traceability across requirements, design elements, and code.

Explore the seven testing principles, showing that testing reveals defects, exhaustive testing is impossible, and risk-driven, early static and dynamic testing with defect clustering guiding focus.

Explore the seven testing principles and apply equivalence partitioning and boundary value analysis to address exhaustive testing, tests wear out, and validation through acceptance testing.

Explore test conditions, test cases, test procedures, and test suites to verify requirements. Prioritize test cases, including high and low-level ones, and organize procedures into functional and performance suites.

Explore how testing is a process of activities beyond executing tests, covering objectives, design, setup, result recording, completeness, testware, traceability, roles, and ISO 29119-2.

Explore the seven main groups of test activities: planning, monitoring and control, analysis, design, implementation, execution, and completion, and how they are tailored to projects and iterations.

Define testing objectives, decide what and who tests, plan how to test with activities and exit criteria, and revisit plans based on monitoring and control activities before reporting to stakeholders.

Monitor progress against the test plan using metrics, then control testing with actions to address deviations. Evaluate exit criteria and report progress to decide whether to stop or continue testing.

Analyze test basis and documentation to identify testable features, define and prioritize test conditions, and establish bi-directional traceability to ensure full coverage and address risks.

Explore how test design turns test conditions into high-level test cases and sets, prioritizes them, identifies data, environment, and tools, and ensures bidirectional traceability across test basis, conditions, and procedures.

Develop and prioritize test procedures, create automated scripts, and assemble test suites to enable efficient test execution, schedule tests, build the environment, prepare data, and ensure traceability.

Execute test suites per the execution schedule, log outcomes, compare actual to expected results, and report defects for investigation; embrace continuous, peer, and pair testing to improve coverage and traceability.

Learn how test completion finalizes a project by verifying deliverables, closing defects, and archiving testware, while capturing lessons learned to improve future testing processes.

Master the test process by exploring the sequences of testing activities and the tasks within each activity, including boundary value analysis and equivalence partitioning in test design.

Apply the test process in context as an integral part of development activities funded by stakeholders to fulfill business needs, and adapt testing to factors: domain, risks, constraints, and tools.

Analyze the impact of context on the test process by examining factors such as stakeholders, team, business domain, technical factors, project constraints, organizational factors, software development lifecycle, and tools.

Explore testware and the full spectrum of test work products across planning, analysis, design, implementation, execution, and completion, with bidirectional traceability and configuration management guided by ISO 29119 standards.

Identify which testware items: test charter, coverage items, change requests, and execution schedules, align with each test activity from design through analysis, implementation, and completion.

Explore traceability from the test basis to test work products, using coverage criteria and KPIs to drive testing, assess requirements, test cases, risks, and auditability for stakeholders.

Explore how maintaining traceability supports testing by enabling impact analysis for selecting regression test cases, and measure progress by linking user requirements to test execution results.

Explore the ISTQB roles of test manager and tester. Identify planning, monitoring, and completion duties for managers, and analysis, design, implementation, and execution for testers.

Compare the different roles in testing, showing testers handle test environments and coverage reporting, while product owners, project managers, and architects contribute in Agile and project contexts.

Develop skills and good practices in testing. Combine knowledge of testing principles, methodologies, SDLC, domain, and tools with hands-on practice, attention to detail, problem solving, and teamwork across independence levels.

Discover the generic skills testers need, including testing knowledge, manual and automated testing, test case design and defect tracking, plus thorough review, communication, and analytical thinking.

Enhance your collaboration between testers and developers by mastering constructive communication, defect reporting, and team-based testing to improve software quality and reduce bugs.

Explore the generic skills testers need, including domain knowledge, critical thinking, and teamwork, and see exam-style examples showing how these skills apply to testing decisions and acceptance criteria.

Apply the whole team approach to build quality software with small, cross-functional teams. Collaborate with developers, testers, business representatives, and the product owner to plan, test, and own quality together.

Explore the whole team approach as an agile concept, highlighting collaboration between testers and business representatives to define test strategy and create suitable acceptance tests.

Explore independence of testing, from developers testing their own code to independent testers, and how independence shapes test management, collaboration, and detecting defects in agile and other lifecycles.

Explore the benefits and drawbacks of independence of testing, highlighting how independent testers question assumptions and verify interpretations of requirements, and note possible adversarial dynamics with developers.

Explore how testing integrates across the software development lifecycle, covering levels and types of testing, maintenance testing, early testing, and how sequential, iterative, and agile models shape test activities.

Describes a sequential development approach—the waterfall—in which requirements, design, coding, and testing occur in distinct stages, and earlier testing reduces the cost of fixing defects.

Explore iterative incremental development, including models that span incremental and iterative categories, and learn how frequent iterations, customer feedback, and automated testing across test levels drive delivering working software.

Explore agile as a philosophy and mindset that enables rapid change response, timeboxed, incremental delivery, and close business collaboration through self-organizing teams delivering customer value.

Value the agile manifesto's core principles: individuals and interactions over processes and tools, working software over documentation, customer collaboration over contract negotiation, and responding to change over following a plan.

Explore scrum, an agile framework, and learn how fixed-length sprints yield a potentially shippable increment, with the product backlog, sprint backlog, definition of done, timeboxing, daily scrums, and roles.

Explains how the software development lifecycle influences testing by selecting and adapting models to project goals, risks, and culture, shaping test scope, timing, and techniques across iterations and agile projects.

Explore how the chosen software development lifecycle affects testing timing, including the V-model and the roles of static testing, dynamic testing, test planning, and acceptance testing.

Link testing activities with every development phase, from requirements to project plans. Ensure testers participate early in discussions to define and refine requirements and design; review drafts of documents.

Recall testing practices that apply to all software development life cycles, align each development activity with a test activity, review drafts early, and base test design on a test basis.

Explore TDD, ATDD, and BDD as test-first approaches driving software with early testing, shift-left, and defined acceptance criteria.

Explore test-first development approaches, including ATDD, TDD, and BDD, and how acceptance criteria drive tests and early testing in a shift-left software development mindset.

Discover how DevOps reshapes testing through automation, continuous integration and deployment, enabling faster releases and availability of executable software, while tackling the cost of test automation setup and pipeline integration.

Shift-left testing moves testing earlier in the SDLC, using specification reviews, pre-code test case design, CI/CD, and static analysis to accelerate feedback and cut costs.

explain the shift-left approach by moving testing earlier in the software development lifecycle to test as early as possible, emphasizing early testing saves time and reduces the cost of quality.

Conduct frequent retrospectives across the SDLC to reflect on successes and areas for improvement, capture lessons learned, and drive process improvement, test effectiveness, quality, and team collaboration.

Explore how retrospectives drive process improvement by identifying weaknesses and turning them into a to-do list for continuous improvement. Clarify key questions about benefits and outcomes for development and testing.

Learn the five test levels from unit to acceptance, covering objectives, test basis, and environments, with a car-building analogy illustrating component, integration, system, and acceptance testing.

explain component testing, the lowest level of testing performed in isolation by developers to verify a unit's specification before integration, and use stubs, drivers, and test basis.

Understand component integration testing after unit testing, focusing on interactions and interfaces between modules, with incremental strategies, continuous integration, and automated regression testing to reduce risk.

perform end-to-end system testing to verify functional and non-functional behaviors, reduce risk, and build confidence by simulating production environments and identifying defects before release.

Validate the interactions and interfaces across systems, subsystems, external services, and microservices, and highlight common defects like data issues, interface mismatches, and security concerns.

Explore acceptance testing as a yes-or-no decision on deployment readiness, covering UAT, OAT, contractual and regulatory, and alpha/beta testing to validate complete, functioning system and readiness for customers.

Distinguish test levels in ISTQB foundation by mapping failures to acceptance testing, component testing, component integration testing, and system testing, and analyze typical system testing questions.

Explore test types and how testing objectives shape activities to assess a software system, including functional, non-functional, black-box, and white-box testing.

Functional testing validates the functions described in requirements, functional specification, or use cases, including implicitly required features. It covers functional completeness, correctness, and appropriateness through verification and validation.

Explore non-functional testing and its quality characteristics, including performance, compatibility, usability, maintainability, reliability, portability, and security, guided by ISO 25010 standards. Learn how non-functional requirements drive test design.

Explore black box testing as a specification-based approach that examines software behavior without internal code. Derive test cases from external documents to verify conformance to requirements and design specifications.

Explore white-box testing, using internal structure such as source code, architecture, and data flows to design targeted test cases that cover the system's underlying structure to an acceptable level.

See how test levels align with test types across a banking application, from functional to non-functional, white box, and change-related testing. Learn when to apply each type at earliest level.

Identify the difference between functional and non-functional testing, with examples such as performance testing, maintainability testing, and portability, and recognize that sorting correctness qualifies as functional testing.

Confirm defects are fixed by retesting with the same inputs and environment. Apply regression testing to detect side effects and automate regression suites early in agile and ci/cd.

Distinguish confirmation testing from regression testing using a practical scenario with test cases, retesting failed defects, and verifying unchanged code.

Perform maintenance testing on live systems to verify changes, guard sensitive data, detect regression, and assess impact analysis for corrective, adaptive, and performance improvements, including hotfixes.

Identify and assess triggers for maintenance in software, including enhancements, release-based corrective and emergency changes, environment upgrades, migrations, data conversion, patches for defects and vulnerabilities, retirement, archiving, and regression testing.

Use impact analysis to determine how changes affect the existing system and guide regression testing. Decide the appropriate tests and scope before making maintenance changes.

Explore maintenance testing and its triggers, including data migration when retirement occurs, along with modifications, upgrades, migration, or retirement.

Explore manual reviews and tool-based static analysis that assess code without execution. See how static testing supports agile teams, continuous integration, and security practices.

Static testing identifies defects early by examining source code and work products, complementing dynamic testing that reveals failures in executable software, often cheaper and improves maintainability.

Compare static and dynamic testing to explain early defect identification, differing defect types, and how reviewing requirements and coding standards helps prevent gaps before execution.

Explain which work products are examinable by static testing, including requirements, architecture, source code, and testware, using reviews and static analysis, with cautions about hard-to-interpret or executable-only items.

Explore static testing techniques, including reviews and static analysis, and identify which work products and defects are detectable without executing code.

Identify the benefits of static testing, including early defect detection, reduced fault severity, lower life-cycle costs, and improved design quality through clearer requirements and effective reviews.

Static testing highlights cost advantages in fixing defects, uncovers coding defects not found by dynamic testing, and detects gaps in requirements through reviews.

Plan early and involve stakeholders frequently to deliver, get feedback, spot issues upfront, prevent costly rework, and ensure changes to requirements are understood and implemented earlier, prioritizing high-value features.

Identify the benefits of early and frequent stakeholder feedback and learn how it avoids requirements misunderstandings, facilitates early communication of potential quality issues, and enables earlier implementation of requirement changes.

Learn to perform work product reviews across five activity groups: planning, review initiation, individual review, communication and analysis, and fixing, and apply entry and exit criteria, roles, and documented results.

Explore the review process by detailing formal reviews, the sequence of activities from planning to fixing and reporting, and how anomalies and access are managed.

Explore roles and responsibilities in formal reviews, including author, manager, moderator or facilitator, review leader, reviewers, and scribe, and how ISO/IEC 20246 guides logging defects, open points, and decisions.

Recall the principal roles in formal reviews: the manager decides what to review, and the review leader organizes the process; the moderator ensures meetings, the scribe records decisions.

Explore the four review types—informal, walkthrough, technical review, and inspection—and how formality, objectives, and the goal of finding defects, gaining understanding, and educating participants shape the process.

Compare four review types—informal, walkthrough, technical review, and inspection—and highlight their key characteristics. Walkthroughs include a meeting led by the author and focus on detecting defects with supporting metrics.

Explore success factors for reviews, including appropriate review types and techniques to meet defined objectives. Apply planning, chunking large documents, early feedback, and training to improve quality through measurable metrics.

Identify factors that contribute to a successful review and distinguish valid support from non-factors, such as dedicating time, splitting work into parts, maintaining respectful behavior, and acknowledging defects.

Master test design techniques to systematically identify test conditions, test data, and coverage items, creating a small yet sufficient set of test cases while balancing effectiveness and efficiency.

Examine black-box, white-box, and experience-based test techniques and how specification-based approaches, internal structure, and stakeholder experience shape test design.

Distinguish black-box, white-box, and experience-based test techniques and learn their test basis differences, emphasizing how tester knowledge drives experience-based testing versus black-box testing based on requirements, specifications, or models.

Master black-box test techniques by deriving test conditions and data from requirements, use cases, and user stories, and learn equivalence partitioning, boundary value analysis, decision table testing, state transition testing.

Learn equivalence partitioning: divide inputs into valid and invalid partitions that exhibit similar behavior, select one representative value from each, and test efficiently toward 100% coverage.

Master equivalence partitioning to derive minimal, representative test cases across scenarios such as apartment search, car wash discounts, pin validators, and cinema ticket pricing.

Boundary value analysis identifies boundary edges in input partitions and tests two-point or three-point values at and near those boundaries, illustrated by employee age and bank fee examples.

Explore boundary value analysis to derive effective test cases, define partitions and boundaries, and apply two- and three-value BVAs across real-world scenarios like grading systems, password length, and temperature controls.

Learn decision table testing, a combinatorial technique that records input conditions and actions to generate test cases for each decision rule and determine the minimum number of tests.

Explore decision table testing to derive test cases, analyze rules and coverage, identify contradictions, and select test data that maximize decision table coverage.

Explore state transition testing by analyzing states, transitions, triggers, and guards with diagrams and tables, highlighting coverage of all states, valid transitions, and all transitions in the embedded software industry.

Learn state transition testing to derive test cases and ensure valid transition coverage through exam-style questions and diagrams and tables.

Employ white-box test techniques that are structure-based and use information like code to guide tests and measure coverage. Use statement and branch testing at the component testing level, emphasizing coverage.

Explore statement testing and coverage concepts, showing how executable statements are exercised, how and/or conditions influence flow, and how 100% statement coverage is achieved in practice.

Explore statement testing and 100% statement coverage, clarifying that executing every statement does not ensure defect-free code or full branch and path coverage.

Demonstrates branch testing, a white-box technique that tests every branch of an if statement in the control flow graph, including true and false outcomes, and contrasts branch with statement coverage.

Master branch testing concepts, including 100% branch coverage, its link to statement and decision coverage, the distinction from decision table testing, and the role of control flow graph edges.

Explain the value of white-box testing, including its use on code, coverage metrics, static testing, and identifying gaps in requirements.

Learn experience-based test techniques that derive test cases from tester and user intuition, including error guessing, exploratory testing, and checklist-based testing, often combined with black-box and white-box approaches for coverage.

Learn how error guessing uses tester experience with past defects to predict likely developer mistakes, and differentiate it from user-focused or rapid task duplication approaches, including fault attacks.

Explore exploratory testing, where tester experience drives testing without test cases. Use session-based testing with a time box and test charter to guide objectives, log results, and decide next steps.

Learn to apply exploratory testing when time is short and requirements are unclear. Leverage domain knowledge to design and execute tests on the fly.

Design, implement, and execute checklist-based testing to cover test conditions and achieve systematic coverage; apply generic and specialized checklists for functional and non-functional testing, including image uploading.

Explore checklist-based testing as a test technique using a list of test conditions; high-level checklists can yield varied test values, increasing coverage, with examples like clear error messages.

Collaborate to prevent defects by applying collaboration-based test approaches, using collaborative user story writing, acceptance criteria, and ATDD in line with the ISTQB agile syllabus.

Collaborate to capture user stories from developers, testers, and business representatives, writing value-driven, small, testable stories with clear acceptance criteria.

Collaborate with business representatives, developers, and testers to define acceptance criteria that scope a user story, specify test conditions, and support given-when-then style scenarios.

Classify options for writing acceptance criteria using the given/when/then format, distinguish scenario-oriented from rule-oriented approaches, and apply best practices for documenting acceptance criteria in software testing.

Master ATDD as a test-first approach uses specification workshops to create manual or automated tests from acceptance criteria, covering positive and negative scenarios and non-functional attributes.

Learn how ATDD derives test cases from user stories and acceptance criteria, with examples including editor login workflows and price-range search filters.

Learn how test strategy, test policy, and test approach shape testing, and plan a project by detailing how to implement the chosen approach for that release.

Define and communicate a comprehensive test plan that outlines objectives, scope, resources, responsibilities, risks, and schedules across test levels, enabling tracking, change management, and stakeholder alignment.

Exemplify the purpose and content of a test plan by clarifying test levels and exit criteria, and how the plan guides testing decisions, including 100% branch coverage for critical components.

Compare agile planning with traditional planning, emphasizing iterative releases and short iterations guided by product vision and backlog refinement to manage uncertainty and risk.

Testers contribute to release planning by refining the product backlog, defining clear acceptance criteria, and shaping the test approach and plan for both release and iteration planning.

Recognize how testers add value to iteration and release planning by participating in detailed risk identification and risk assessment of user stories, leveraging testers' knowledge as essential inputs.

Define entry criteria, or definition of ready, to start testing with clear preconditions, and define exit criteria, or definition of done, to declare completion by coverage and quality goals.

Explore how entry criteria determine when testing can start and exit criteria justify when to stop, illustrating that exit criteria of one stage become entry criteria for the next.

Learn estimation techniques for software projects using metric-based and expert-based approaches, including ratios, extrapolation, wideband delphi, planning poker, and three-point estimates with PERT.

Learn estimation techniques to calculate test effort, including three-point estimates, planning poker decisions, ratio-based planning from historical data, and extrapolation for iterative sprints.

Learn to prioritize test cases, assemble test procedures into suites, and schedule tests using risk-based, coverage-based, and requirements-based strategies, while managing dependencies and regression and confirmation tests.

Master the art of test case prioritization by analyzing dependencies and priorities in mobile and web scenarios, using traceability and additional coverage techniques to determine optimal execution order.

Explore the test pyramid, from unit and integration tests to end-to-end checks, emphasizing granularity, isolation, and faster feedback to detect defects early and improve cost efficiency.

Recall the test pyramid concepts, focusing on automation levels and granularity across unit, component, system, and acceptance testing. Compare GUI-based and API-based tools at different test levels.

Discover Testing Quadrants in agile development, mapping unit, system, user acceptance, and operational acceptance tests to technology-facing and business-facing goals, with manual, automated, or hybrid approaches for dynamic testing.

Explore the testing quadrants, mapping each quadrant to tech or business facing test levels and types, and learn how they aid stakeholder understanding and team collaboration.

Explore how risk guides testing strategies by weighing internal and external factors to decide when to test and how much effort to invest, improving product quality and stakeholder confidence.

Define risk as the possibility of a future negative event, based on likelihood and impact. Use risk-based testing to mitigate risks and prioritize testing where threats are greatest.

Identify risk level by applying risk likelihood and risk impact, noting that these factors are independent; calculate risk impact from given risk level and likelihood in practice.

Differentiate product risks from project risks by classifying risks to the software versus risks to the development process, with examples across quality characteristics such as usability and security.

Distinguish project risks from product risks by when they could occur: during development or while using the software, with examples like scope creep and response time.

Lead risk identification and risk assessment using techniques like brainstorming, interviews, workshops, templates, and past experience; quantify risk with likelihood and impact, prioritize testing scope to mitigate high-risk areas.

Product risk analysis influences the thoroughness and scope of testing by guiding the testing rigor and scheduling early performance efficiency testing in the software development lifecycle.

Apply product risk control by mitigating and monitoring risks with a risk-based testing approach, selecting techniques, prioritizing testing, and implementing actions like avoid, mitigate, transfer, accept, and contingency planning.

Examine measures in response to analyzed product risks, focusing on risk mitigation through performance testing and alpha/beta testing to reduce likelihood and impact.

Discover how test monitoring provides feedback and visibility on test activities, how test control guides corrective actions when plans diverge, and how test completion consolidates results across projects.

Explore how test metrics measure progress, quality, and effectiveness, and learn key metrics for test progress, defects, risk, coverage, and cost to guide testing decisions.

Recall metrics used for testing to report the test object's quality, including defect density and defects found, and distinguish product quality metrics like mean time to failure.

Explain the purpose, content, and audience of test reports, including test progress reports and test completion reports, to stakeholders, guiding testing plans and risk management.

Summarize the purposes, content, and audiences for test reports, and explain how test progress reports inform business representatives and support test monitoring, control, and completion.

Communicate testing status to stakeholders using tailored methods that fit each context, balancing detailed metrics and high-level views with agile or waterfall strategies, regulatory needs, and team dynamics.

Explain how to communicate the status of testing in agile DevOps, using burn down charts to show work left and dashboards to share ongoing test progress.

Maintain integrity of configuration items, including documents, components, and testware, by tracking versions and changes to ensure traceable references in test planning and documentation, supported by an automated DevOps pipeline.

Learn how configuration management supports testing by tracking versions of test scripts and environment libraries, stubs, and drivers, ensuring traceability, and managing changes across test environments.

log and track defects from recognition to closure using a standardized defect reporting process that classifies issues and supports continuous improvement.

Learn how to prepare a defect report by identifying missing elements such as test environment and test item, and describe reproduction, expected vs actual results, priority, and severity.

Explore how test tools support management, static testing, design and implementation, execution and coverage, and non-functional testing, plus DevOps and collaboration tools, with insights on benefits, risks, and tool selection.

Explore how different types of test tools support testing, from data preparation in the test implementation stage to test execution, and from static testing to DevOps and collaboration tools.

Explore the benefits and risks of test automation and test execution tools, including reduced repetitive work, greater consistency, objective coverage, faster feedback, and realistic planning.

Identify the benefits and risks of test automation, examine example exam questions, and learn to distinguish when automation helps or poses risk in practical testing.