This document discusses testing mobile applications with entire development teams. It describes a meeting called Kakuninkai that the Cookpad iOS team holds to test new features by role-playing as different user types before public release. The goal is to uncover any unexpected behaviors or strange user experiences rather than just checking for broken features. Team members explain new features and are given 5-10 minutes each to test features by taking on personas like "evil users" or "edge case users".

1. Testing
with
the whole team
Tech Talk meet up #2
by Kazuaki Matsuo(@Kazu_cocoa)

2. Kazuaki Matsuo( @Kazu_cocoa)
🏢: Cookpad Inc.
Software Engineer in Quality / Test
Lang: / / /
Maintainer: Appium client libraries

3. Try!SwiftTokyo

4. Testing
with
the whole team

5. Testing
with
the whole team

6. Testing vs Checking

7. Testing vs Checking
http://www.satisfice.com/blog/archives/856

8. Testing vs Checking
Testing is the process of evaluating
a product by learning about it
through exploration and
experimentation, which includes to
some degree: questioning, study,
modeling, observation, inference, etc.
http://www.satisfice.com/blog/archives/856
by James Bosh, Testing vs Checking Refined

9. Testing vs Checking
Testing is the process of evaluating
a product by learning about it
through exploration and
experimentation, which includes to
some degree: questioning, study,
modeling, observation, inference, etc.
http://www.satisfice.com/blog/archives/856
by James Bosh, Testing vs Checking Refined

10. Testing vs Checking
Checking is the process of making
evaluations by applying algorithmic
decision rules to specific
observations of a product.
http://www.satisfice.com/blog/archives/856
by James Bosh, Testing vs Checking Refined

11. Testing vs Checking
Human Checking
Machine Checking
Human/machine Checking
http://www.satisfice.com/blog/archives/856
by James Bosh, Testing vs Checking Refined

12. Testing vs Checking
Human Checking
Machine Checking
Human/machine Checking
http://www.satisfice.com/blog/archives/856
by James Bosh, Testing vs Checking Refined

13. Testing
with
the whole team

14. Testing
with
the whole team

15. Two Cookpad iOS App

16. Japan and Global

17. Japan and Global

18. Structure
Android
Engineers
iOS
Engineers
Feature A
Group
Feature B
Group
Feature C
Group
Tech
Group

19. Feature Groups
Feature A
Group
Feature B
Group
Tech
Group
Feature C
Group

20. iOS
Engineers
Cross-group communities
Android
Engineers
Feature A
Group
Feature B
Group
Feature C
Group
Tech
Group

21. iOS
Engineers
the iOS team
Feature A
Group
Feature B
Group
Feature C
Group
Tech
Group

22. Testing
with
the whole team

23. Meetings
• Kick off
• Kakuninkai (in Japanese)
• Retrospective

24. Meetings
• Kick off
• Kakuninkai (in Japanese)
• Retrospective

25. What is Kakuninkai
Prevent releasing ios-cookpad with
unexpected behaviours
• features
• animatins/transitions
• user experiences
• …

26. Doesn’t aim to uncover defects such
as broken feature by checking.
Just testing and uncover something
strange.
What isn't Kakuninkai

27. For testing in Kakuninkai
• Explain new features and user story
• Time box
• 5~10 minutes for each features
• Roll playing game
• persona
• evil users
• edge case users
http://www.satisfice.com/blog/archives/856

28. For testing in Kakuninkai
• Explain new features and user story
• Time box
• 5~10 minutes for each features
• Roll playing game
• persona
• evil users
• edge case users
http://www.satisfice.com/blog/archives/856

29. For testing in Kakuninkai
• Explain new features and user story
• Time box
• 5~10 minutes for each features
• Roll playing game
• persona
• evil users
• edge case users
http://www.satisfice.com/blog/archives/856
Testing

30. Conclusion
• Testing and Checking
• our iOS team
• Testing with the whole team
• roll playing as some users

31. Thanks