1. Introduction
Static testing is one of the core ISTQB Foundation topics. This question asks you to identify which statement is NOT a real benefit of static testing.
Note (EN/KR):
Static testing includes reviews, walkthroughs, and analysis done without executing the code.
정적 테스트는 코드를 실행하지 않고 리뷰, 워크스루, 분석을 통해 결함을 찾는 활동입니다.
2. Key Concepts
-
Static Testing – evaluating work products (requirements, design, code) without execution.
정적 테스트: 실행 없이 요구사항, 설계, 코드 등의 작업 산출물을 평가하는 과정입니다. -
Main Benefits
주요 장점- Early detection of defects → lower cost
결함을 초기에 발견 → 비용 절감 - Finding defects difficult to catch with dynamic testing
동적 테스트로 놓치기 쉬운 결함 발견 - Detecting inconsistencies, ambiguities, and gaps in requirements/design
요구사항/설계의 비일관성·모호성·누락 발견
- Early detection of defects → lower cost
3. Practice Question
❓ Question
Which of the following is NOT a benefit of static testing?
- a) Having less expensive defect management due to the ease of detecting defects later in the SDLC
- b) Fixing defects found during static testing is generally much less expensive than fixing defects found during dynamic testing
- c) Finding coding defects that might not have been found by only performing dynamic testing
- d) Detecting gaps and inconsistencies in requirements
✅ Correct Answer: a)
📘 Explanation (EN/KR)
-
a) Correct. Finding defects later in the SDLC is more expensive, not cheaper.
Static testing is valuable because it finds defects early, not late.
정답. SDLC 후반에 결함을 찾으면 비용이 더 많이 듭니다. 정적 테스트의 장점은 ‘늦게’ 찾는 것이 아니라 ‘초기에’ 결함을 찾는 것입니다. -
b) Not correct. This is a true benefit of static testing: fixing defects early is cheaper.
오답. 정적 테스트의 실제 장점입니다. 초기에 결함을 수정하면 비용이 절감됩니다. -
c) Not correct. Static analysis can reveal issues not easily caught by dynamic testing.
오답. 정적 분석은 동적 테스트만으로 발견하기 어려운 코딩 결함을 탐지할 수 있습니다. -
d) Not correct. Reviews help detect requirement gaps and inconsistencies — a key benefit of static testing.
오답. 정적 리뷰는 요구사항의 누락·비일관성·모호성을 찾아내는 중요한 장점입니다.
✔ Therefore, the only statement that is NOT a benefit is option (a).
✔ 따라서 정적 테스트의 장점이 아닌 유일한 문장은 (a)입니다.
📊 Summary Table
| Option | Statement Summary | Correct? | Explanation |
|---|---|---|---|
| a | Defects are cheaper to manage later in SDLC | ❌ NOT a benefit |
Late fixes are more costly. 후반 결함 수정은 비용이 더 큼. |
| b | Fixing defects found early is cheaper | ✔ Benefit |
Early detection saves cost. 초기 발견이 비용 효율적. |
| c | Static testing finds defects dynamic testing might miss | ✔ Benefit |
Static analysis catches structural/code issues. 동적 테스트로 놓칠 결함 탐지 가능. |
| d | Detecting requirement gaps/inconsistencies | ✔ Benefit |
Reviews reveal issues before coding. 코딩 전 요구사항 문제 발견. |
4. Summary & Call to Action
Static testing is powerful because it finds defects early, saves cost, and improves the quality of requirements and design artifacts.
정적 테스트는 결함을 조기에 발견하여 비용을 절감하고 요구사항·설계 품질을 높이는 데 매우 효과적입니다.
refer to : FL-3.1.2
Related: More ISTQB Posts
