This document summarizes Janet Gregory's work promoting agile testing practices. It notes that she has been involved with agile teams since 2000 and has authored books and online courses on agile testing. The document discusses how testing should be a shared responsibility of the whole team. It emphasizes that testing provides feedback to improve quality, not just find bugs, and explains practices like examples, acceptance test-driven development, and exploratory testing that involve the whole team in testing activities.
%in Benoni+277-882-255-28 abortion pills for sale in Benoni
Testing is a team problem
1. Agile Testing Fellowship
Copyright 2020
Halton Agile/Lean Network
August 11, 2010
Janet Gregory @janetgregoryca
DragonFire Inc.
-- input from Lisa Crispin
2. first agile team about 2000
Agile Testing Condensed 2019
More Agile Testing 2014
Agile Testing 2009
Agile Testing Essentials video course 2017
Agile Testing for the Whole Team 3-day
course
Agile Testing for the Whole Team remote
facilitation
Agile Testing Fellowship, 2017
2
New!
3. @janetgregoryca
How the whole team working together
improves product quality
… and that testing activities
belong to the whole team
3
6. -- testing activities
“Accelerate the achievement of shippable quality”
-- a tester’s job Brent Jensen, 2011
6
Good testing ….
• provides information about the product through fast feedback loops
• is more than testing software
• is about learning about the product and what it can and can not do
8. @janetgregoryca
Excerpt from Agile Testing pg. 46
Several people we've talked to described the 'mini-waterfall'
phenomenon that often occurs when a traditional software
development organization implements an agile development process.
The organization replaces a six-month or year-long development cycle
with a two- or four-week one, and just tries to squeeze all of the
traditional SDLC phases into that short period."
8
9. @janetgregoryca
• an activity; not a phase (Elisabeth Hendrickson)
• interactive and starts from the beginning
• more than testing code
9
Potentially shippable
product
Potentially shippable
product
10. @janetgregoryca
10
• Think about the primary roles / specialties on your current
team?
• Are there specialties outside your team that help …or hinder
your team to achieve your quality goals?
• Are there dependencies on others? Share in the chat.
Example: and ops specialist to help with a test environment
issue.
13. @janetgregoryca
• Developers think about
testability
• Testers think about the big
picture and what ifs…
• Multiple skill sets mean
better solutions
13
14. @janetgregoryca
What makes it work?
• Commitment to a level of quality
➢ Identifying what’s valuable to customers
➢ Bug prevention over bug detection
➢ Fast response to prod issues
• Diverse perspectives, skill sets, biases
• Competencies > roles
19. @janetgregoryca
Expand the tests
Pair to discuss
automation
Create test
method(s)
Write the tests in
the automation
framework
Select a test
and run it
Repeat until all
tests have passed
Perform
exploratory
testing, and any
other testing
required for the
definition of
DONE.
Acceptance
Test(s)
TDD
20. @janetgregoryca
• Examples provide common language
• Shared common understanding
• Coding and testing concurrently
• Shared definition of DONE
• Prevents defects in code
20
21. @janetgregoryca
It’s not just about code !!!
◦ Test assumptions
◦ Uncover hidden assumptions
The goal:
◦ Shared common understanding of the story
◦ Preventing defects (eliminate waste)
24. @janetgregoryca
• Checking: Does the system do what
it's supposed to do?
• Exploring: Are there any other risks
or vulnerabilities that we haven't
thought about yet?
• Testing == checking + exploring
24
**Elisabeth Hendrickson, “The Two Sides of Software Testing”,
Agile Connection
GUI
API
Unit Tests
29. @janetgregoryca
Compile &
Unit Testing
Static
Analysis
Integration
Testing
GUI &
End to End
Testing
Exploratory
Testing
User
Acceptance
Testing
(UAT)
Perf Testing
Penetration
Testing
Deploy to
Production
Deploy to QA
Env
Deploy to
Staging
Env
Deploy to
Stress Env
Deploy to
Security Env
Testing is the of DevOps
Original example from Ashley Hunsberger and Lisa Crispin
Observe &
monitor
Question &
get examples
31. @janetgregoryca
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
product successfully!
31
32. @janetgregoryca
Instead of
We’re here to code and throw it over the
wall and then fix bugs
Think
What can I do to help create testable code
and deliver the product successfully!
32
33. @janetgregoryca
Instead of
We’re here to tell you what we want,
and you just do it.
Think
How can I work with the development
team to deliver the product
successfully?
33
34. @janetgregoryca
Testers are NOT responsible for
quality, the whole team is
Programmers do not code alone …..
everyone helps them understand what to code
36. @janetgregoryca
Building a quality culture
• Transformative leaders
• Trust and psychological safety
• Focus on quality, not speed
Teams and organizations talk about what level of quality they
desire, and everyone knows how they contribute to the quality of
the product.
37. @janetgregoryca
• https://janetgregory.ca/blog/ A four-part series on testing and quality
• https://agiletester.ca
• lisacrispin.com
• Hendrickson, Elisabeth, Explore It! Reduce Risk and Increase Confidence
with Exploratory Testing, Pragmatic Programmer, 2013
• Knight, Adam P., "T-shaped Tester, Square Shaped Team",
http://thesocialtester.co.uk/t-shaped-tester-square-shaped-team/, 2013
• Agile Testing Condensed, A Brief Introduction, LeanPub and Amazon
• Agile Testing and More Agile Testing, Amazon
37
38. @janetgregoryca
Agile Testing Condensed: A Brief Introduction)
More Agile Testing: Learning Journeys for the Whole Team
Agile Testing: A Practical Guide for Testers and Agile Teams
Essential Agile Testing 5 hour video course
agiletester.ca
agiletestingfellow.com
Twitter: janetgregory.ca
LinkedIn: janet_gregory
Email: janet@agiletester.ca
38
