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

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 Quality Center - Best Practices

1.Introduction Quality Center is a test management tool which provides very good features for managing both your manual and automated test cases. This paper highlights the best practices for managing your test cases. When you open Quality center, depending on your rights it display the below mentioned option in the sidebar: 1. Requirements 2. Test Plan 3. Test Lab 4. Defects 5. Dashboard 2.Requirements When you have assigned with the responsibility of developing your test cases in the quality center then you must be wondering where to start with. I am going to share my experience to overcome such a situation. You need to find the solution of some question before you start writing your test cases. 1. Is your requirement developed and available? 2. Is your requirement organized in a logical sequence? If answer to both of the above question is Yes, then you can start with Requirement option in the side bar. In case your requirement is under development, then you keep your...

ABC of Unit Testing

What is Unit Testing? After writing any code, every programmer will do some kind of testing to make sure the code works as expected. This testing is called 'unit testing'. Unit testing is done in different ways. Some programmers write simple test applications to test their own code. Some others simply debug the code and change the values during debugging to make sure the code works fine for different cases. Some facts about unit testing: Unit testing is done by developers. Quality department does different tests, they are not unit tests. Every programmer must do unit testing after finishing development or during development itself. Unit testing can be done by writing separate test applications to call your classes and methods to make sure the classes work as expected. This is called manual unit testing. Unit testing can be automated by writing unit test scripts. This is called Automated Unit Testing. In automated Unit Testing, after writing each class/method, you will write sev...