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.