Chapter 3 - Static Testing

 

3.1 Static Testing Basics

What is Static Testing?

Static testing:

핵심 문장 (시험 표현)
“Static testing can find defects without executing the software.”


Static vs Dynamic Testing



Static TestingDynamic Testing
No executionCode execution required
Reviews, inspectionsTest execution
Early defect detectionFailure detection

Work Products Reviewed


3.2 Feedback and Review Process

Benefits of Static Testing (★★★★★ 시험 단골)

Static testing helps to:

  • Detect defects early
  • Reduce cost of fixing defects
  • Improve communication
  • Improve product quality
  • Identify inconsistencies and ambiguities

시험 함정
“Static testing finds failures” → ❌
Failures are found by dynamic testing


3.3 Review Types (★★★★★ MUST MEMORIZE)

Informal Review


Walkthrough

  • Author leads the meeting
  • Used for learning and understanding
  • Less formal


Technical Review


Inspection (Most Formal)

Exam favorite
“MOST formal review type” → Inspection


Review Roles (Very Important)

RoleResponsibility
AuthorCreated the work product
ModeratorLeads the review
ReviewerFinds defects
ScribeRecords defects
ManagerOptional, supports process

3.4 Review Process (Inspection Process)

Typical steps:

  1. Planning
  2. Initiation
  3. Individual review
  4. Review meeting
  5. Rework
  6. Follow-up

시험에서 “order” 문제로 자주 나옴


3.5 Static Analysis

What is Static Analysis?


Typical Defects Found by Static Analysis


Static Analysis vs Dynamic Testing (Trap Area)

Static AnalysisDynamic Testing
Finds defectsFinds failures
No executionExecution required
Early feedbackLater feedback

Chapter 3 – 시험 직전 암기 포인트

반드시 기억:

  • Static testing ≠ execution
  • Reviews ≠ test execution
  • Inspection = most formal
  • Moderator ≠ Author
  • Static analysis uses tools


VERY COMMON EXAM TRAPS

  • “Static testing detects failures” ❌
  • “Walkthrough is the most formal review” ❌
  • “Reviewer fixes defects” ❌
  • “Static analysis replaces dynamic testing” ❌

다음 이전