VodQA-TooMuchVerificationNotEnoughValidation_SrinivasChillara
•Download as PPT, PDF•
0 likes•153 views
This was a lightening talk presented by Srinivas Chillara in the vodQA-3 : A QA Meet held in ThoughtWorks, Pune.
![Too Much Verification; insufficient Validation ,[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
Viewers also liked
Similar to VodQA-TooMuchVerificationNotEnoughValidation_SrinivasChillara
Similar to VodQA-TooMuchVerificationNotEnoughValidation_SrinivasChillara (20)
Recently uploaded
Recently uploaded (20)
VodQA-TooMuchVerificationNotEnoughValidation_SrinivasChillara
- 1. Saturday, 26 th March, 2011
- 4. How is it a case of impropriety? We are not doing justice to the QA role, but stopping at QC… … how do we see quality (as shown by our actions)… … Let’s see how we stop at QC
- 7. What can be done about it? We have to spend more time on validation activities, instead of only looking at verification Verification => That we are building it right Validation => That we are building the right thing While many of us will nod our heads wisely, there is little evidence on the ground in terms of behaviour.
- 8. Example Sides of a triangle: a,b,c String ClassifyTriangle(a,b,c)
- 9. Example Cancelling a railway ticket… you want to cancel first?
- 10. What are the signs of validation We should see that significantly more functionality being designed as a result of validation… in other words there are many more alternate paths identified. 80% of the code is executed in only 20% of the instances. We would be filling in the 80%. The analysts/designers, and end customers engage more with the testers, only then we’d have justification to the title of Quality Assurance.
Editor's Notes
- Quality is seen too narrowly as lack of bugs … bugs being defined as non conformance to documented wishes.
- Quality is seen too narrowly as lack of bugs … bugs being defined as non conformance to documented wishes.