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

Revolutionize software testing with AI! 🤖💻 Share your thoughts on ethical implications in the comments.

  As technology evolves, so too does the field of software testing. One exciting development in recent years is the use of AI (Artificial Intelligence) to automate repetitive tasks and improve testing accuracy. Through analyzing large amounts of data and identifying patterns, AI can help identify potential defects or vulnerabilities in software. AI-powered tools can also generate test cases and scenarios by simulating user behavior and input, allowing for more efficient and effective testing. In addition, machine learning algorithms can analyze and learn from past testing data, leading to better predictions and more streamlined testing. AI-powered tools can also help identify and prioritize critical bugs and defects, saving valuable time and effort in manual testing. But it's important to note that AI-powered testing is not a replacement for human testers. While AI can automate certain tasks and help identify potential issues, it's still necessary for human testers to provide a

Is AI taking over your job in software development and testing? 😱"

Are you a software developer or tester feeling threatened by the rise of AI in your industry? 😰 You're not alone. Many professionals in the field are concerned about the potential consequences of AI's integration into software development and testing. While some experts believe that AI can bring significant benefits to the industry, others worry that it could replace human expertise altogether. 🤔 AI algorithms can analyze massive amounts of data and automate many tasks, but they cannot replace the critical thinking and creativity of human beings. Additionally, there are ethical concerns associated with the use of AI in software development and testing. So, what can you do to ensure that you're not replaced by AI in your job? 💪 First, it's essential to recognize that AI is not a replacement for human expertise but rather a tool to augment it. Therefore, it's essential to learn how to work with AI-powered systems to increase your efficiency and productivity. Additi

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