Master key concepts with interactive flashcards
What is the difference between an error, a defect, and a failure?
Click to reveal answer
An **error** is a human mistake (e.g., a developer misunderstands a requirement). A **defect** (fault/bug) is the flaw introduced into the code or document as a result. A **failure** occurs when the defect is executed and the system produces an incorrect result. Error → Defect → Failure.
Click to show question
ISTQB CTFL is a ISTQB certification. These facts come from the current exam guide and are the numbers to plan around.
| Domain | Weight | What to focus on |
|---|---|---|
| Testing Throughout the Software Development Lifecycle | 20% | Software development lifecycle models, Test levels, Test types |
| Test Analysis and Design | 20% | Test techniques overview, Equivalence partitioning, Boundary value analysis |
| Managing the Test Activities | 16% | Test planning, Test monitoring and control, Entry and exit criteria |
| Test Tools | 16% | Tool support for testing, Benefits and risks of automation, Tool selection considerations |
| Fundamentals of Testing | 15% | Why testing is necessary, Test objectives, Testing principles |
| Static Testing | 13% | Static testing basics, Review process, Review roles and responsibilities |
Yes. You can start CTFL practice and flashcards free without creating an account. A free account keeps your progress, and the full bank (300+ questions) unlocks with a subscription.
They cover all 6 domains of the CTFL exam: Testing Throughout the Software Development Lifecycle (20%), Test Analysis and Design (20%), Managing the Test Activities (16%), Test Tools (16%), Fundamentals of Testing (15%), Static Testing (13%). Each section is weighted in the same proportion as the real exam, so nothing high-value is buried.
The CTFL exam has approximately 40 questions in 60 minutes, with a passing score of 65%. Use the practice questions to confirm you are consistently above that line before booking the real exam.
Study in short, spaced sessions: a card you have not seen for two days is worth more than a card you reread immediately. Filter by Testing Throughout the Software Development Lifecycle first, then mix domains so you practise identifying the topic before recalling the definition.
They are the recall half of preparation. Pair the cards with practice questions and at least one timed practice exam — candidates who only review cards usually recognise terms but miss scenario questions.