[2025] ISTQB Foundation Level (CTFL) v4.0.1 100% PASS Course

Explore testing as a process that uncovers defects, evaluates reliability and usability, and assesses whether software meets requirements and user needs, contrasting dynamic and static testing with verification and validation.

Explore seven fundamental principles of software testing, including showing defects exist, impossibility of exhaustive testing, early testing saves time, defects cluster together, tests lose effectiveness over time, and context-dependent testing.

Explore the seven core test activities—planning, monitoring and control, analysis, design, implementation, execution, and completion—and how they form an adaptable test process across projects and methodologies.

Explore how the test process adapts to context, influenced by stakeholders, team, business domain, architecture, constraints, and development life cycle, and why tailoring testing is essential.

Explore testware, the work products created during testing—from planning and risk registers to logs, defect reports, and lessons learned—emphasizing configuration management and traceability for reuse.

Explore how traceability links test basis and testware to map requirements, risks, and results, enabling coverage measurement, change impact analysis, and audit-ready reporting.

Explore two key ISTQB roles in testing: test management oversees planning, monitoring, and reporting, while testing focuses on design, execution, and defect logging. Responsibilities may be shared or distributed.

Develop essential testing skills for agile and DevOps contexts through knowledge, practice, and attitude, emphasizing curiosity, clarity, critical thinking, collaboration with developers, and including automation and domain knowledge.

Explore how the software development life cycle shapes testing, aligning planning, execution, and reporting with waterfall, V-model, iterative, and agile models.

Explore testing across all SDLC models, with unit, component, system, and acceptance testing, and embrace early test analysis, design, shift-left practices, and document reviews to build quality.

Explore how testing drives development by applying TDD, ATDD, and BDD to guide coding, emphasize early testing, collaboration, and reusable automated regression tests.

Explore how testing fits into DevOps through continuous integration and delivery with automated unit to system tests, enabling quick feedback, fewer defects, and manual testing for usability and edge cases.

Shift left moves testing earlier in the life cycle to catch defects early and reduce the cost of quality by reviewing requirements, writing tests before coding, and automating checks.

Retrospectives enable the whole testing team to reflect on what went well and what didn’t, identify actionable improvements to test cases, reviews, and coverage, and drive continuous improvement.

Explore the five test levels from component testing (unit testing) to acceptance, detailing objectives, scope, and integration patterns like top-down, bottom-up, and big bang.

Explore four main test types in ISTQB: functional, non-functional, black box, and white box, and learn how each evaluates different aspects of software quality.

Confirmation testing verifies that a defect has been fixed by re-running the failed tests, while regression testing checks for unintended side effects and defines the scope through impact analysis.

Perform maintenance testing on deployed software to validate post-deployment changes and prevent regressions. Use impact analysis to assess risk and scope across modifications, upgrades, migrations, and retirement.

Explore static testing, evaluating work products without execution to detect defects early and improve quality. Apply manual reviews and static analysis tools to ensure readability, completeness, correctness, testability, and consistency.

Explore static testing of readable, structured work products—requirements, source code, test plans, test cases, backlog items, test charters, UML diagrams, and process flows—before execution, and learn its time-saving, risk-reducing benefits.

Static testing detects defects early in the life cycle, even during requirements and design, at lower cost. It reveals issues dynamic testing may miss and strengthens quality through stakeholder collaboration.

Compare static testing and dynamic testing to show how static reviews detect gaps in requirements and design before execution, while dynamic testing reveals runtime crashes and performance issues.

Engage stakeholders early and frequently to review requirements, designs, and other work products, reducing costs by catching defects before coding and improving product quality through collaboration and shift-left practices.

Explore the ISSB review process activities for static testing, including planning, initiation, individual review, communication analysis, and fixing and reporting, to improve collaboration and reduce rework.

Define roles and responsibilities in reviews for static testing, clarifying how managers, authors, moderators, scribes, reviewers, and review leaders collaborate to improve quality.

Explore the four review types in static testing - informal reviews, walkthroughs, technical reviews, and inspections - and learn how context, formality, and roles shape their use for early feedback and quality assurance.

Define clear objectives and measurable exit criteria for reviews, select appropriate review types, and focus on improving the work product rather than judging participants.

Explore how test techniques guide test design, turning requirements and code into structured test cases for black box, white box, and experience-based approaches, including equivalence partitioning and boundary value analysis.

Explore equivalence partitioning, a black box test technique that reduces redundant tests and ensures coverage by selecting one value from each equivalence class across valid and invalid inputs.

Learn boundary value analysis, a core test design technique that targets the edges of equivalence partitions using two-value and three-value BVA to reveal boundary defects.

