If a team believes they are agile but they test the same way as always, then there's still much to learn. Agile testing is fundamentally different to traditional testing. Are you one of those "walking death teams", with "agile development" but traditional testing? Do you want to become agile in testing too? As agile coaches in 233 Grados de TI, we help companies to adopt agile testing. In this talk we will present the most typical problems teams face in testing when they try to adopt Scrum, or agile values in general. We will also explain how we face similar situations and the experiences we have learnt changing from a traditional testing mentality to agile testing.

1. Agile Testing...
Or Walking Dead
Testing?

2. Are you ready for
the zombie
apocalypse?
is ready

3. How To Identify A Zombie
Testing Process, Kill It,
And Stay Alive

4. but we cannot launch
new functionalities
frequently
With productivity, time and happiness
“We are agile”,

5. But our clients
find lots of bugs
in production
environment
“We are agile”,

6. but testing
bottleneck
“We are agile”,
is always a

7. The following is a list of
traits that are common to
most zombie testing.
If Anything on this list
applies to you, it means
you are not an agile
testing TEAM.
Many average teams can
have all of these traits []

8. TESTING
IS ALSO ABOUT

9. PROCESS

10. Sprint 1 Sprint 2 Sprint 3
Development
Testing
Development
Testing
Development
Testing
Agile Development
But Waterfall testing

16. THREE FRIENDS RULE
DEVTESTER
PRODUCT
OWNER

17. PRODUCT
TECHNICAL ISSUES

18. Most repetitive
processes remain
being manual

19. Automate processes and
Testers should focus on
testing, not on making
environments stable
after deploys
optimize them as much as you
can

20. Not controlling
code quality generates
TECHNICAL DEBT

21. Agile testing means also
continuous inspection
and code refactoring

22. Code merges of
death

23. Continuous
integration

24. Continuous integration
does not only mean
using Jenkins

30. PEOPLE

31. Tes$ng
department
Development
department
Opera$ons
department
This is not an agile team

32. Agile Team = Cross-Functional Team
Developer
Tester
Developer
Tester Tester
Developer

33. Self-organized
team

34. Testing DepartmentDevelopment Department
Testing must not be
An External And
So Far
Department

35. Developers
Testers
More collaboration is
needed!

36. ¿Quality
records?
Traditional
Software
Quality: The
one in charge
of quality
and his
papers

37. Whole-team approach
of quality

38. The whole team
should promote
technical
excellence

39. Unit testing
Integration testing
Developers

40. Acceptance testing
Tester & PO

41. Exploratory testing
Regression testing
Test facilitator
Better communication
PO & DEV
Tester

42. Automated regression tests
Automated smoke tests
Load tests
Code static analysis
…

43. In order to survive,
Remember…

44. If you don’t control software
quality you will quickly
notice the consequences.
Your team will slow down,
you won’t be able to meet
sprint goals…

45. QUALITY AND TESTING
IS MUCH
MORE THAN
FUNCTIONAL
TESTING

46. *
From
Spo$fy
Engineering
Culture
–
Henrik
Kniberg

47. Cultural
challenge
for
the
company
Agile
tes$ng
=

48. Technical
challenge
Agile
tes$ng
=

49. @jgarzas
@amgarciao
Thank you!
Any questions?

50. Acknowledgements
• Thanks to MediaLoot.com for the Zombie icons,
and canva.com for vector resources