By the way, risk analysis is quite a big word. It is not specific to software industry, and depending on what's you're looking for you can get very different results.

So, let me define what the purpose of conducting risk analysis in software testing is. My 2 cents definition would be "activity of understanding the impact of malfunctioning of the application." And the severity of the impact of each malfunction scenario will determine priority and intensity of the testing.

One thing I like to call out is that application malfunctioning is not only about use cases failures defined in spec. There are always implicit requirements that is not written in spec.

But normally, I start with use cases defined in spec.
Go through each use cases and find out the impact of malfunction. For example, you are testing login page. There are several use cases for this.

- Login with activated user with valid user name and password
- Login with invalid username
- Login with invalid password
- Login with not activated user name and password.
- Forgot password
- Register link

Now let's define risk and impact of each malfunction
- Failed to login with activated user name and password (high impact)
- Login success with invalid user name(high impact)
- Login success with invalid password (high impact)
- Login success with non-activated username and password (medium impact)
- Forgot password not working (medium impact)
- Register link is broken (high impact)

This is just an example of this. You can argue with different level of impact on each malfunction. But you have an idea about this approach. Here is another post for checking business impact and fault likelihood.  Let's go into more details
- Login failure message not specific enough (medium impact)
- Already logged user going to login page and still require login (medium impact)
- Login process taking too long (medium)
- Logout link does not work (high)
- Login username and password text field is too small (low)
- Password text field showing the password not dots (medium)
- on and on.....

Now you have three different buckets of test cases (high-medium-low). And then you decide what to test first and how intensively test those test cases.
You would..
Share
Related Documents
  1. Applying Risk Analysis in testing (1102)
  2. Risk Management & Analysis Techniques? (976)
  3. How Do I: Get Started with Test Cases in Visual Studio Test Professional 2010? (1526)
  4. Test automation using specific test script language (2051)
  5. Risk Analysis (1227)
  6. Project Management Guide Website (1039)
  7. Quality Risk Analysis (1264)
  8. Quality Risk Analysis (1146)
  9. [Ebook] Applying UML and Patterns (1765)
  10. Static Analysis and Statistical Analysis (1610)
  11. Risk Analysis (1100)
  12. Project Risk Analysis Questionnaire (2227)
  13. Documenting Analysis and Test (1808)
  14. Test Point Analysis: a method for test estimation (10156)
  15. Test Planning (1365)
  16. Web Load Test Planning (1470)
  17. Software Risk Management (2555)
  18. Software Risk Analysis : Qualitative and Quantitative (1243)
  19. Risk Management (2758)
  20. Secrets of Iteration Planning -- Tested, Working Software Every Two Weeks (588)