CTFL-v4 Fundamentals of Testing Practice Question
Which of the following is a key characteristic of the 'whole-team' approach to testing in Agile environments?
⚠ Common exam trap
Candidates often believe the whole-team approach means everyone performs the same tasks, rather than understanding it as a shared responsibility for quality outcomes across different roles.
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
✓
Testing is considered a shared responsibility across the entire team.
In a whole-team approach, quality is a shared responsibility, not just the tester's job. Developers, testers, and business analysts collaborate throughout the process, from planning to deployment. This reduces silos, improves communication, and ensures that quality is considered at every step. By involving everyone, the team leverages diverse perspectives, leading to faster identification of issues and a more robust, user-focused end product that satisfies all stakeholder expectations effectively.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Testers work in isolation to ensure objective and unbiased results.
Why it's wrong here
Working in isolation creates silos and delays feedback. Modern testing practices emphasize collaboration and early involvement. Isolation prevents testers from understanding the developers' logic or the business requirements, often leading to misunderstandings and delayed bug detection, which contradicts the core values of Agile and modern quality assurance methodologies.
- ✓
Testing is considered a shared responsibility across the entire team.
Why this is correct
The whole-team approach promotes collective ownership of quality. When developers, testers, and business stakeholders work together, they identify risks earlier and resolve issues faster. This shared responsibility ensures that the quality strategy is integrated into the development process rather than being an afterthought performed by a separate group.
- ✗
Developers do not need to write tests, as the tester handles all validation.
Why it's wrong here
This approach is dangerous because it relies solely on the tester for quality, which is inefficient. Developers are best positioned to write unit tests for their own logic. Expecting a tester to be the sole guardian of quality ignores the benefits of developer-led testing and slows down the delivery cycle.
- ✗
Documentation is eliminated entirely to save time for writing code.
Why it's wrong here
Agile emphasizes 'working software over comprehensive documentation,' but this does not mean zero documentation. Some level of documentation is necessary for maintenance and regulatory compliance. Eliminating all documentation creates technical debt and long-term maintenance nightmares, regardless of the development methodology or the collaborative approach of the team members.
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.