Chapter 5 - Test Management

 

5.1 Test Planning

Purpose of Test Planning

Test planning defines:

  • Scope of testing
  • Approach (levels, types, techniques)
  • Resources and roles
  • Schedule
  • Risks
  • Entry and exit criteria

시험 표현
“Which activity defines the scope and approach?” → Test planning

A test plan may include test data requirements at a high level, but it does not define detailed test data and expected results.


Test Plan Contents (★★★★★ MUST KNOW)

A test plan typically includes:

  • Test objectives
  • Test scope
  • Test strategy / approach
  • Test environment
  • Test schedule
  • Roles and responsibilities
  • Risks and mitigation
  • Entry and exit criteria



5.2 Risk-Based Testing (★★★★★)

What is Risk?

Risk = Likelihood × Impact


Product Risk vs Project Risk

Product RiskProject Risk
Risk of product failureRisk of not completing the project
Related to functionality, performance, securitySchedule, resources, skills

Exam trap:
“Performance failure” → Product risk


Risk-Based Testing Principles

  • Identify risks
  • Assess risks
  • Prioritize testing based on risk
  • Allocate effort to high-risk areas


5.3 Test Monitoring and Control

Test Monitoring

  • Collect metrics
  • Track progress
  • Compare actual vs planned


Test Control

  • Take corrective actions
  • Re-plan if necessary

Monitoring = observe
Control = act


5.4 Configuration Management

Purpose

Configuration management ensures:


Items Under Configuration Control

  • Test cases
  • Test scripts
  • Test data
  • Requirements
  • Code


5.5 Incident (Defect) Management

Incident Report Contents

  • Unique ID
  • Summary
  • Steps to reproduce
  • Expected vs actual result
  • Severity
  • Priority
  • Status


Severity vs Priority (★★★★★ Exam Favorite)

SeverityPriority
Impact of defectUrgency of fixing
TechnicalBusiness decision

High severity ≠ High priority (and vice versa)


5.6 Test Estimation

Common Estimation Techniques

  • Expert-based estimation
  • Analogous estimation
  • Metrics-based estimation


5.7 Test Completion Criteria

Exit Criteria Examples

  • Planned tests executed
  • Acceptable defect level reached
  • Coverage achieved
  • Risks mitigated


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

무조건 기억:

  • Test planning defines scope & approach
  • Risk = likelihood × impact
  • Product risk ≠ Project risk
  • Monitoring ≠ Control
  • Severity ≠ Priority


VERY COMMON EXAM TRAPS

  • “Risk-based testing eliminates risk” ❌
  • “Monitoring includes corrective actions” ❌
  • “Priority is set by testers” ❌ (often business)
  • “Configuration management is optional” ❌

다음 이전