The trend of Agile Software Development recently has raised the questions about testing activity. The Agile and principles always mention about teamwork, shorten the feedback time, inspect and adapt … but how about testing, how about the role of tester? Actually testing never become less importance even in an Agile Project. The only different is that Testing now is actually an activity, and not a phase. That why it is not “visible” in Agile project. The Scrum Breakfast Event this time will bring Agile Testing in to the table, helps us understand more about the new mindset of Testing activity and how we could maximize the benefit of testing base on Agile thinking. – Topic : AGILE TESTING – Speaker: Mr. Hai Dang – Branch Manager (Da Nang Branch – Axon Active Vietnam) If you are interested in this topic, please be invited to join our event.

1. THE AGILE TESTING
A new testing approach to success

5. Jenga Block Game

6. Build a castle

7. • Form a team about 7, select 1 tester
• Build a castle with at least 3 levels
• Use all the blocks
Build a castle

8. • Team build the whole structure and use all the blocks
• Tester come and verify the structure only after the whole
structure is built
• Tester point out problem blocks.
• The Team need to remove the problem blocks and make sure
the whole structure is still follow the requirement
5 minutes Sprint
Build a castle - Sprint 1

9. • Team build the whole structure and use all the blocks
• After every 12 blocks, tester can point out the problem blocks
• The Team need to remove the problem blocks, finish the
current 12 blocks and continue with the next 12 ones
5 minutes Sprint
Build a castle - Sprint 2

10. • Team build the whole structure and use all the blocks
• Tester is allowed to work with the developer as he is building
the structure and point out if he is using a problem block
5 minutes Sprint
Build a castle - Sprint 3

11. What can you see?

12. Arrange the blocks back to the box!
Sprint 4

20. Create the report
showing the
average sales data
for the last six
months

21. • If I run the report on 1 Feb is data from Feb included or not?
• What about if I run the report on 29 February?
• How exactly should the average calculated, as monthly average, or
the average over the six months?
• Does the average need to be stored or is it calculated on the fly?
• Does the report need to be stored, or will it only be created when
someone selects it?
• What field in the database is the average calculated from?
• Who would be using the report and why did they need it?

30. • Pair a team: 1 tester, the rest in the table is programmer
• Tester sit back to the team
• Tester get the drawing which need the team to replicated
• Programmer draws the shapes based on what tester
explained. No talking during “coding”
• Tester “tests” the drawing, report bugs on index card
• Programmers fix the “bugs”
Sprint 1 – 5 minutes
Drawing Game

31. • Collaborate!
• Tester tells programmer what to draw, watches the
programmer draw, answers questions, points out “defect” for
programmer to fix immediately
• Tester do not show the programmer the drawing
Sprint 2 – 5 minutes
Drawing Game

32. What can you see?