Talk:Risk-based testing
![]() | Computing: Software Unassessed | ||||||||||||
|
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)
Assessing risks
A new section was added by an Indian technology student trying to obtain a mark. It was titled "assessing risks", however it does not explain how to asses risks at all. It discusses the need to asses risk in vague terms and is lacking the details required for an encyclopedic article. I tried to repair the section but it may be better to remove it. --Walter Görlitz (talk) 17:10, 26 October 2011 (UTC)
Neologism?
The quality of the current sources suggest this is a WP:NEOLOGISM. Can we get better sources, or should we consider merging this into Software testing? --Ronz (talk) 16:57, 25 January 2012 (UTC)