View
1
Download
0
Category
Preview:
Citation preview
Overview of Agile Testing
George Dinwiddiegdinwiddie@idiacomputing.com
IDIA Computing, LLChttp:idiacomputing.com
http://blog.gdinwiddie.com
Ken Pughken.pugh@netobjectives.com
Net Objectiveshttp://www.netobjectives.com
Agile Development Practices West 2011Agile Testing Workshop Monday, June 6, 2011
Check http://idiacomputing.com/publications.htmlfor an updated copy of these slides
ADP-West 2011 Copyright © 2011 by George Dinwiddie, iDIA Computing, LLC, all rights reserved 2
Make Balloons Like This:
ADP-West 2011 Copyright © 2011 by George Dinwiddie, iDIA Computing, LLC, all rights reserved 3
The Testers' Placein Software Development
Are testers hereon your project?
ADP-West 2011 Copyright © 2011 by George Dinwiddie, iDIA Computing, LLC, all rights reserved 4
Why so many rejects?
● What does “Like this” really mean?
● How can we measure “Like this” earlier?
ADP-West 2011 Copyright © 2011 by George Dinwiddie, iDIA Computing, LLC, all rights reserved 5
This time, no rejects!
ADP-West 2011 Copyright © 2011 by George Dinwiddie, iDIA Computing, LLC, all rights reserved 6
The Three Amigos
● Business people● Programmers● Testers
working together to produce the best possible outcome.
draw
ing
from
http
://pi
ctof
igo.
com
ADP-West 2011 Copyright © 2011 by George Dinwiddie, iDIA Computing, LLC, all rights reserved 7
Bugs
Still netting a few But not swatting swarms
ADP-West 2011 Copyright © 2011 by George Dinwiddie, iDIA Computing, LLC, all rights reserved 8
Not collecting, counting, and classifying bugs!
Pho
to b
y M
ike
Sco
ltock
ADP-West 2011 Copyright © 2011 by George Dinwiddie, iDIA Computing, LLC, all rights reserved 9
Helping the programmermake a system that works right
ADP-West 2011 Copyright © 2011 by George Dinwiddie, iDIA Computing, LLC, all rights reserved 10
Helping the businessmake the right system
draw
ing
from
http
://pi
ctof
igo.
com
ADP-West 2011 Copyright © 2011 by George Dinwiddie, iDIA Computing, LLC, all rights reserved 11
Agile Testing Quadrants
from Brian Marick, http://www.exampler.com/old-blog/2003/08/21/#agile-testing-project-1
Agile addsthis side to
testing.
Finding Bugs
Performance,Reliability tests
ATDD
TDD
ADP-West 2011 Copyright © 2011 by George Dinwiddie, iDIA Computing, LLC, all rights reserved 12
What about your current practices?
● Which practices should we keep?● Which practices should we discard?● Which practices should we keep for awhile
and then phase out?● Which practices should we modify?● Which practices should we replace with a
different practice?
ADP-West 2011 Copyright © 2011 by George Dinwiddie, iDIA Computing, LLC, all rights reserved 13
Waiting for Developmentbefore Testing
● Purpose:● Reducing testing effort by testing in a single pass
● But...● If tests find bugs after “Dev Complete” then it
requires time-costly rework● If tests are automated, then re-running them is
cheap and easy● Untested code leaves uncertainty about how much
functionality is really “done”
ADP-West 2011 Copyright © 2011 by George Dinwiddie, iDIA Computing, LLC, all rights reserved 14
Pre-Release Regression Testing
● Purpose:● Checking against specifications
● But...● If specifications are expressed with automated tests,● Consider investing this time doing exploratory testing
● Considerations● Don't drop until your automated tests give you
confidence● Work toward making these tests find zero bugs
ADP-West 2011 Copyright © 2011 by George Dinwiddie, iDIA Computing, LLC, all rights reserved 15
Requirements Documents
● Purpose:● Carrying specifications from analysts to
programmers and testers
● But...● If the Three Amigos have direct conversations,● Consider combining with automated tests
● Considerations● Provides the ultimate in traceability● Who else reads these documents?
Recommended