Your SlideShare is downloading. ×
VodQA-TooMuchVerificationNotEnoughValidation_SrinivasChillara
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

VodQA-TooMuchVerificationNotEnoughValidation_SrinivasChillara

295
views

Published on

This was a lightening talk presented by Srinivas Chillara in vodQA-3 : A QA Meet held in ThoughtWorks, Pune.

This was a lightening talk presented by Srinivas Chillara in vodQA-3 : A QA Meet held in ThoughtWorks, Pune.

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
295
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • 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.
  • Transcript

    • 1. Saturday, 26 th March, 2011
    • 2. Too Much Verification; insufficient Validation
      • Srinivas S Chillara
      • Independent Consultant
      • GoodAgile
    • 3. QA?
      • The QA community is obsessed by bugs;
      • Should it be the case?
      • Well, yes and no.
    • 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
    • 5. The underlying influencers
      • As we write test cases we tend to anchor it to some document or the other
      • Unfortunately many of us largely take document as correct
      • Somewhere as a group we think that the quality of software that we build lies in the meeting the functional description documented
      • Quality is lack of bugs
      • Meet the letter… what about the spirit?
    • 6. The two problems
      • Meet the letter… what about the spirit?
      • Quality is seen too narrowly
      • We create conflict later on, between ourselves and our customers
    • 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.