testing of fitbit web appli · pdf file target audience target audience of fitbit application...
Click here to load reader
Post on 10-Jul-2020
Embed Size (px)
Testing of Fitbit web application
Oshmarina Daria firstname.lastname@example.org
A4B39TUR CVUT FEL 2015
Description of the application Target Audience Use cases outline Use case 1: see how many steps user walked yesterday Use case 2: add information about sleep in case user didn’t wear fitbit tracker when he went to bed Use case 3: see earned badges Use case 4: add new alarm Use case 5: customize tracker display to show only clock and distance Methods of testing Cognitive Walktrough Heuristic Evaluation Testing use cases
Use case 1: see how many steps user walked yesterday Use case 2: add information about sleep in case user didn’t wear fitbit tracker when he went to bed Use case 3: see earned badges Use case 4: add new alarm Use case 5: customize tracker display to show only clock and distance Discoveries
Description of the application Fitbit web application shows users information that the fitbit activity tracker measures such as number of steps done during the day and in certain hours, distence walked, floors climbed, calories burned. It also shows a sleep pattern, that is hours alseep and times awakened. Application allows user customize display of fitbit device, e.g. hiding and showing items(steps, distance, time), change order of these items on diaplay. User can set daily goal, e.g. 10000 steps and user will be notified when reaching the goal. There is an ooportunity to set an alarm and then device will wake user up. One more nice feature is badges user earns for activities.
image 1: screenshot of the application
Target Audience Target audience of fitbit application is fitbit activity tracker users. Age of users doen’t really matter. Assume that these people feel comfortable with technologies.
Use cases outline 1. See how many steps user walked yesterday. 2. Add information about sleep in case user didn’t wear fitbit tracker when he went
to bed. 3. See earned badges. 4. Add new alarm. 5. Customize tracker display to show only clock and distance.
Use case 1: see how many steps user walked yesterday Steps is one of the main metrics that fitbit device measures. Application shows user information about number of steps done during the day. User can choose particular date and see how many steps were walked that day. Showing users their steps is a way to motivate people to be more physically active. It shouldn’t be a problem for user to find information about steps.
Use case 2: add information about sleep in case user didn’t wear fitbit tracker when he went to bed Fitbit application also allows users to add information about their activities in case tracker wasn’t worn. We will test adding information about sleep.
Use case 3: see earned badges For activity achievements users earn badges. E.g. for walking 112 kilometres user earns “Penguin March Badge”(image 2). Application shows user earned badges and gives information what user achieved to get the badge.
Image 2: “Penguin March Badge”
Use case 4: add new alarm User can set up an alarm and device will wake him up. This use case is not about viewing metrics. So probably user can be a bit lost while finding where actually he can set up an alarm.
Use case 5: customize tracker display to show only clock and distance User can customize tracker display the way he like more. Device with default settings shows user current time, steps and distance walked, calories burned and floors climbed during the day. Different users set different goals. E.g. user want to see only what time is it and what distance he walked today.
Methods of testing
Cognitive Walktrough Cognitive Walkthrough is a method of testing user interface without user. When start testing use case we answer question Q0: “What does the user want to achieve?” To determine level of usability of application we will go through use case step by step and at each step we raise and answer three questions: Q1: “Will the correct action(s) be evident to the users?” Q2: “Will the users connect the label of an action with their goals?” Q3: “Will the user receive a sensible feedback?"
Heuristic Evaluation Heuristic Evaliation is a method of testing that identifies usability problems in UI design. This method uses set of 10 heuristics written by Jakob Nielsen. Application is tested if it follows these heuristics. List of heuristics:
H1: Visibility of system status
H2: Match between system and the real world
H3: User control and freedom
H4: Consistency and standards
H5: Error prevention H6: Recognition rather than recall H7: Flexibility and efficiency of use H8: Aesthetic and minimalist design H9: Help users recognize, diagnose, and recover from errors
H10: Help and documentation
Testing use cases Initial state: Application shows user today’s metrics. (image 5)
Image 5: screenshot of initial state
Use case 1: see how many steps user walked yesterday Q0: What is user trying to achieve? Answer: User wants to see how many steps he walked yesterday.
Steps Answers to questions Comments
Step 1: Move mouse over the button with calendar icon (image 3).
Q1: Yes Q2: Yes Q3: No
User expect calendar to open when moving mouse over the button with calendar icon. H4 is breached. Discovery D1.
Step 2: Press “
Image 3: Button in normal state Image 4: Button in hover state Final state: Application shows user yesterday’s step counts (image 6).
Image 6: screenshot of final state Summary: User will not be lost when finding where to chose date, calendar icon hints that date can be changed here. But user expects that window with calendar will open and there he can choose the day. So H4: Consistency and Standards is breached. What if user wants to see how many steps he walked on e.g. February 13 (Assume that now is March)? He should press “
Use case 2: add information about sleep in case user didn’t wear fitbit tracker when he went to bed Q0: What is user trying to achieve? Answer: User forgot to wear tracker when went to bed and now wants to log sleep information.
Steps Answers to questions
Step 1: Click on “Log” in the top menu(image 7).
Q1: Yes Q2: No Q3: Yes
Step 2: Click on “Sleep” tab(image 8) Q1: Yes Q2: Yes Q3: Yes
Step 3: Enter data(image 8) Q1: Yes Q2: Yes Q3: Yes
Step 4: Press “Log” button Q1: Yes Q2: Yes Q3: Yes
Final state: Application tells user that “Sleep record was added to the list below”. This is actually what user wanted (image 9).
Image 7: Log tab
Image 8: Sleep tab
Image 9: application’s feedback on last step
Summary: One problem for user can be to find out what should he click first to add information of sleep. After finding “Log” tab in menu all actions are evident for users and user always gets feedback.
Use case 3: see earned badges
Q0: What is user trying to achieve? Answer: user wants to see badges he earned for activity achievements
Steps Answers to questions Comments
Step 1: Scroll page to find badges tile on dashboard (image 10)
Q1: No Q2: No Q3: Yes
User is not sure if there is badges tile on dashboard or information about badges is in user’s profile
Step 2: Click on tile with badges (image 11)
Q1: Yes Q2: Yes Q3: Yes
Step 3: Click “See more” button (image 12)
Q1: Yes Q2: Yes Q3: Yes
Image 10: badges tile
Image 11: opened tile with badges
Image 12: page with user’s badges Summary: User