3. Agile Testing: A Practical Guide for Testers and
Agile Teams; Addison Wesley 2009
4. Copyright 2012: Lisa Crispin
Whole-Team Approach is:
• Meaningful commitment to quality
• Shared vision of product
• Diversity of skills, experience, viewpoint
5. Copyright 2012: Lisa Crispin
Is this rebellion?What’s rebellious here?
“Control is ultimately held by the doers”
7. Copyright 2012: Lisa Crispin
7
A Problem: User Mistakes
Users mis-type bank
account numbers =>
many phone calls for
Operations
8. Copyright 2012: Lisa Crispin
8
A solution: Dojo
Type-ahead select lists (& other features)
9. Copyright 2012: Lisa Crispin
A new problem
We want to help users avoid
mistakes, but we can’t have production
code that’s not protected by automated
tests
10. Copyright 2012: Lisa Crispin
Looking to the future…
Dojo would improve UX on our
new UI…
Let’s research
possible
solutions.
15. Copyright 2012: Lisa Crispin
15
Proof of Concept with Geb
• Developers write tests for new
UI page
•Testers and sys admin
integrate tests into Jenkins CI
• Pros: developers more
involved in GUI test design
• Cons: Learning curve for
testers, result reporting
17. Copyright 2012: Lisa Crispin
17
Another bake-off
Robot Framework vs. Xebium
• Xebium uses FitNesse framework
• Robot Framework result reporting excellent
18. Copyright 2012: Lisa Crispin
18
Proof of Concept with RF
• Sys admin helps
install, integrate w/
Jenkins, customize test
results, example page objects
• Testers write tests for same
pages as Geb tests
• Friends help with Se 2
keywords
19. Copyright 2012: Lisa Crispin
Next Steps
Dojo training
Test design
& RF
training
Get started
in a good
direction
20. Copyright 2012: Lisa Crispin
Whole Team FTW!
• Team commitment to improve site
• Sys admin, architect, developers, testers,
DBAs all worked on experiments
• Gave us confidence to experiment, find the
best solution for us
• We could go forward with plans to improve
UX, reduce user mistakes
21. Copyright 2012: Lisa Crispin
Another Experiment, Another Team:
API Automation
•Team wants to do SBE/ATDD for API
•Also need better regression test coverage
22. Copyright 2012: Lisa Crispin
Slightly different approach
•Tester/dev pair spiked 1 week
•Presented results to team
•Consensus – too much overlap w/ existing
tests
Should
have
23. Copyright 2012: Lisa Crispin
Second automation spike
• API console
• Team consensus –
explore, enhance, expand
• Spike for doc generation
• Team consensus – go with it
• Continue to build on strategy
24. Copyright 2012: Lisa Crispin
Tips for Experimenting
•Divide and conquer
•Sub-teams
•Time boxed
•Pros and Cons
•Pof concept
•Rinse and repeat
25. Copyright 2012: Lisa Crispin
Your experiences & ideas?
• Has your whole team pulled together to
solve a problem?
• Have you tried a “divide and conquer”
approach?
• Do you have problems that might be solved
more easily if people in multiple positions
helped?
30. Copyright 2012: Lisa CrispinCopyright 2008 Janet Gregory, DragonFire
30
Specification by Example
How successful teams deliver the right
software
Gojko Adzic
Case studies from > 50 teams
31. Copyright 2012: Lisa CrispinCopyright 2008 Janet Gregory, DragonFire
31
ATDD by Example
A practical guide to Acceptance Test-Driven
development
Markus Gaertner
32. Copyright 2012: Lisa Crispin32
All Proceeds to Charity!
Beautiful Testing: Leading Professionals Reveal How
They Improve Software
Edited by Tim Riley, Adam Goucher
Includes chapter by yours truly
Editor's Notes
Communication, Not “stepping on each other”,Pairing,Time zone differences,Staying motivated
From the OredevwebsiteReallystanding up for quality takes a ot of courage, Learning the biz domain takes a lot of workIt can be uncomfortable to work with other roles – may be way out of comfort zone. Anyone here already doing a whole team approach?18:05
Tell story of what pgmrs on my team said when we discussed what we’re looking for in a tester(explain why I say programmer instead of developer)
And this is a testing conference, so… But do try to educate your teammates about testing!18:10
And this is a testing conference, so… But do try to educate your teammates about testing!
They work together
They work together
And this is a testing conference, so… But do try to educate your teammates about testing!
I’m not trying to sell you on RF, or any other driver/framework. The point is that we tried different approaches til we found the optimal for us. This investment will pay off by allowing us to have maintainable regression tests, providing quick feedback & good ROI, which in turn allows us to implement a better UX.18:25
Tester/dev pair to spike: 1 weekPresent results at brown bagTeam consensus: too much overlap with Rspec controller tests?Lesson learned:Should have done a bake-off
Continue to find solutions for API automation strategy. Continued experiments and bakeoffs.18:30
