Risk-based testing
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
No issues specified. Please specify issues, or remove this template. |
Risk-based testing (RBT) is a type of software testing that prioritizes the tests of features and functions based on the risk of their failure - a function of their importance and likelihood or impact of failure.[1][2][3][4] 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.
Assessing risks
{{asy to set up and to maintain with software changes.[vague]
Types of Risks
Risk can be identified as the probability that an undetected software bug may have a negative impact on the user of a system.[5]
The methods assess risks along a variety of dimensions:
Business or Operational
- High use of a subsystem, function or feature
- Criticality of a subsystem, function or feature, including the cost of failure
Technical
- Geographic distribution of development team
- Complexity of a subsystem or function
External
- Sponsor or executive preference
- Regulatory requirements
E-Business Failure-Mode Related[6]
- Static content defects
- Web page integration defects
- Functional behavior-related failure
- Service (Availability and Performance) related failure
- Usability and Accessibility-related failure
- Security vulnerability
- Large Scale Integration failure
References
- ^ Gerrard, Paul (2002). Risk Based E-Business Testing. Artech House Publishers. ISBN 1-58053-314-0.
{{cite book}}: Unknown parameter|coauthors=ignored (|author=suggested) (help) - ^ Bach, J. The Challenge of Good Enough Software (1995)
- ^ Bach, J. and Kaner, C. Exploratory and Risk Based Testing (2004)
- ^ Mika Lehto (October 25, 2011). "The concept of risk-based testing and its advantages and disadvantages". Ictstandard.org. Retrieved 2012-03-01.
- ^ Stephane Besson (2012-01-03). "Article info : A Strategy for Risk-Based Testing". Stickyminds.com. Retrieved 2012-03-01.
- ^ Gerrard, Paul and Thompson, Neil Risk-Based Testing E-Business (2002)
 | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |