Skip to main content

Risk Based Testing

Introduction
Risk based testing is a concept which define the roadmap for making test strategy and taking decision on release of product. This concept outlines many of the important aspect of testing when time to market and quality has to be met. How many of times you have tested your product in limited time? I hope you have done it many a times? What approach you normally take when your testing schedule has been reduced and you are asked to test the application in limited schedule? Do you follow any defined approach to overcome such a scenario? I hope many of us “not”. We know all these concepts but making use of it is really difficult as we do not know how to approach with this concept.
Purpose
The purpose of this article is to present a practical approach to Risk based testing based on my experience. It may be applicable or may not be applicable for your day to day activity.
References
• CSTE Group
• Project Experience - myself
Input
Testing schedule and effort has been reduced.
Process
Entry Criteria
Test Cases & Scenarios are ready
Identification of Important Test Scenario or Cases
The first step is to identify the important test scenario or cases based on below mentioned parameters:
• Capability
• Reliability
• Usability
• Performance
• Installability
• Compatibility
• Supportability
• Testability
• Maintainability
• Portability
• Localizability
Mechanics for Identification and Prioritization of Test Scenarios
To identify and prioritize the test scenarios, you need to prepare a Test Factor matrix and assign test scenarios, weightage based on the importance of above parameters. To carry out this you need to do brainstorming session with your team members.
It is not necessary that you are going to provide score for all the test cases for all the factors. Some of your test cases do not suffice the above factors. In that case you need not to give scoring. This help in focusing only on important cases.
The Test Factor matrix gives you an analysis based on important quality factors that are required to be fulfilled in the product. It helps in identifying your test scenarios which must be executed before the delivery of the product.
The customer input may be required for prioritizing the test scenario based on your analysis.
From Test Factor matrix , you can analyze that “Performance is not a major concern area”, the major concern area are “Usability”, “Reliability”, “Capability”.
Now start with Usability Test Scenarios – execute the cases based on maximum weightage to minimum weightage. Follow the same rule for other factors.
Output
Test Factor matrix
• Test Priority List
Note: Your feedback is most welcome. Please leave your comments.

Comments

Popular posts from this blog

Mantis - Defect Management Tool - User Guide

Introduction This white paper contains information related to an open source defect management tool called Mantis which is freely available for managing all your defects. Where to Download One can download the latest version of Mantis from http://sourceforge.net/project/showfiles.php?group_id=14963 Download the “mantis-stable” and then “mantis-x.y.z.zip”.1.1 PRE-REQUISITE Operating System Windows 2003 Server, MacOS, OS/2, Linux, Solaris Database MySQL database 3.23.2 and higher Software PHP 4.0.6 and higher Application Server Apache 1.3, Apache 2.0.54, IIS 6.0 with Web Services Extension Browser IE6 and above, Mozilla Firefox STEPS FOR INSTALLATION – FOR WINDOWS MySQL Installation Install MySQL by downloading it from http://dev.mysql.com/get/Downloads/MySQLGUITools/mysql-gui-tools-5.0-r6-win32.msi/from/http:/www.mirrorservice.org/sites/ftp.mysql.com/ . Please follow the below mentioned steps while installing MySQL: (Please remember the password for “root” account...

Why to do Software Testing?

Regardless of the limitations, testing is an integral part in software development. It is broadly deployed in every phase in the software development cycle. Typically, more than 50% percent of the development time is spent in testing. Testing is usually performed for the following purposes: To improve quality. As computers and software are used in critical applications, the outcome of a bug can be severe. Bugs can cause huge losses. Bugs in critical systems have caused airplane crashes, allowed space shuttle missions to go awry, halted trading on the stock market, and worse. Bugs can kill. Bugs can cause disasters. The so-called year 2000 (Y2K) bug has given birth to a cottage industry of consultants and programming tools dedicated to making sure the modern world doesn't come to a screeching halt on the first day of the next century. [Bugs] In a computerized embedded world, the quality and reliability of software is a matter of life and death. Quality means the conformance to the ...

HP QTP Tutorial - Chapter 10

1 Debug In my previous chapter, I discussed about the features available in Resources Menu such as Object Repository, OR Manager, and Associate Repositories etc. This chapter covers the features available under Debug Menu option. This chapter explains the following features available under Debug Menu : The features under Debug menu are very useful and also frequently used. Although in most of the cases you use Short Keys. We will cover all these features in detail in this chapter. 1.1 Pause  There could be case when are you running your script and want to pause (remember Pause and Stop are different things), then you can navigate to Debug ->Pause. The script will be paused at the current execution step. You can then do your analysis and then continue with your run by clicking on Automation-> Run. Alternatively you can also Press F5 or Run button from the tool bar.  1.2 Step Into  There are situation in a script which makes call to other Action or Funct...