CTFL-v4 Fundamentals of Testing Practice Question
Which of the following best describes the 'Early Testing' principle in the context of the software development lifecycle?
⚠ Common exam trap
Candidates frequently confuse early testing with 'early automation' or 'automated unit testing', failing to realize it primarily refers to reviewing requirements and design documents before implementation begins.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Test activities should begin during the requirements and design phases.
Early testing involves starting test activities as early as possible, such as reviewing requirements or design documents. This is crucial because it allows for the early detection and correction of defects, which are significantly cheaper to fix in these stages than during the implementation or release phases. It promotes proactive quality assurance and reduces the overall cost and risk of the project by preventing defects from propagating into downstream development activities.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Testing should start only after the code is fully compiled.
Why it's wrong here
Starting testing only after code compilation ignores the benefits of static testing. By waiting until the code exists, organizations miss the opportunity to find requirement or design defects early, leading to higher rework costs and delayed project timelines, which contradicts the core principle of early testing.
- ✓
Test activities should begin during the requirements and design phases.
Why this is correct
Early testing emphasizes that testers should be involved in reviewing requirements and design documents before coding begins. This allows for the identification of inconsistencies, ambiguities, and errors at the earliest possible stage, which significantly reduces the cost and effort required to fix these defects later.
- ✗
Testing must be completed before the development phase begins.
Why it's wrong here
Testing is an iterative process that runs alongside development. It is logically impossible to complete all testing before development starts, as the software must exist to be tested. The principle of early testing suggests starting as early as possible, not completing the entire testing cycle prematurely.
- ✗
Early testing is only applicable in Waterfall development models.
Why it's wrong here
Early testing is a universal principle applicable to all software development models, including Agile and DevOps. In Agile, early testing is achieved through activities like sprint planning reviews and story grooming, which ensure that quality concerns are addressed long before any actual code is written.
Visual reference
About these practice questions
One of 144 original CTFL-v4 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official ISTQB exam blueprint
This CTFL-v4 practice question is part of Courseiva's free ISTQB certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CTFL-v4 exam.