Quality assurance – winning formula
Click here to load reader
-
Upload
sreeram-kishore-chavali -
Category
Business
-
view
865 -
download
1
description
Transcript of Quality assurance – winning formula
![Page 1: Quality assurance – winning formula](https://reader038.fdocuments.in/reader038/viewer/2022100600/55525bc0b4c905d41d8b4972/html5/thumbnails/1.jpg)
QUALITY ASSURANCE – WINNING
FORMULA
Sreeram Kishore Chavali
![Page 2: Quality assurance – winning formula](https://reader038.fdocuments.in/reader038/viewer/2022100600/55525bc0b4c905d41d8b4972/html5/thumbnails/2.jpg)
CHALLENGES
� Balancing business goals and quality criteria
� Get it right first time Vs Get it out on time
� Prevention
� Costs due to bad quality
� Lost customers
![Page 3: Quality assurance – winning formula](https://reader038.fdocuments.in/reader038/viewer/2022100600/55525bc0b4c905d41d8b4972/html5/thumbnails/3.jpg)
People
•Domain experience
•Training
•Customer exposure
•Product Knowledge
•Dev: QA Ratio
Planning
•QA Strategy
•Scope
•Priorities
•Resources
•Risks
•Exit Criteria
•Resource Investment
Process
•Enforcement
•Exceptions
•Tools
•Metrics
IDEAS THAT WORK
![Page 4: Quality assurance – winning formula](https://reader038.fdocuments.in/reader038/viewer/2022100600/55525bc0b4c905d41d8b4972/html5/thumbnails/4.jpg)
INVESTMENT OF RESOURCES
Business Scenario Testing
Automation
Performance, Volume, Stress Testing
Certification
Unit/Reliability Testing
![Page 5: Quality assurance – winning formula](https://reader038.fdocuments.in/reader038/viewer/2022100600/55525bc0b4c905d41d8b4972/html5/thumbnails/5.jpg)
CUSTOMER FOCUS
� Role play: Simulate user scenario
� Data
� Environment
� Workflow
� Validate scenarios for ‘closeness’ to real-life
scenarios
� Crash-Testing of Cars
� Understand Usage
� 80 – 20 rule of functionality
� User Profiles
� Roles, Tasks
![Page 6: Quality assurance – winning formula](https://reader038.fdocuments.in/reader038/viewer/2022100600/55525bc0b4c905d41d8b4972/html5/thumbnails/6.jpg)
AUTOMATION
� Code Coverage
� How many lines of code is covered through
automated tests?
� What is good enough target? 60%?
� What is practical given resources/technology?
� Code Coverage goals for
� Most used features in application
� High risk areas
![Page 7: Quality assurance – winning formula](https://reader038.fdocuments.in/reader038/viewer/2022100600/55525bc0b4c905d41d8b4972/html5/thumbnails/7.jpg)
DEFECT ESCAPE RATE
� Defects found after a product release
� Review all of them
� Identify root cause (5 Whys)
� Set a baseline for release
� Monitor for future releases
� Refine processes/training to keep this stable or
lower
![Page 8: Quality assurance – winning formula](https://reader038.fdocuments.in/reader038/viewer/2022100600/55525bc0b4c905d41d8b4972/html5/thumbnails/8.jpg)
DON’T FORGET BASICS
� Reliable bug tracking system
� Clear instructions in bugs to avoid confusion
� Steps to reproduce
� Severity and priority
� Screenshots
� Instructions to differentiate between bugs and
enhancements
� Impacted customers for defects/enhancements
![Page 9: Quality assurance – winning formula](https://reader038.fdocuments.in/reader038/viewer/2022100600/55525bc0b4c905d41d8b4972/html5/thumbnails/9.jpg)
NEED FOR SPEED
� Keep the train moving
� Bucket features into
� High dev effort, high regression impact (Major
change)
� Low dev effort, high regression impact (Architecture
changes)
� Low dev effort, low regression impact (UI changes)
� High dev effort, low regression impact (new features)
� Plan releases with a mix of features to minimize
overall regression testing effort