ISTQB-BCS Certified Tester Foundation Level 

Start the course

describe why software testing is necessary

describe what software testing involves

describe how to meet a test objective and use defects to plan tests effectively

describe the first three general principles of software testing relating to presence of defects, impossibility of exhaustive testing, and error of confusing absence of errors with product fit

describe the last four applied software testing principles relating to early testing, defect clustering, pesticide paradox, and context dependency

describe test planning and control activities

describe test analysis and design activities

describe test implementation and execution activities

describe evaluation of exit criteria and test closure activities

describe the psychological considerations and levels of independence related to software testing

describe the importance of good communication for software testing tasks

describe the code of ethics related to software testing

describe the types of tests associated with the V-model

describe the types of tests associated with iterative-incremental models, including rapid application development (RAD)

describe component testing

describe integration testing

describe system testing

describe acceptance testing

describe the functional software testing type

describe the nonfunctional software testing type

describe the structural testing type

describe change-based testing, including regression testing

describe maintenance testing

identify an appropriate software testing strategy

start the course

distinguish between static and dynamic testing and outline the importance of static techniques for assessing software products

describe the activities in a formal review

describe the roles and responsibilities associated with formal reviews

describe different types of review - walkthroughs, technical reviews, and inspections

describe the success factors for reviews

describe the objective of static analysis in assessing software products

outline the steps in the test development process and how these are documented

describe the different types of test design techniques for dynamic testing

describe the black-box technique equivalence partitioning (EP)

describe the black-box technique boundary analysis

describe how to use decision tables for black-box test design

describe the black-box technique state transition testing

describe the black-box technique use case testing

describe how white-box techniques can be used to measure test coverage and design tests

describe how statement coverage is calculated and test design is based on the results

describe how decision coverage is calculated and test design is based on the results

describe other structure-based techniques, including various forms of condition coverage

describe the experience-based techniques error-guessing and exploratory testing and how they work with specification-based techniques

list the factors involved in choosing a test technique

practice identifying an appropriate software testing technique and the considerations for its implementation

Start the course

describe the benefits of independent testers and the way in which complex tests can be organized to use them

describe the activities associated with the test leader and tester

describe the activities associated with planning a test for a system and typical entry and exit criteria

describe two approaches to estimation of test effort ? expert-based and metrics-based

describe how the test strategy is implemented with a test approach, and describe typical approaches

describe how test progress can be monitored and define common metrics

describe the activities involved in test reporting, including metrics and documentation used

define what test control is and

describe examples of test control actions

define configuration management and its importance in the context of software testing

define project risks in relation to testing as a project activity and

describe types of risk, including organizational factors and technical and supplier issues

describe how product risks can be identified to develop risk-based testing

define incidents in relation to software testing and

describe how they should be managed

describe the testing activities that tools can be used to support and their aim

describe how tools can be classified according to the activities they support, and define intrusive tools

describe the uses of test management tools

describe how tools are used to support static testing

describe how tools are used to support test specification

describe how tools are used to support test execution and logging

describe how tools are used to support test performance, monitoring, and specific testing needs

describe the potential benefits and risks associated with using testing tools

describe the special considerations required for some tool types, including test execution tools, static analysis tools, and test management tools

describe the considerations relating to introduction of testing tools into an organization

practice identification of planning and management considerations and identify considerations for using tools for testing