ISTQB Foundation Level 4.0 (NEW SYLLABUS) + Sample Questions

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.