Key Success Factors for Agile Testing 2016
-
Upload
janetgregoryca -
Category
Technology
-
view
476 -
download
1
Transcript of Key Success Factors for Agile Testing 2016
Janet Gregory, DragonFire Inc.Copyright 2016
Agile Singapore
February 17 2016
@janetgregorycaWith input from Lisa Crispin
Agile Testing; 2009
More Agile Testing: 2015
Website:
www.agiletester.com www.agiletester.ca
DragonFire Inc.
www.janetgregory.ca
@janetgregoryca
2
Some ideas for successful agile testing
and
the understanding of the mindset change in that needs to accompany the
adoption of agile
3
“agility”
A methodology or a philosophy?
So simple to define
So hard to implement
Agile teams:
produce a continuous stream of value
at a sustainable pace
while adapting to the changing needs of the business.
http://testobsessed.com/blog/2010/12/14/the-agile-acid-test/
• an activity; not a phase• interactive and starts from the beginning• more than testing code
1. Use the whole-team approach
2. Adopt an agile testing mindset
3. Automate your regression suite
4. Provide and obtain feedback
5. Build a foundation of core agile values
6. Collaborate with your customers
7. Look at the big picture
1. Use real examples
2. Perform exploratory testing
3. Test your features (and the system)
4. Learn continually
5. Sensitivity to your context
6. Keep it real
8
Ask what problem are they trying to solve?
What examples express the intent of the story / feature, the business rules?
Identify risks so customer can make best decision.
Sticker by Brian Marick
Feature(with
examples) UserStory
High-Level
AT
AcceptStory
Explore Examples
Fix Defects
Code, test & automate story
ATDDAcceptance Test Driven Development
#3 – Test Your Feature (capabilities)
• What’s important to the business?
#4 – Learn Continually
through play
Cross-functional knowledge
Dis
cip
linar
y sk
ills
http://www.slideshare.net/ehendrickson
Analytical
Relentlessly Curious
Observant
Skeptical
Empiricist
Critical Thinker
Investigator
17
Instead of ◦ We’re here to find bugs … or ensure
requirements are met … or break the software …
Think◦ What can I do to help deliver
the software successfully!
Mobile and embedded
Large organizations
• Don’t over promise
• Keep testing in sync with development
• Make your information visible
• Work to remove testing constraints
There’s no magic!
and teams need to stop
living in a
fantasy world
1. Use real examples
2. Perform exploratory testing
3. Test your features (and the system)
4. Learn continually
5. Sensitivity to your context
6. Keep it real
21
Picture by Growing Agile
And always, strive for qualityby remembering the whole
team approach
photoshd.wordpress.com/2008/04/24/13/
Agile Testing: A Practical Guide for Testers and Agile Teams
More Agile Testing: Learning Journeys for the Whole Team
By Janet Gregory and Lisa Crispin
www.agiletester.ca
www.agiletester.com
Contact info
www.janetgregory.caEmail: [email protected]: janetgregoryca
24
Instead of saying NO,
or being the gatekeeper
Be the information provider so business can make the decisions
Questions?
25
• Adzic, Gojko, Specification by Example: How Successful Teams Deliver the Right Software, Manning, 2011
• Gärtner, Markus, ATDD By Example: A Practical Guide to Acceptance Test-Driven Development, Addison-Wesley, 2012a
• Karten, Naomi, "Are You Listening?", http://www.agileconnection.com/article/are-you-listening, Agile Connection, 2009
• Keogh, Liz, http://lunivore.com - look for her posts on BDD, Real Options
• Levison, Mark, "The Beginner's Mind - An Approach to Listening", http://www.infoq.com/news/2008/08/beginners_mind, InfoQ, 2008
• Wynne, Matt and Aslak Hellesoy, The Cucumber Book: Behavior-Driven Development for Testers and Developers, Pragmatic Programmers, 2012
26