Confirmation Testing vs Regression Testing
1. Introduction
When defects are fixed, ISTQB expects you to clearly understand what type of testing is performed and in which order.
This question focuses on testing performed after a software update that fixes incorrect behavior.
이 문제는 결함 수정 이후 어떤 테스트를 수행해야 하는지, 그리고 어떤 순서로 수행해야 하는지를 정확히 알고 있는지를 묻습니다.
2. Key Concept: Confirmation Testing vs Regression Testing
Two important concepts are involved here:
- Confirmation testing: checks that a specific defect has been fixed
- Regression testing: checks that unchanged parts of the system still work correctly
When a change is made, both types of testing are usually required.
두 가지 핵심 개념을 정리하면 다음과 같습니다.
- 확인 테스트(Confirmation testing): 수정된 결함이 제대로 고쳐졌는지 확인
- 회귀 테스트(Regression testing): 변경되지 않은 영역에 새로운 결함이 생기지 않았는지 확인
3. Practice Question
❓ Question
The navigation system software has been updated because it suggested routes that break traffic laws (e.g., driving the wrong way down one-way streets).
Which of the following BEST describes the testing that will be performed?
- a) Only confirmation testing
- b) Confirmation testing then regression testing
- c) Only regression testing
- d) Regression testing then confirmation testing
✅ Correct Answer: b)
4. Explanation (EN / KR)
✔ b) Confirmation testing then regression testing — Correct
After fixing the defect, the first step is confirmation testing to verify that the incorrect route suggestions are no longer produced.
Once the fix is confirmed, regression testing is performed to ensure that no new defects were introduced into unchanged parts of the system.
결함 수정 후에는 먼저 확인 테스트를 수행하여 잘못된 경로 안내 문제가 해결되었는지 확인합니다. 그 다음, 변경되지 않은 기능에 문제가 생기지 않았는지 회귀 테스트를 수행합니다.
❌ a) Only confirmation testing — Incorrect
Although confirmation testing is required, it is not sufficient on its own. Regression testing is also necessary to check for side effects of the change.
확인 테스트는 반드시 필요하지만, 그것만으로는 충분하지 않습니다. 수정으로 인한 부작용을 확인하기 위해 회귀 테스트도 필요합니다.
❌ c) Only regression testing — Incorrect
Regression testing checks unchanged areas, but it does not verify that the specific defect was fixed. Confirmation testing is therefore required.
회귀 테스트는 기존 기능을 확인할 뿐, 결함이 제대로 수정되었는지는 보장하지 않습니다. 따라서 확인 테스트가 반드시 필요합니다.
❌ d) Regression testing then confirmation testing — Incorrect
Although both types of testing are required, the order is wrong. Confirmation testing should always be performed before regression testing.
두 테스트 모두 필요하지만, 수행 순서가 틀렸습니다. 항상 확인 테스트를 먼저 수행한 뒤 회귀 테스트를 합니다.
5. Summary Table
| Testing Type | Purpose | Order | 한글 요약 |
|---|---|---|---|
| Confirmation testing | Verify defect is fixed | First | 결함 수정 확인 |
| Regression testing | Check unchanged areas | After confirmation | 부작용 확인 |
6. Final Takeaway
For ISTQB exams, remember this sequence:
Fix a defect → Confirmation testing → Regression testing
시험에서는 이 순서를 공식처럼 기억하세요.
결함 수정 → 확인 테스트 → 회귀 테스트
Related: More ISTQB Posts | Next Question
```