Talk:Risk-based testing

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
???	This article has not yet received a rating on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by WikiProject Software.

To the extent that this article relies on James Bach's and my work (the two cited articles). I think it misses the point.

There are really two different approaches to risk-based software testing.

One is about risks. Under this view, the risk-based tester imagines a way that the program can fail and designs tests to see if the program has that type of weakness. This is what I see as risk-based testing.
The other approach is about prioritizing resources. Given that we have figured out that some "area" or "feature" or something is risky, we throw more resources at it. This might be appropriate management, but I don't see much about testing here.

For more about my work on risk-based testing, see my course notes and videos at www.testingeducation.org/BBST/BBSTRisk-BasedTesting.html CemKaner (talk) 19:06, 8 March 2010 (UTC)[reply]