As many testers know, you cannot test everything. Many things in a software product cannot be tested simply because there isn't enough time. Somehow you need to decide what to test. Just as important, you need to decide what NOT to test. Is your test team testing the right things? How would you know? This seminar introduces a systematic, risk-based approach to deciding where to focus your limited testing resources to get the maximum leverage. 2-day seminar

Who Should Attend

Project leaders, scrum masters, team leads, managers, test leads, quality managers, and developers


All of our public classes are held at the Construx Training Center

Review of Testing Basics

Why You Can't Test Everything

Introduction to Risk Management

  • Scope of risks
  • Risk management lifecycle

Identifying Elements of Product Risk

  • Identifiying functional elements of risk
  • Identifying non-functional elements of risk

Analyzing Element of Product Risk

  • Analyzing the probability of failure
  • Analyzing the severity of failure

Prioritizing Elements of Product Risk

Deciding How Much to Test, Based on Risk

Real World Examples of Risk-Based Testing

Variations on the Theme

  • Single factor risk analysis
  • Failure modes and effects analysis (FMEA)
  • Fault tree analysis (FTA)

Steve Tockey

Steve Tockey is the Principal Consultant at Construx Software. During more than three and a half decades in the software industry, he has worked as a programmer, ...