These are thes slides I used during my workshop on both Freetest (Norway) and TestNet (Netherlands). Both Mobile and Traditional Testing benefits by having a clear and solid test strategy that can be explained to the stakeholders, and that enables us to tell a test story that aligns with that strategy. Rather than communicating lists of bugs and passed test cases, we need a language to explain or stakeholders how we perceive the application or App that we test. What language do we use, how do describe the application? What language do we use when we want to express our experience with the application that we have just tested. In this hands-on workshop we will seek words to do so. We will use the analogy of the coffee taste wheel to draw up our own Testers taste wheel. In coffee land (but also in whiskey land) they use a taste wheel to describe tastes that you can look for while sampling the coffee. It serves as a kind of checklist, but also helps to give names to the flavors. It provides a language that is commonly understood among the tasters. The coffee taste wheel displays both the disqualifiers (bad tastes like burned, to bitter, etc) and the nice flavors (the qualifiers) of the coffee. An example of the coffee taste wheel can be found in the slides. The set-up of the taste wheel can be quite beneficial as basis of test process that aligns with the information need of the stakeholders. In this workshop groups of testers will explore a few sample Apps on their mobile device or laptop. Their mission will be a) Defining the qualifiers and disqualifies of the application, using the KANO model, b) Execute some testing and c) Report verbally towards the other teams about they way they perceive the application. Based upon the reports, we will model our own testing taste wheel.

1. Taste wheel for testers…
Workshop Freetest (Norway) Testnet (Netherlands)
May 2014
Derk-Jan de Grood
1

2. Introduction
Bridge the gab
Find some shared language
Experiment: build our own flavor wheel for testers
Do some exploratory testing
Find what is needed to be the quality ambassador
2

3. My Passion

4. Key Problem
4

5. 5

6. Testing What’s app
6
Define items you want to test
Distribute tasks
Execute tests
Prepare your test story
10 min
10 min

7. Reporting
7

8. Did you take into account
Different kind of users, or persona’s ?
8

9. Qualifiers
10

10. Disqualifiers
11

11. 12

12. Check vs Test
Check
Test
13
Exploratory
Scripted

13. 3 step strategy
Persona’s Qualifiers Disqualifiers
14

14. TestNet Network test
15

15. The flavor wheel
Where my passions meet
16

16. 17
Generic
Qualifiers
Shows like
Dis-
Qualifiers

17. 18

18. Simplified
19
Generic
Qualifiers
Shows like
Dis-
Qualifiers

19. Benefits
Checklist what could we test
Involve stakeholders
Find common language
Focus on the right things
Have a good test story
Show your added value
20

20. Lets compose our own flavour wheel
The experiment
21

21. 22
1 Define Persona’s

22. 23
2 Define Qualifiers
Format:
As Person I Goal, because single
attribute
Example
As end user I trust the system, because I
know my private data is not shared over
the internet

23. Put them on the board
24

24. Different stakeholder have same
goals…
As a <partner> I <enjoy> my girlfriend because
see can cook a good diner
As a <partner> I <mistrust> my girlfriend
because she likes the neighbor
As a <brother> I <enjoy> my sister because see
can cook a good diner
As a <neighbor> I <enjoy> my neighbor
because …
25

25. Counting
26

26. First drafts
27
Freetest- Norway
TestNet- Netherlands

27. Persona’s
28

28. Put to practice
29

29. Remember the case
Pick a qualifier
How could you test it?
What would you communicate?
30

30. Product Demo
31

31. Review (static tests)
32

32. Tell a appealing test story
33

33. 34
WRAP-UP

34. Wrap up
Check vs Test
Check
Test
12
Explotatory
Scripted
`````````````

35. Derk-Jan de Grood
Valori
Coltbaan 4a
3439 NG NIEUWEGEIN
The Netherlands
derkjandegrood@valori.nl
+31(0)651807878
www.valori.nl
Blog: http://djdegrood.wordpress.com
Twitter: @DerkJandeGrood