- Risk-based Testing
Risk-based testing (RBT) is a type of
software testing that prioritizes the features and functions to be tested based on priority/importance and likelihood or impact of failure. In theory, since there is an infinite number of possible tests, any set of tests must be a subset of all possible tests. Test techniques such as boundary value analysis and state transition testing aim to find the areas most likely to be defective. So by using test techniques, a software test engineer is already selecting tests based on risk.Types of Risks
This section lists some common risks.
Business or Operational
* High use of a subsystem, function or feature
* Criticality of a subsystem, function or feature, including unacceptability of failureTechnical
* Geographic distribution of development team
* Complexity of a subsystem or functionExternal
* Sponsor or executive preference
* Regulatory requirements
* [http://www.testingeducation.org/a/nature.pdf Exploratory & Risk Based Testing (2004) www.testingeducation.org, by Cem Kaner and James Bach]History
Most people consider [http://www.satisfice.com/blog James Bach] to be the "father" of risk-based testing. He described the idea in a paper entitled [http://www.satisfice.com/articles/gooden2.pdf The Challenge of Good Enough Software] in October 1995 appearing in the journal
American Programmer .
Wikimedia Foundation. 2010.