ISTQB Foundation v2018 Course (ISTQB Officially Accredited )

Explore the waterfall model, a sequential approach in which testing follows coding, overruns shorten testing time and increase the cost and effort to rectify issues.

adopt a v-model that integrates testing with planning, allowing early verification of requirements and acceptance tests to reduce defect cost and speed up time to market.

Develop, build, test, and implement a working software piece in each iteration of the iterative-incremental model, where regression testing grows with complexity and automation helps manage it.

Explore the four test levels—component, integration, system, and acceptance—mapped to development activities in the v model, and identify objectives, test basis, objects, defects, harness requirements, and planning considerations.

Examine component testing, or unit testing, to verify individually testable modules in isolation using drivers or simulators, applying test-driven development and addressing functional and non-functional concerns such as memory leaks.

Plan incremental integration testing to validate interfaces between components and subsystems, guided by system architecture, ensuring module communication and early defect detection across cross-platform interfaces.

explore system testing as a whole-system evaluation against requirements, use cases, and risk analysis reports, using black box, white box, and independent test team approaches.

Assess acceptance testing by examining the test basis, including user and system requirements, use cases, business processes, risk analysis, and stakeholders, to establish confidence in the system for deployment readiness.

Explore functional and non-functional testing, including regression, confirmation and security testing, to verify behavior, fix defects, and measure coverage across test levels.

Explore maintenance testing, including regression testing, impact analysis, and risk-based test design techniques, with master test plans, release planning, and data migration considerations.

Static testing activities, such as reviews of specification documents and static analysis of code, occur on the downward side of V model, while dynamic testing verifies behavior when executed.

Apply equivalence partitioning and boundary value analysis to create efficient blackbox test cases, distinguishing valid vs. invalid outcomes and focusing on boundary values, with a preview of decision table testing.

Learn how to use decision table testing to cover multiple conditions and outcomes, including equivalence partitioning and boundary value analysis, illustrated by a car insurance fee example.

Learn state transition testing for machines and components, using state diagrams, starting states, events, and actions to validate correct transitions and identify invalid paths with zero and one switch coverage.

Explore how use cases model interactions between actors and systems, detailing preconditions, postconditions, basic paths, deviations, and risk-based testing to design robust acceptance tests.

Explore structure-based white box design techniques, including statement, decision, and branch coverage, and learn to model with control flow diagrams to derive minimal tests achieving full coverage.

Explore structure-based testing with complex examples, determine test cases for 100 percent statement and decision coverage, and distinguish statements from decisions in flow diagrams.

Experience-based test design techniques, such as error guessing and exploratory testing, rely on domain knowledge of the software and its environment to uncover defects in high-risk areas after structured testing.

Explore how test management aligns testing activities with product goals, detailing the roles of a test leader, testers, and experts, and outlining test strategy, planning, metrics, and independence levels.

Craft a comprehensive test plan detailing scope, approach, resources, and schedule of testing activities, plus which items and features are tested or not, and who handles each task.

Outline two estimation approaches for testing—metrics-based and expert-based—and highlight factors influencing estimates, including product characteristics, test basis, maturity, and resources.

Maintain the integrity of system products through the project and product lifecycle by applying configuration management, including version control, change management, and unique identification of test items and infrastructure.

Define and manage software incidents using a standard incident report with title, problem description, reproduction steps, outcomes, severity, priority, and environment; track status through closure to improve quality.

Identify and analyze risks by evaluating likelihood and impact with risk metrics and stakeholder input, then prioritize testing using risk matrix and techniques like boundary value analysis and statement coverage.

Identify two categories of test tools—administration tools and test automation tools—with non-functional tools for performance, load, capacity, penetration, and browser compatibility, plus regression capture and playback tools.