ISTQB Foundation Level (CTFL)-Complete Training [2024]

Explore fundamentals of testing by distinguishing static and dynamic testing, defining testing objectives such as finding defects and reducing risk, and clarifying the difference between testing and debugging.

Discover how testing contributes to success by applying appropriate techniques at the right level and by involving testers in requirement reviews, QA and QC, and root-cause analysis to prevent defects.

Adopt the seven testing principles: testing shows presence of defect, exhaustive testing is impossible, early testing saves time, defect clustering, pesticide paradox, context dependent testing, and absence of error fallacy.

Explore desk work products across the testing life cycle, from test planning and design through traceability matrices, reports, and final testing documents.

Map test requirements to test cases with the traceability matrix to track fulfillment, analyze change impact, enable auditing for IT governance, and report product quality and project progress to stakeholders.

Explore the psychology of testing, including confirmation bias, how conflicts arise between testers and developers, and how collaboration, clear communication, and a common goal improve product quality.

Learn how testing spans the software life cycle, from SDLC and test levels to maintenance testing, and how the v-model extends waterfall with parallel verification and validation.

Explore the ISTQB foundation test levels, from component (unit) testing to integration, system, and acceptance testing, including alpha and beta practices.

Explore static and dynamic testing in ISTQB foundation level, distinguishing verification from validation, and learn functional and non-functional testing, white-box versus black-box techniques, and retesting and regression strategies.

Master static testing basics, review processes, roles, and documents to catch defects early. Compare static and dynamic testing, and learn how reviews of specs and design reduce defects and cost.

Explore the review life cycle from planning to fixing and reporting, including initiation of the review, individual review, issue communication, and exit criteria, with defects, roles, and defect reports.

Identify and define the roles in a formal review, including author, manager, facilitator, review leader, reviewers, and scribe, and describe each role's responsibilities for defects, planning, and documentation.

Identify the success factors for reviews, including clear objectives, review types, and effective defect detection. Ensure organizational support, up-to-date checklists, diverse team skills, preparation time, and a culture of trust.

Explore how static testing and static analysis, along with reviews, improve defect management and early defect detection, reduce missed requirements, and enhance tester–developer communication through planned reviews and walk-throughs.

Summarizes test design techniques across black box, white box, and gray box testing, focusing on input–output validation, code structure, test conditions, test data, and coverage.

Apply equivalence partitioning by grouping inputs into equivalence classes and testing one value from each class to verify outputs. Group ranges like 1-17, 18-65, and 66 and above for testing.

Apply boundary value analysis to test boundaries where outputs change, using valid and invalid boundary values around lower and upper boundaries, as demonstrated with age input 18–30.

Apply the decision table testing technique to capture conditions and actions in a tabular form, using true/false cases for Citibank card members and room types to derive upgrade rules.

Use case testing documents an actor and a system to map process flow, not for unit testing, enabling integration and acceptance testing and uncovering defects in data flow and interactions.

Explore white box testing techniques, including statement coverage and decision (branch) testing, which examine code statements and if/else decisions, with 100% decision coverage implying 100% statement coverage.

Explain statement coverage by counting the minimum paths from start to end that cover all code nodes, including statements and conditions, using A to B examples and if/else diagrams.

Learn decision coverage by counting paths that cover all branches from start to end, using ifs count plus one for nested decisions and always two paths for unnested cases.

Explore the experience based testing technique, where tester intuition and past application experience uncover hidden bugs not found by formal testing, when specs are unclear or time is tight.

Explore error guessing, an experience-based testing technique that anticipates defects by inputs likely to break the app, using fault attack concepts and past failure data.

Create a complete list of test items and explore or update existing checklists to design test scenarios and test cases. Enable guideline-driven, high-level testing that improves coverage and consistency.

Learn how test organization defines roles - independent testers, test managers, and testers - and how independence affects defect detection, communication, and defect management in software testing.

Master test planning and estimation by defining scope, risk, objectives, entry and exit criteria, and by using matrix-based and expert-based estimation with scheduling and test suites.

Define and apply test monitoring and controlling using metrics to track test progress, coverage, risk, and exit criteria, and adjust plans through test reports.

Learn how configuration management maintains integrity between testing documents and products, with unique IDs, version control, change tracking, and the traceability matrix across versions.

Manage defects through the complete life cycle from new to close, including defect reports with severity and priority, assignment, verification, retesting, and change history.

Classify testing tools by purpose, covering test management, defect management, static testing, design and data tools, model-based and BDD/TDD approaches, and performance and specialization testing tools.

Automation tools reduce repetitive manual work, enable regression testing with diverse data sets, and provide consistent coverage and reports, but risks include underestimated setup costs and vendor interoperability concerns.

Explore data driven and key driven testing for test execution tools, using data inputs or keyword scripts, and how test management tools link to spreadsheets for traceability to requirements.

Explore key principles for introducing a test tool in an organization, including pilot project, phased rollouts, standardization, and cost monitoring, with insights on keyword-driven tools and test management.