What is AgileTesting all about? How does it affect teams? We go undercover to explore some teams in action. If you like what we have to say here and would like some more techniques - check our our book: https://leanpub.com/AgileTesting
To get exclusive access to a new techniques from us each month, sign up to our newsletter: http://bit.ly/W1dP3o
5. Scenario:
ACME Corporation has hired us to investigate this
“agile” thing.
Essentially we are spies.
We were tasked with sneaking around and seeing
how other companies do this agile thing -
particularly how it relates to testing...
6. ACME Corp. Concerns
How is agile testing different?
Are testers still responsible for
quality?
Do I still get to break things?
8. Agile Testing
Mindset
•testing vs checking
•defect prevention
•“I’m here to help create the best
product we can”
•quality is everyone’s responsibility
•testing is an activity
9. ACME Corp. Concerns
What do testers do at the start of
the sprint?
How do testers keep up?
We have a separate QA team, will
that work?
How many testers do we need, we
never have enough?
10.
11. Whole Team
Approach
•cross functional teams
•no magic
• 6 trumps... ratio
•testers are NOT plug & play
•
•whole team commitment
•sustainable pace
•role boundaries blur
12. ACME Corp. Concerns
How do developers and testers
work together?
How do we test before the whole
feature is complete?
Do tester’s have to be able to
code now?
14. Collaborat
ion by side
•work side
•• 6 trumps... understanding & ideas
test shared
•“how can I test that?”
•
•agree what to test before coding
•dev writes test fixture,
tester writes test case
•steel threads
17. Automa
tion
•automation != GUI
• use the pyramid
•automate regression & run it daily
•regression never finds new bugs
•creates time for exploratory
testing
•share the pain