Session 1.3 - Goals of Testing

Module 1: Introduction to Software Testing | Duration: 1 hour

Learning Objectives
  • Explain the primary goals of testing and their rationale.
  • Map goals to strategy selection across risk, requirements, and architecture.
  • Define measurable criteria (coverage, oracles, exit) aligned to goals.

What Are Testing Goals?

Testing goals articulate the purpose of our validation effort: reduce risk, build confidence, and provide decision-ready information. Goals guide scope, depth, and investment.

Reduce Risk Build Confidence Inform Decisions

Core Goals

Defect Discovery: Expose faults early to lower remediation cost.
Risk Reduction: Focus on features with high business/technical risk.
Confidence & Fit-for-purpose: Provide evidence the product satisfies intended use.
Regression Safety: Guard against unintended side-effects of change.
Compliance & Reliability: Demonstrate standards adherence and operational resilience.

From Goals to Strategy

Goals determine how we test:

  • Risk-based testing: Prioritize critical paths and failure modes.
  • Requirements-based testing: Trace tests to user and system requirements.
  • Architecture-based testing: White-box and component interaction coverage.
  • Exploratory testing: Rapid learning loops to probe unknown risks.
  • Automation strategy: Stable, repeatable scenarios (regression, data permutations).
Goals Strategy Outcomes

Oracles & Coverage

Test Oracles
  • Specifications, contracts, reference implementations
  • Heuristics: consistency, comparable products, history
  • Metamorphic relations for complex domains
Coverage
  • Requirements, risks, data partitions
  • Code (branches/paths), interfaces, environments
  • Note: coverage is an indicator, not the end goal

Metrics & KPIs

  • DRE (Defect Removal Efficiency), escaped defects
  • Mean-Time-To-Detect (MTTD), Mean-Time-To-Repair (MTTR)
  • Automation stability (flake rate), coverage trends

Exit Criteria

Define done using goal-aligned thresholds:

  • All critical risks mitigated; no open Sev-1 defects
  • Requirement coverage ≥ agreed threshold; key scenarios automated
  • Performance/SLA benchmarks achieved in target environments

Summary & Assignment

Testing goals shape the strategy, oracles, coverage, and metrics we choose. Clear goals keep teams aligned and prevent metrics from becoming vanity targets.

Assignment: Pick a feature from a current/previous project. Write 3 testing goals, map each to a strategy, and define one metric and one exit criterion per goal.
Course Home