What is Risk Based Testing?

Prioritisation of test effort based on risk scores: find the most important defects as early as possible at the lowest price

“The goal is to reach an acceptable level of risk. At that point, quality is automatically good enough” 1)

Why Risk Based Testing?

  • Because testing is always under pressure; Testing effort is limited by time and money available.
  • Testing is the last thing done in a project
  • You must be able to cut down on the least important things
  • Because Risk based testing works well with Agile Development challenges.

Risk = Probability X Damage

  • Risk is defined on the basis of two factors: the probability of a fault occurring and the damage a fault would cause.
  • Damage determined by: financial, loss of clients, corporate identity, usage frequency
  • Probability determined by: complexity, size, prior knowledge, experiences gained during testing (defects tend to clump together), newly developed product vs. “off-the-shelf”

How is it done?

Test risk scores are obtained through Risk Assessment Sessions. These are simlar to Agile scoring sessions:

1) “The Challenge of Good Enough Software”, James Bach, American Programmer, 1995
 
risk_based_quality_assurance.txt · Last modified: 2010/01/18 06:32 by root
 
RSS - 200 © CrosswireDigitialMedia Ltd