Certified Tester Foundation Level Syllabus

Certified Tester Foundation Level Syllabus

1. Certification Details

  • Document Version: 4.0.1
  • Published By: International Software Testing Qualifications Board (ISTQB®)
  • Copyright Notice:
    • 2024-09-15 © ISTQB® & various authors from previous updates (2005-2023)
    • Translation and adaptation authorized under licensing conditions for training providers.

2. Revision History

  • Latest Updates:
    • CTFL v4.0.1 – Errata (15.09.2024)
    • CTFL v4.0 – General release (21.04.2023)
    • CTFL v3.1.1 – Updates and copyright adjustments (01.07.2021)

3. Table of Contents

  1. Introduction

    • Purpose of the syllabus
    • Overview of the Certified Tester Foundation Level
    • Career pathways
    • Expected business outcomes
    • Learning objectives and cognitive levels
    • Examination details
    • Accreditation information
    • Standards handling
    • Keeping current with testing standards
    • Syllabus organization

  2. Fundamentals of Testing – 180 minutes

  3. Software Development Lifecycle and Testing – 130 minutes

  4. Static Testing – 80 minutes

  5. Test Design and Analysis – 390 minutes

  6. Managing Test Activities – 335 minutes

  7. Test Tools – 20 minutes

  8. References

  9. Appendices

  10. Index

4. Introduction

4.1 Purpose of this Syllabus

  • Serves as a foundation for the International Software Testing Qualification.

4.2 Overview of Certified Tester Foundation Level

  • Geared towards individuals in various roles including testers, managers, and developers.

4.3 Career Pathways

  • Levels from Foundation to Advanced, including specialized areas such as Agile Testing.

4.4 Expected Business Outcomes

  • FL-BO1 to FL-BO14:
    • Outcomes range from understanding testing principles to reporting progress effectively.

4.5 Learning Objectives and Cognitive Levels

  • Structured into three cognitive levels:
    • K1: Remember
    • K2: Understand
    • K3: Apply

4.6 Examination Details

  • Exam necessary for certification; all sections examinable except for introductory sections and appendices.

4.7 Accreditation Information

  • Training providers may obtain accreditation to offer courses based on this syllabus.

4.8 Standards Handling

  • Standards referenced but not directly examinable; they serve as guidelines.

4.9 Keeping Current with Testing Standards

  • Continuous updates on practices mentioned on the ISTQB® website.

4.10 Syllabus Organization

  • Six primary chapters detailing fundamental testing and management practices.

5. Fundamentals of Testing (180 minutes)

5.1 What is Testing?

  • Definition: Activities to discover defects and assess software quality within its operational environment.
    • Dynamic vs Static Testing:
      • Dynamic includes execution of software.
      • Static involves reviews and analysis without execution.
  • Common Misconceptions:
    • Testing is only execution-based (includes design and analysis).
    • Focus is solely on verification (also on validation).
5.1.1 Test Objectives:
  • Covering requirements evaluation, defect identification, risk reduction, compliance, stakeholder information provision.
5.1.2 Testing vs Debugging:
  • Testing identifies failures caused by defects, whereas debugging seeks to identify and fix those defects.

5.2 Importance of Testing

  • Supports achievement of quality controls and stakeholder satisfaction through early defect detection.
5.2.1 Testing Contributions to Success
  • Cost-effective defect detection contributing to overall quality and project management decisions.
5.2.2 Testing and Quality Assurance (QA)
  • Distinction between product-oriented testing and process-oriented QA efforts; both essential for project success.

5.3 Testing Principles

  1. Presence vs Absence of Defects: Testing indicates defects are present, not that none exist.
  2. Exhaustive Testing Impossibility: Testing cannot cover all scenarios.
  3. Early Testing Savings: Early removal of defects saves time and resources.
  4. Defect Clustering: Most defects arise from a small number of components.
  5. Test Wear Out: Repeated tests become less effective, necessitating new tests.
  6. Context-Sensitive Testing: The appropriate testing approach depends on specific contexts.
  7. Absence-of-Defects Fallacy: Verification doesn't guarantee the system meets user needs.

5.4 Test Activities, Testware, and Test Roles

  • Core Test Activities: include planning, monitoring, analysis, design, implementation, execution, and completion.
  • Testware: includes all documentation and tools used during testing.
  • Roles: important roles in testing include testers, managers, and developers depending on tasks and organizational structure.

5.5 Essential Skills and Good Practices in Testing

  • Skills include testing knowledge, attention to detail, analytical thinking, communication, and independence in testing.

6. Software Development Lifecycle and Testing (130 minutes)

6.1 Impact of SDLC on Testing

  • Different SDLC models demand adaptive testing approaches for effective quality assurance. Examples: Waterfall, Agile methodologies.

6.2 Good Testing Practices Across SDLCs

  • Maintain parallel testing activities corresponding with development tasks; adhere to early testing principles to enhance product quality.

6.3 Testing as a Driver

  • Implementing test-driven approaches encourages proactive defect identification and resolution throughout development phases.