State transition testing uses state diagrams and state tables to model behavior, design tests for valid and invalid transitions, and apply all states, valid transitions, and all transitions coverage.

Explore white-box test techniques, or structural testing, that examine code structure, loops, and decisions, using statement and branch coverage to measure what's actually tested and reveal untested paths.

Explore white box testing with statement testing and statement coverage, defining executable statements, achieving coverage metrics, and recognizing 100% statement coverage limits in unit testing through practical examples.

Master branch testing and branch coverage as a white box technique, ensuring every decision outcome is tested and both true and false paths are exercised to improve test effectiveness.

Discover the value of white box testing, measuring coverage with statement and branch metrics to reveal untested paths, detect logic errors, and improve test efficiency.

Explore error guessing, an experience-based test technique that uses tester knowledge, past experience, and fault attacks to reveal defects and failures not covered by formal design.

Explore exploratory testing as an experience-based technique where test design, execution, and analysis happen together; use timeboxing and a test charter to adapt to risks and unclear requirements.

Explore checklist-based testing, an experience-based technique using test conditions, quality attributes, and defect indicators to guide design, execution, and continuous improvement in agile, exploratory, and regression contexts.

Collaborate to write clear, valuable, and testable user stories using the three Cs: card, conversation, and confirmation, define acceptance criteria, and apply the Invest model during backlog refinement.

Define acceptance criteria for user stories through collaboration, detailing success conditions and test scenarios to guide testing, acceptance testing, planning, and verification.

Explore acceptance test driven development as a collaborative approach. Define acceptance criteria and test cases in natural language, aligning with user story and including positive, negative, and non-functional tests.

Craft a test plan that defines objectives, resources, and processes, serves as a roadmap for testing aligned with policy and strategy, and addresses risks, constraints, and communication.

Explore how testers contribute to release and iteration planning by shaping testable user stories, acceptance criteria, risk analysis, and test effort estimates, and by integrating testing tasks into each iteration.

Define entry criteria and exit criteria in test planning, outlining preconditions, resources, test basis, and quality gates to start testing and to declare it complete.

Explore estimation techniques for testing, including ratio-based estimates from historical data, extrapolation from early iterations, and expert-based methods like wideband Delphi, planning poker, and three-point estimation.

Explore test case prioritization to optimize test execution order using risk-based, coverage-based, and requirements-based strategies, while considering dependencies and resource constraints for effective testing.

Discover the test pyramid, with unit tests at the base, integration tests in the middle, and UI tests at the top, to drive fast feedback and balanced test automation.

Learn the testing quadrants model, grouping tests by technology facing versus business facing and development versus critique, covering component tests through non-functional tests for a balanced agile strategy.

Explore how risk management guides testing by identifying and assessing risks, then mitigating and monitoring them to improve product quality and stakeholder confidence through risk based testing.

Define risk as an event that may harm software, causing delay or cost. Use likelihood and impact to determine risk level and guide risk-based testing across project and product risks.

Identify and distinguish project risks and product risks to tailor the test strategy, prioritize test coverage, and mitigate issues that affect schedule, budget, quality, and user experience.

Identify risks early and assess them through risk identification and risk assessment, guiding testing scope, levels, techniques, and effort.

Manage product risks through risk mitigation and risk monitoring, aligning the test strategy to reduce likelihood and impact. Apply testing techniques, coverage, and dynamic testing to support risk responses.

Master test monitoring to track progress and exit criteria, apply test control directives to adjust priorities and schedules, and complete the test cycle with consolidated results and lessons learned.

Explore how testing metrics drive project control and decision making in software testing. Track project progress, test progress, product quality, defects, risk, coverage, and cost to guide improvements.

Explore the purpose, content, and audience of test progress and test completion reports, learn how real-time metrics, impediments, risks, and planned activities guide testing decisions.

Communicate testing status using verbal updates, dashboards, emails, chat, online documentation, and formal reports, tailored to stakeholders and team contexts for clear, timely visibility.

Learn configuration management (CM) for testing, identifying and versioning items like test plans, cases, scripts, and environments, establishing baselines and formal change control for traceable, repeatable results in DevOps pipelines.

Execute defect management with a structured workflow for logging, analyzing, triaging, and closing defects. Use well-documented defect reports to improve product quality and process.

Explore how test management, static testing, and test execution tools streamline planning, design, and coverage across agile, DevOps, and traditional processes.

Explore the benefits of test automation, including time savings, regression testing, error reduction, objectivity, dashboards, and faster feedback, while recognizing risks like unrealistic expectations, poor planning, and vendor dependencies.