This document discusses testing in an Agile environment. It recommends that testing responsibilities be shared by the whole team, including business analysts, developers, and testers. Key practices include writing acceptance scenarios during "3 Amigos" meetings, conducting session-based exploratory testing, and maintaining a functional test map to facilitate automated regression testing. If these practices are followed, the outcomes will be a collaborative team, living documentation, automated tests, and a stable delivery process.

1. How To Manage Testing in
AGILE
World
v 1.1.1
Monday, October 7, 13
@adzynia

2. ANDRII DZYNIA
Test Engineer / Consultant /
Trainer
@adzynia
adzynia.com
Monday, October 7, 13

3. Idea
Monday, October 7, 13

4. Monday, October 7, 13

5. Monday, October 7, 13

6. Minimal Valuable
Product
Monday, October 7, 13

7. Monday, October 7, 13

8. Monday, October 7, 13

9. GO
Monday, October 7, 13
LIVE

10. AND ?
Monday, October 7, 13

11. Fixing bugs
Missing features
Angry Users
Lack of time
Monday, October 7, 13

12. Stress
Monday, October 7, 13

13. QA
Monday, October 7, 13

14. To
Monday, October 7, 13
be Responsible for
Quality
Write test plan
write test cases
do manual testing
automate testing

15. 2 Days Before Demo
To Do
User
Story
In Development
Code Review
Testing
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
Monday, October 7, 13
Demo

16. Outsource
testing?
Monday, October 7, 13

17. Oh no...
How it can be different?
Monday, October 7, 13

18. QA != Testing
Quality is whole team responsibility
Monday, October 7, 13

19. User
Story
BA
Monday, October 7, 13
Dev
Tester

20. User
Story
BA
Monday, October 7, 13
Dev
Tester

21. User
Story
BA
Monday, October 7, 13
Dev
Tester

22. User
Story
BA
Monday, October 7, 13
Dev
Tester

23. User
Story
BA
Monday, October 7, 13
Dev
Tester

24. User
Story
BA
Monday, October 7, 13
Dev
Tester

25. User
Story
BA
Monday, October 7, 13
Dev
Tester

26. User
Story
BA
Monday, October 7, 13
Dev
Tester

27. Look for consensus!
not compromise
WIN/lose
WIN/WIN!
lose/WIN
lose/lose
Monday, October 7, 13

28. Look for consensus!
not compromise
WIN/lose
WIN/WIN!
lose/WIN
lose/lose
Monday, October 7, 13

29. Business
Developer
Tester
3 Amigo’s Meeting
Monday, October 7, 13

30. Outcome
Acceptance Scenarios
Testing Checklist
Testability Tasks
Monday, October 7, 13

31. Scenarios Demo
https://github.com/adzynia/cucumber-jvm-scrum-test
Monday, October 7, 13

32. Monday, October 7, 13

33. Monday, October 7, 13

34. How to write
Acceptance Scenarios
Find more
at
adzynia.com
Monday, October 7, 13

35. But
Manual Testing
Is
Still Important !
Monday, October 7, 13

36. Checking != Testing
Monday, October 7, 13

37. Session Based Test
Management
VS
Test Cases Management
Monday, October 7, 13

38. Testing Session
should be:
Goal focused
Time-boxed
Reported
Debriefed
Monday, October 7, 13

39. Exploratory testing
Learning
Feedback
Design
Execution
Monday, October 7, 13

40. Regression
Testing
?
Monday, October 7, 13

41. Functional Map
Monday, October 7, 13

42. Release to
Production
should be
EASY
Monday, October 7, 13

43. At the End you will get
Friendly Team
Living Documentation
Automated Acceptance Scenarios
Functional Map
Testing Session Reports
Stable Delivery Pipeline
Monday, October 7, 13

44. Development flow
To Do
Acceptance Test
Design
User
Story
User
Story
In Development Code Review
User
Story
Testing
User
Story
Demo
User
Story
User
Story
User
Story
User
Story
Monday, October 7, 13

45. AND
Do not forget
about Balance
Control
Monday, October 7, 13
Ad-hoc

46. me
Em
@a
a il
dz
:
yn
ia.c
om
Monday, October 7, 13
@a
dz
yn
ad
zy
n
ia.
co
m
ia

47. To Read
Monday, October 7, 13