Fundamentals of Testing

Chapter 1 in the CTFL exam

Exam questions

8 / 40

Share of exam

20%

Highest K-level

K2

Glossary terms

30

Chapter 1 tops out at K2 — you are asked to explain and compare concepts, never to apply a technique. Questions are definitional and comparative.

What this chapter covers

Chapter 1 establishes the vocabulary the rest of the syllabus depends on. It is the third-largest slice of the exam at 8 of 40 questions, behind only Test Analysis and Design and Managing the Test Activities, and almost every question is answerable from precise definitions rather than judgement.

The chapter opens by separating testing from debugging. Testing finds failures; debugging locates and fixes the defect that caused them. The exam returns to this distinction repeatedly, usually by describing an activity and asking which one it is. It then builds the error → defect → failure chain: a person makes an error (mistake), which introduces a defect (fault) in the work product, which may cause a failure when the code executes. Not every defect produces a failure, and failures can also arise from environmental conditions with no defect present at all.

Test objectives cover evaluating work products, triggering failures, ensuring required coverage, reducing risk, providing information for decision-making, building confidence, and complying with contractual or regulatory requirements. Testing's contribution to success is framed in terms of defect prevention and early feedback, not merely defect detection.

The seven testing principles are heavily examined. Testing shows the presence of defects, not their absence; exhaustive testing is impossible; early testing saves time and money; defects cluster together; tests wear out; testing is context dependent; and the absence-of-defects fallacy — a system can be defect-free against its specification and still fail to meet user needs.

Section 1.4 introduces the test activities and tasks that structure the whole discipline: planning, monitoring and control, analysis, design, implementation, execution, and completion. It also defines testware — the work products produced by those activities — and traceability between the test basis and testware, which is what makes coverage measurable and impact analysis possible.

The chapter closes on skills and independence. A whole-team approach means quality is everyone's responsibility, not the tester's alone. Independence of testing exists on a spectrum, from developers testing their own code through to testing by an external organisation, with increasing objectivity traded against increasing distance from the work.

CTFL v4.0 syllabus outline

1. 1.1 What is Testing?

   • Test Objectives
   • Testing and Debugging

2. 1.2 Why is Testing Necessary?

   • Testing's Contributions to Success
   • Testing and Quality Assurance (QA)
   • Errors, Defects, Failures, and Root Causes

3. 1.3 Testing Principles

4. 1.4 Test Activities, Testware and Test Roles

   • Test Activities and Tasks
   • Test Process in Context
   • Testware
   • Traceability between the Test Basis and Testware
   • Roles in Testing

5. 1.5 Essential Skills and Good Practices in Testing

   • Generic Skills Required for Testing
   • Whole Team Approach
   • Independence of Testing

Highest-value terms in this chapter

Start here if you are short on time.

• defect
• failure
• error
• root cause
• quality assurance
• testability
• test objective
• independence of testing

Common exam traps

• ⚠️Confusing error, defect, and failure — the exam deliberately describes one and offers the others as distractors.
• ⚠️Reading 'testing shows the presence of defects' as 'testing proves software works'. It proves the opposite direction only.
• ⚠️Assuming more independence is always better; the syllabus presents it as a trade-off, not a ranking.
• ⚠️Treating quality assurance and testing as synonyms. QA is process-oriented; testing is product-oriented.