ISTQB Foundation Level 4.0 (NEW SYLLABUS) + Sample Questions

Learn what testing is and why it matters for product quality. Discover the tester's role in reviews, defects, risk reduction, and regulatory compliance.

Understand why testing is essential from requirements review through regression, and learn the difference between QA and QC, static and dynamic testing, and defects, failures, and root causes.

Master seven testing principles: presence of defects, exhaustive testing is impossible, early testing saves time and money, defects cluster, tests wear out, context dependent, absence of defects is a fallacy.

Explore test activities and the test process, including planning, analysis, design, implementation, execution, and completion, and learn how context, stakeholders, and factors shape testing.

Identify the core testing deliverables from planning to completion. Understand test plans, risk registers, progress reports, defect reports, and traceability, and distinguish test management from test engineers.

Acquire essential testing skills and good practices, communicate findings clearly to stakeholders, and balance constructive defect reporting with neutral language to preserve collaboration and independence.

Adopt the whole team approach to enable co-location, cross-functional collaboration, and shared quality ownership, while blending independence levels from author testing to outsourcing for effective testing and acceptance test.

Explore sample questions from chapter 1 of the ISTQB foundation level 4.0 (new syllabus), focusing on valid test objectives, pesticide paradox, test wear out, risk identification, and regulatory requirements.

Explore how the software development life cycle influences testing across waterfall, v-model, and agile. Learn good testing practices, role distribution, and the shift-left approach with static testing.

Discover TDD, BDD, and ATDD as agile testing drivers, with tests written before development and a shift-left approach, and explore DevOps testing, CI/CD, and automation.

Shift left approach and retrospective drive early defect detection and process improvement across the sdlc, using specification reviews, test-first development, ci/cd, and early non-functional testing.

Explore test levels and test types, focusing on component testing. See how developers use white box testing in development environments with test harnesses and mocks to validate independent components.

Explore component integration testing, focusing on interfaces between two or more components within a module, using bottom up, top down, or big bang strategies.

System testing examines the entire product's behavior, combining functional end-to-end testing with non-functional characteristics in a representative environment, often by an independent team, using simulations when needed.

Analyze system integration testing, focusing on interfaces and communications between multiple systems, including software–software and software–hardware integrations. Create near-real environments to validate end-to-end interactions across embedded and hardware components.

Explore acceptance testing as validation of business requirements by users, covering functional, operational, and regulatory checks, and distinguish alpha and beta testing for feedback in real and pre-prod environments.

Compare functional and non-functional testing, examining core functionalities and how quality characteristics—performance, security, usability, accessibility, portability—shape testing priorities across levels such as unit, integration, system, and acceptance.

Compare white box testing, a structure-based, code-level approach, with black box testing, a specification-based, external approach, and learn how both apply across all test levels.

Explore confirmation testing and regression testing as change related testing, focusing on defect fixes, fixed version re-testing, and impact analysis to scope regression across test levels and automation in CI/DevOps.

Explore maintenance testing, a post-release regression process for enhancements to live applications. Learn categories like corrective updates, upgrades, migrations, and retirement, plus impact analysis and risk-driven scope.

Explore sample questions from chapter 2 on testing throughout the SDLC, covering shift left, regression vs retesting, and how development models relate to testing activities.

Explore static testing basics by reviewing work products and using static analysis to detect anomalies early, improving quality, maintainability, and security through collaboration.

Compare static testing with dynamic testing, showing how static review finds documentation defects such as inconsistencies and ambiguities. Static analysis with root cause analysis reveals defects earlier and cheaper.

Understand the formal review process for work products, including planning, initiation, individual review, communication, fixing, and reporting, with roles like manager, author, moderator, scribe, reviewers, and leader.

Explore the four review types—from informal walkthrough to inspection, including technical review—highlighting factors for agile, waterfall, and regulatory contexts.

Identify clear objectives and measurable exit criteria to guide reviews. Balance management support and reviewer contribution, tailor review types, and provide timely feedback to drive a successful review process.

Explore sample questions on chapter 3 about static testing, including its benefits, early life-cycle focus, and review types like walkthroughs, with emphasis on static vs dynamic testing.

Discover how to reduce test cases without sacrificing coverage by applying black box, white box, and experience-based test techniques, including equivalence partition and boundary value analysis.

Learn equivalence partitioning, a black box test technique that divides inputs into partitions or ranges where values behave the same. Pick one test per partition, e.g., 1 to 15 inclusive.

