CAPM Agile Frameworks and Methodologies Practice Question
In Extreme Programming (XP), which practice involves integrating and testing the entire system multiple times per day?
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
✓
Continuous integration
Continuous integration (CI) is the practice of integrating code changes frequently, often multiple times per day, followed by automated testing. Option B (test-driven development) focuses on writing tests before code. Option C (refactoring) is about improving code structure without changing behavior. Option D (pair programming) involves two developers working together on the same code. Only CI involves integrating and testing the entire system multiple times per day.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Continuous integration
Why this is correct
Continuous integration in XP means integrating and testing the whole system several times daily, keeping the codebase releasable. This satisfies the practice constraint by catching integration defects within hours rather than at iteration end, when they are costlier to fix.
- ✗
Test-driven development
Why it's wrong here
Test-driven development writes unit tests before code, driving design at the developer level; it does not integrate or test the whole system. Continuous integration is the XP practice that merges and builds the entire system several times daily. TDD is tempting because it also centres on testing, but its scope is a single unit, not the full system.
- ✗
Refactoring
Why it's wrong here
Refactoring restructures existing code to improve its internal design without altering behaviour; it performs no integration or test execution. It is a continuous design hygiene practice, correct when the goal is reducing technical debt, not the daily whole-system build-and-test cycle Continuous Integration describes.
- ✗
Pair programming
Why it's wrong here
Pair programming places two developers at one workstation for continuous code review and knowledge sharing; it does not itself integrate or test the whole system. It is the correct practice when the aim is raising code quality and spreading expertise, not the multiple daily integration and testing cycle.
Go deeper
Related to this question
About these practice questions
This CAPM question is part of Courseiva's 451-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CAPM practice question is part of Courseiva's free PMI 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 CAPM exam.