ISTQB 연습문제 풀이 - Exam A : Q#18

1. Introduction

This question assesses whether you can distinguish true review success factors from statements that are incorrect or misleading.

Note (EN/KR):
Static testing (including reviews) finds defects, not failures. 정적 테스트(리뷰 포함)는 결함(defects)을 찾으며, 실패(failures)는 실행 기반 테스트에서 발생합니다.

2. Key Concepts

✔ Success Factors in Reviews

  • Adequate time allocation 충분한 시간 배정
  • Review small, manageable parts 작은 단위로 나누어 리뷰
  • Respectful and collaborative behavior 존중하는 태도와 협력적인 분위기
  • Objective handling of findings 발견된 결함을 객관적으로 처리

3. Practice Question

❓ Question

Which of these statements is NOT a factor that contributes to successful reviews?

  • a) Participants should dedicate adequate time for the review
  • b) Splitting large work products into small parts to make the required effort less intense
  • c) Participants should avoid behaviors that might indicate boredom, exasperation, or hostility to other participants
  • d) Failures found should be acknowledged, appreciated, and handled objectively

✅ Correct Answer: d)

📘 Explanation (EN/KR)

  • a) Not correct. Allocating enough time is a known review success factor.
    충분한 시간을 할당하는 것은 성공적인 리뷰의 핵심 요인입니다.
  • b) Not correct. Splitting work products into smaller parts increases review effectiveness.
    산출물을 작은 단위로 나누면 리뷰 효율성이 증가합니다.
  • c) Not correct. Participants avoiding negative behaviors contributes to a safe and effective review environment.
    부정적 태도를 피하는 것은 안전하고 생산적인 리뷰 환경을 만듭니다.
  • d) Correct. Reviews identify defects, not failures. “Failures” occur only during dynamic testing when code is executed.
    리뷰는 결함(defects)을 찾는 활동이며, 실패(failures)는 동적 테스트 실행 중에만 발생합니다.

✔ Therefore, option (d) is the only statement that does NOT represent a success factor.
✔ 따라서 (d)만 성공 요소와 무관한 문장입니다.

📊 Summary Table

Option Statement Success Factor? Explanation
a Adequate time for review ✔ Yes 충분한 시간은 성공 요소
b Split work into smaller parts ✔ Yes 작은 단위 리뷰는 효과적
c Avoid negative behaviors ✔ Yes 협업 분위기 조성
d “Failures” handled objectively ❌ No 리뷰는 결함 찾기 활동, 실패 아님

4. Summary & Call to Action

Understanding what contributes to successful reviews helps strengthen your knowledge of static testing and prepares you for real-world QA collaboration.

성공적인 리뷰 요인을 이해하면 정적 테스트 전반을 더 잘 이해하고 실제 QA 협업에서도 큰 도움이 됩니다.

refer to : FL-3.2.5


Related: More ISTQB Posts

다음 이전