Explore how to apply equivalence partition to tests with multiple inputs, minimize test cases, and ensure 100% coverage using concrete two- and three-input examples from the ISTQB foundation material.

Learn boundary value analysis as a black box testing technique, contrasting with equivalence partition, and apply two-point or three-point analyses to test valid and invalid boundaries with practical exam questions.

Explore decision table testing as a black box technique, crafting condition–action tables from requirements and applying truth table concepts to derive minimal test cases and outcomes.

Learn state transition testing, a black box testing technique using state transition diagrams to identify valid and invalid transitions and derive minimum test cases.

Explore white box test techniques, focusing on statement testing and statement coverage, defining the minimum tests for 100% coverage using simple code examples and nested conditions.

Explore branch testing and branch coverage in white box testing, learn to derive the minimum tests to cover all branches, and compare branch coverage with statement coverage.

Explore the value of white box test techniques, showing how code-level analysis detects defects when requirements are vague and complements black box testing with measured code coverage.

Explore error guessing, an experience-based test technique driven by tester intuition and domain knowledge to uncover defects after formal techniques, using fault attack for improved coverage and confidence.

Engage in exploratory testing as an experience-based, time-boxed technique that clarifies requirements. Create a test charter, conduct session-based testing, and debrief to guide tests and findings.

Use checklist based testing to design, implement, and execute high-level, question-based checklists that cover test conditions for static and dynamic testing, mapping to requirements and acceptance criteria to ensure coverage.

Collaborative user story writing unites business, development, and testing to craft, testable stories using the three cs (card, conversation, and confirmation) and invest principles—independent, negotiable, valuable, estimable, small, and testable.

Define acceptance criteria as the conditions that determine when a user story is done. Include persona, feature, and outcome, and use given-when-then or bullet lists for testability, UAT, and planning.

Learn acceptance test driven development as a collaborative, test-first approach where tests from acceptance criteria guide development, with manual or automated tests, created by customers, developers, and testers.

Explore experience-based test techniques and acceptance criteria documentation using given when then formats through sample questions from chapter 4 of the ISTQB foundation course.

Understand the purpose and content of a test plan, including entry and exit criteria, risks, resources, stakeholders, and life cycle considerations.

Explore testers' roles in release and sprint planning within agile and traditional models. Learn to define testable user stories, acceptance criteria, risk analysis, and test approach for releases and iterations.

Entry criteria define the preconditions to start a test activity, while exit criteria specify completion measures to declare it done, aligning with definition of ready and done in agile.

Apply matrix-based and expert-based estimation techniques to predict testing effort, time, and cost, using ratios, extrapolation, wideband Delphi, planning poker, and three-point estimates.

Explore how to prioritize test cases using risk-based, coverage-based, and requirement-based approaches, blend priorities with dependencies and blockers, and craft an effective test execution schedule.

Explore the test pyramid and four testing quadrants in agile development, outlining unit, integration, UI, and non-functional tests, their automation roles, and technology facing vs business facing perspectives.

Identify and assess risks early to drive risk-based testing, prioritize test activities by likelihood and impact, and distinguish project risks from product risks with ongoing mitigation and monitoring.

Conduct product risk analysis to identify and assess risks, categorize and prioritize them, and apply risk mitigation, risk control, and risk monitoring to reduce residual risk and guide testing activities.

Learn ISTQB foundation level test monitoring, test control, and test completion using matrices to measure progress, detect deviations, and guide corrective actions toward meeting exit criteria and milestones.

Learn how to prepare test progress and test completion reports for stakeholders, including content, audience, frequency, risks, defects, and practical communication via dashboards and templates.

Explore how configuration management uniquely identifies items, manages changes, controls versions, and maintains traceability across baselines and test items within testing and DevOps pipelines.

Master defect management fundamentals by outlining why to write defect reports, which fields to include, and how reports drive defect resolution, quality tracking, and process improvement in software testing.

Explore how testers contribute to iteration and release planning, identify and assess risks, and apply exit criteria with chapter 5 sample questions from the ISTQB Foundation Level course.

Explore tool support for testing and learn how management, static testing, test design and implementation, test execution and coverage, non-functional testing tools, DevOps, and collaboration tools support the test lifecycle.

Assess the benefits and risks of test tools and automation, including time savings, reduced human error, improved coverage, and key risk mitigation like cost, vendor dependency, and compliance.

Analyze chapter 6 test tools through sample questions, linking test data preparation to the test implementation phase and highlighting risks of under-resourcing testware in automation.