The assessment of quality requires an objective review of the solution against the requirements. The quality of the solution is typically measured by testing teams through well-defined tests that are written from requirements. No amount of testing will prevent all defects, detect all defects, or prove a product is defect-free. There are too many permutations possible to completely test a system. Therefore, Risk Based Testing and its underlying principles: requirements validation, static testing, risk assessment, risk scoring, and risk driven testing are a necessity in defining and reaching quality expectations at the end of each testing phase. Furthermore, risk based testing provides both the IT Team and business stakeholders confidence in the quality ensured through the testing strategy. In this presentation, you will learn about how to implement a risk driven testing cycle and then measure your results. Was it worth it? Come find out!

1. Shaminder Rai
Dave Patel

2. What do you mean!!! Risk Based Testing?
 Guides Testing: application
of risk scores to support test
planning, creation, and
execution
 Improves Transparency:
testing estimates and
budgeting
(Project Decision
Framework)
 Promotes collaboration
between IT and business
stakeholders
 Facilitates the reduction in
test execution time and
total cost of quality
 Provides greater
assessment of risk and
achieved quality

3. What Can Get Risky?
Risk Scoring Criteria
Hardware
Reqs.
Docs. Defect
Trends
Software

4. 1. Validating Requirements & Collecting
Inputs
 Static Testing: Documentation
 Stakeholder Inputs
 Requirements: Use Cases, Stories, Content Matrix
 Architecture: System Diagram, Process Flow

5. 2. Assessing Risk
Risk Score = Business Criticality * Failure Probability
RISK: Any factor that can result in negative
consequences
 What can be provided a Risk Score:
 Functional Requirements
 Epics, Features, Story Cards
 Nonfunctional Requirements
 Environments, Hardware, Software, Testing Tools, Resources, Hours

6. Business Criticality
 Type of Process
 Business Impact
 Frequency of Use
 Number of Users
Business Impact: Revenue Generation, Increased
Customer Engagement, Simplified Processing,
Marketing, Customer Utility
Visibility: Customer Perception, Retention, Market
Expansion
(1) Most Critical  (4) Least Critical

7. Failure Probability
 Change Rate
 Software Maturity
 Defect Rate
 GUI screen elements
(1) Highest Failure  (4) Lowest Failure

8. Risk Scoring
Additional
Factors
Requirement
Name/UC ID
Type of
Process
Business
Impact
Frequency
of Use
(Views)
Number of
Users
(Visitors)
Business
Criticality
Score
Native App
High priority/
Critical
Input From
Requirements
Calculation
Validation
Legal Very Often Many/High 1
Responsive
Website
Data Change Revenue Often Some/Medium 2
Web App
Customer
Satisfaction
Display Customers Rarely/ Very
Rarely
Few/ Low 3
Additional
Factors/
Application
Type
Requirement
Name/ UC ID
Change Rate
(Software/App
Impact)
Software
Maturity
Defect
Rate
# of GUI/
Mainframe
Screen
Elements
Failure
Probability
Score
Native App
High priority/
Critical
Input From
Requirements
New Feature Immature High More Than X 1
Responsive
Website
Changed
Feature
Middle Medium Between X-
X
2
Web App
Customer
Satisfaction
Unchanged
Feature
Mature Low Only X 3
Business Criticality
Failure Probability

9. Risk Scoring =
Business Criticality * Failure Probability

10. 3. Test Planning
 Test High Risk Items first & deeper
 Test Low Risk later
 Test allocation across OS, Browsers, Devices
 Heat map Representation of Test Strategy

11. Visual Representation of Test Strategy

12. Risk Profiling by Test Type & Phase

13. 4. Test Execution
 Determine level of Coverage for Regression Testing
 Execute Tests based on Risk
 Manage defects based on risk

14. The Feedback Loop
 Continually Adapt Testing Strategy
 Managing Defect Resolution based on Risk
Outcomes:
 Increased Transparency of Testing Strategy for
Project Decision-Makers
 Quantitative Approach for Providing Confidence in
Quality of Solution
 Possible Reduction of Overall Testing Time & Project
Cost

15. Critical Success Factors
 Consistency in Risk Score Assessment
 Understand the Benefits of the Process
 Understand the Importance of Risk Scoring & Testing
 Maintain Visibility: Priority of implementing
requirement & managing development, testing, and
defects