ACC presentation for QA Club Kiev
-
Upload
nikita-knysh -
Category
Business
-
view
897 -
download
6
description
Transcript of ACC presentation for QA Club Kiev
![Page 1: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/1.jpg)
Balancing Your Test Effort
Planning test with Google’s approach
Nikita Knysh
Ciklum, August 17, 2011
![Page 2: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/2.jpg)
The Speaker
• Nikita Knysh, 30 y.o., ~11 years in IT
• Background: IT education, webdev, support+lead, PM, TW, BA+lead, ISTQB FL
• Now: 4 years with Scanjour, Test TL
![Page 3: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/3.jpg)
Agenda
• The Challenge• The Directions• The Method• The Tools• Probs & Cures
![Page 4: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/4.jpg)
The Challenge
• What to test if not enough time?• What to test if have buffer?• Much test, few bugs• No overview of test needs• Not enough sync between roles
![Page 5: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/5.jpg)
The Directions
• Discuss• Summarize• Prioritize
… team-wide & easily
So what’s the right approach then??
![Page 6: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/6.jpg)
The Method: Origin
ACC (Attribute-Component-Capability)
James A. Whittaker,
Test Director at Google,
2010
![Page 7: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/7.jpg)
Microsoft and Google use this.
Can we?
![Page 8: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/8.jpg)
The Method: Concept
• List product’s selling points (Attributes)• Break down the product into tech
Components. • Break down the product based on
WHAT it does (Capabilities).
We get a model that reflects all
the vital views on the product!
![Page 9: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/9.jpg)
The Method: ACC Modeling
• ACC list
• Time to give it some numbers!
![Page 10: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/10.jpg)
The Method: Giving it Numbers
• Complexity
increases risk of human mistakes during code development and maintenance and therefore risk of introducing bugs
• Use full scale (1 to 5)• Track averages
![Page 11: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/11.jpg)
The Method: Giving it Numbers
• Complexity factors
code logicbusiness logic
how much UI?
how much error handling?
how easy to debug?quality of requirements
tech expertise
unit test coverage
auto test coverage
code ownership
architecture
![Page 12: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/12.jpg)
The Method: Giving it Numbers
• Frequency of Use
how often the capability is called by user or automatically and therefore how often failures caused by defects in code will most likely occur
![Page 13: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/13.jpg)
The Method: Giving it Numbers
• User Impact
damage dealt to user and / or system intent should the capability fail completely or severely
![Page 14: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/14.jpg)
The Method: Outcome
• Testing Needs
= Complexity * Frequency * Impact
![Page 15: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/15.jpg)
Now we know where the risk is.
Now we know where we need more test.
and…
![Page 16: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/16.jpg)
Our knowledge is based on cumulated vision of the whole team!
…and it is extremely easy to overview!
![Page 17: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/17.jpg)
The Method: Outcome
• ACC list, now with numbers
![Page 18: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/18.jpg)
The Method: Outcome
• Matrix view of capability count
![Page 19: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/19.jpg)
The Method: Outcome
• Matrix view of testing needs
![Page 20: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/20.jpg)
The Tools: How We Do It
• ACC items are TFS work items• ACC linked to TCs and bugs for metrics• Excel book for each model• Two-way sync between TFS and Excel• Instant update: DWH cube is avoided• Pivot tables and charts
make the beauty
![Page 21: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/21.jpg)
The Tools: How It Looks
• Model overview in Excel
![Page 22: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/22.jpg)
That easy?
Really?
![Page 23: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/23.jpg)
Probs & Cures
• “No time for modeling!”. Include into DoD.
• “It shows what we knew!”
Be strong! Don’t manipulate!
+True for any document.
![Page 24: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/24.jpg)
More Probs & Cures
• Can’t test individual capabilities. Reconsider product breakdown.
• Hard to bind test cases and bugs to capabilities. Reconsider model’s detail level. Think starting from ACC, not test cases.
![Page 25: ACC presentation for QA Club Kiev](https://reader034.fdocuments.in/reader034/viewer/2022051111/55388e4a550346bf308b47c7/html5/thumbnails/25.jpg)
Thank you!
• Questions & Answers