O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.
Janet Gregory, DragonFire Inc.
Copyright 2014
Knowit, Helsinki
2014
Copyright 2014
DragonFire Inc.
First agile team – 2000
Currently – coaching, testing
Agile Testing; January 2009
Working o...
Copyright 2014
DragonFire Inc.
• Testing and agile
• Challenges and suggestions
• Importance of collaboration
• Wrap-up
3
Copyright 2014
DragonFire Inc.
• have short feedback loops
• active customer participation
• demand whole team collaborati...
Agile teams:
produce a continuous stream of value at
a sustainable pace, while adapting to the
changing needs of the busin...
Copyright 2014
DragonFire Inc.
• more than “just” testing code
• an activity; not a phase
6
Potentially shippable
product
...
Copyright 2014
DragonFire Inc.
1. Testing doesn’t keep up with coding
2. Forgetting the big picture
3. Testers aren’t real...
Copyright 2014
DragonFire Inc. 8
Risk: The Mini-Waterfall
10
• Stories aren’t tested completely
• Testers lose credibility
• Technical debt increases
• Team changes meaning of ‘DON...
Copyright 2014
DragonFire Inc.
• Include testing tasks in the velocity
• Involve whole team in story creation
◦ ensure sto...
Copyright 2014
DragonFire Inc.
• Know your build pipeline
• Provide adequate test infrastructure
12
Copyright 2014
DragonFire Inc.
Instead of saying NO,
or being the gatekeeper
Be the information provider so
business can m...
Copyright 2014
DragonFire Inc.
The red flags
• Testing only individual stories
• Finding integration bugs late
• Testing i...
Copyright 2014
DragonFire Inc.
We only see the tip of the Iceberg
We don’t think of big systems
We only looking at our own...
Copyright 2014
DragonFire Inc.
• Think system impacts
• Test data to reflect real world
◦ Examples, exploratory tests
• Dr...
Copyright 2014
DragonFire Inc. 17
Copyright 2014
DragonFire Inc.
• Define “Release DONE”
◦ What needs to be in place?
• Define “Feature DONE”
◦ Acceptance t...
Understand the business value !
ATDD (Acceptance Test Driven Development)
Copyright 2014
DragonFire Inc.
Instead of saying NO,
or being the gatekeeper
Be the information provider so
business can m...
Copyright 2014
DragonFire Inc.
• Testers aren’t in iteration planning sessions
• Testers test what the developers code
• T...
• Wrong assumptions are made
• Impacts to the system are found too late
• Everyone’s skills are not utilized
• The team be...
Copyright 2014
DragonFire Inc.
• Communication is through the
defect tracking system
• Developers use testers as a
safety ...
26
Tips for Tester Involvement
Copyright 2014
DragonFire Inc. Copyright 2009 Janet Gregory, DragonFire 27
The Agile Testing Quadrants (adapted from Brian...
Copyright 2014
DragonFire Inc.
Instead of saying NO,
or being the gatekeeper
Be the information provider so
business can m...
Copyright 2014
DragonFire Inc.
• Spending time retesting features already tested
• Not testing new features
• Not contribu...
Copyright 2014
DragonFire Inc.
• Testing cannot keep up with new stories
• Features that used to work, are broken and
not ...
Copyright 2014
DragonFire Inc.
• Automate as you go
• Include automation time in your estimates
• Design for testability
•...
Common automation model
Automation
through the
GUI
Unit Tests
push
the
tests
lower
34
“Living
Documentation”
David Evans, Gojko Adzic
Copyright 2014
DragonFire Inc. 35
**Automation does not
exclude the need for
exploratory testing*
Copyright 2014
DragonFire Inc.
Instead of saying NO,
or being the gatekeeper
Be the information provider so
business can m...
Copyright 2014
DragonFire Inc.
• Can’t “test quality in”
• Whole team thinks testing
• Team is committed to quality
• Whol...
Copyright 2014
DragonFire Inc.
Agile testing is full of challenges
• Problems happen faster, so impact is felt faster
• Be...
Copyright 2014
DragonFire Inc.
Agile Testing: A Practical Guide for
Testers and Agile Teams
By Lisa Crispin and Janet Greg...
Copyright 2014
DragonFire Inc.
• www.lisacrispin.com
• agile-testing@yahoogroups.com
• www.testobsessed.com (heuristics ch...
Janet Gregory - Agile testing challenges Knowit 2014
Próximos SlideShares
Carregando em…5
×

Janet Gregory - Agile testing challenges Knowit 2014

1.351 visualizações

Publicada em

Janet Gregory's presentation at Knowit's Agile testing challenges -seminar 22.5.2014

Publicada em: Software, Tecnologia
  • Seja o primeiro a comentar

Janet Gregory - Agile testing challenges Knowit 2014

  1. 1. Janet Gregory, DragonFire Inc. Copyright 2014 Knowit, Helsinki 2014
  2. 2. Copyright 2014 DragonFire Inc. First agile team – 2000 Currently – coaching, testing Agile Testing; January 2009 Working on 2nd book: Fall 2014 2
  3. 3. Copyright 2014 DragonFire Inc. • Testing and agile • Challenges and suggestions • Importance of collaboration • Wrap-up 3
  4. 4. Copyright 2014 DragonFire Inc. • have short feedback loops • active customer participation • demand whole team collaboration • test features as they are coded • deliver business value at regular intervals • adapt their processes based on feedback …and so on………….
  5. 5. 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/
  6. 6. Copyright 2014 DragonFire Inc. • more than “just” testing code • an activity; not a phase 6 Potentially shippable product Potentially shippable product
  7. 7. Copyright 2014 DragonFire Inc. 1. Testing doesn’t keep up with coding 2. Forgetting the big picture 3. Testers aren’t really part of the team 4. Trying to test everything manually 7
  8. 8. Copyright 2014 DragonFire Inc. 8
  9. 9. Risk: The Mini-Waterfall
  10. 10. 10 • Stories aren’t tested completely • Testers lose credibility • Technical debt increases • Team changes meaning of ‘DONE’
  11. 11. Copyright 2014 DragonFire Inc. • Include testing tasks in the velocity • Involve whole team in story creation ◦ ensure stories are small and testable • Get your developers used to immediate feedback 11
  12. 12. Copyright 2014 DragonFire Inc. • Know your build pipeline • Provide adequate test infrastructure 12
  13. 13. Copyright 2014 DragonFire Inc. Instead of saying NO, or being the gatekeeper Be the information provider so business can make the decisions Questions… about not testing stories 13
  14. 14. Copyright 2014 DragonFire Inc. The red flags • Testing only individual stories • Finding integration bugs late • Testing is based on what developers code • Testing finds requirements type bugs • Developers add extra code after they are finished 14
  15. 15. Copyright 2014 DragonFire Inc. We only see the tip of the Iceberg We don’t think of big systems We only looking at our own team. The Risks 15
  16. 16. Copyright 2014 DragonFire Inc. • Think system impacts • Test data to reflect real world ◦ Examples, exploratory tests • Draw pictures / workflows • Understand the story before coding starts 16
  17. 17. Copyright 2014 DragonFire Inc. 17
  18. 18. Copyright 2014 DragonFire Inc. • Define “Release DONE” ◦ What needs to be in place? • Define “Feature DONE” ◦ Acceptance tests for bigger picture • Define “story DONE” ◦ Acceptance tests – expected behaviour, misbehaviours 18
  19. 19. Understand the business value !
  20. 20. ATDD (Acceptance Test Driven Development)
  21. 21. Copyright 2014 DragonFire Inc. Instead of saying NO, or being the gatekeeper Be the information provider so business can make the decisions Questions… Remembering the Big Pic? 22
  22. 22. Copyright 2014 DragonFire Inc. • Testers aren’t in iteration planning sessions • Testers test what the developers code • Testers don’t understand the stories Testers don’t actively participate 23
  23. 23. • Wrong assumptions are made • Impacts to the system are found too late • Everyone’s skills are not utilized • The team becomes divided • Testers don’t know what is going on
  24. 24. Copyright 2014 DragonFire Inc. • Communication is through the defect tracking system • Developers use testers as a safety net • The team never ‘gels’ 25 • Project team doesn’t buy the ‘build quality in’ concept
  25. 25. 26 Tips for Tester Involvement
  26. 26. Copyright 2014 DragonFire Inc. Copyright 2009 Janet Gregory, DragonFire 27 The Agile Testing Quadrants (adapted from Brian Marick)
  27. 27. Copyright 2014 DragonFire Inc. Instead of saying NO, or being the gatekeeper Be the information provider so business can make the decisions Questions about whole team? 28
  28. 28. Copyright 2014 DragonFire Inc. • Spending time retesting features already tested • Not testing new features • Not contributing to implementation / design discussions 29 • Testers miss meetings – too busy • Regression suite not run regularly
  29. 29. Copyright 2014 DragonFire Inc. • Testing cannot keep up with new stories • Features that used to work, are broken and not noticed • Testers don’t learn new technology • Testers get stuck in a rut 30
  30. 30. Copyright 2014 DragonFire Inc. • Automate as you go • Include automation time in your estimates • Design for testability • Chose tools that encourage collaboration • Understand the power & risks of automation 31
  31. 31. Common automation model Automation through the GUI Unit Tests
  32. 32. push the tests lower
  33. 33. 34 “Living Documentation” David Evans, Gojko Adzic
  34. 34. Copyright 2014 DragonFire Inc. 35 **Automation does not exclude the need for exploratory testing*
  35. 35. Copyright 2014 DragonFire Inc. Instead of saying NO, or being the gatekeeper Be the information provider so business can make the decisions Questions… Automation? 36
  36. 36. Copyright 2014 DragonFire Inc. • Can’t “test quality in” • Whole team thinks testing • Team is committed to quality • Whole team solves problems • Everyone collaborates 37
  37. 37. Copyright 2014 DragonFire Inc. Agile testing is full of challenges • Problems happen faster, so impact is felt faster • Be courageous – be a change agent • Adapt, Learn Mostly, have fun and enjoy the challenge! 38
  38. 38. Copyright 2014 DragonFire Inc. Agile Testing: A Practical Guide for Testers and Agile Teams By Lisa Crispin and Janet Gregory www.agiletester.ca Contact info www.janetgregory.ca Email: janet@agiletester.ca Twitter: janetgregoryca 39
  39. 39. Copyright 2014 DragonFire Inc. • www.lisacrispin.com • agile-testing@yahoogroups.com • www.testobsessed.com (heuristics cheat sheet) • Gojko Adzic, Specification by Example, 2011, Bridging the Communication Gap, 2009, Impact Mapping 2013 • www.stickyminds.com/ Pragmatic Personas - Jeff Patton’s weekly column 1/25/2010 • www.mountaingoatsoftware.com – Mike Cohn’s web site • http://www.exampler.com - Brian Marick’s web site • Ester Derby and Dianne Larsen, Agile Retrospectives • Agile Manifesto: http://agilemanifesto.org/ • Mary Poppendieck and Tom Poppendieck, Lean Software Development, Addison-Wesley (series of 3) • Photos – Janet’s vacations or Microsoft office 40

×