-
Notifications
You must be signed in to change notification settings - Fork 4
Use Case 08: Cache a Story
jmalina edited this page Nov 15, 2013
·
1 revision
User Stories |
User Story 9
User Story 12 |
||
Participating Actors | User | ||
Goal | Cache a story | ||
Trigger | User clicks "Store in Favs" button. | ||
Precondition | The user is in the app and clicks on a story | ||
Postcondition | On success: The user can view the story offline. | ||
Basic Flow |
1 Open up the app 2 Go into the main screen. 3 From the main screen choose the story which you want to save (cache) on your device. This will bring you to the Story View screen 4 In the Story View screen in the top right corner drop-down menu choose "Save" (It does not matter what fragment your in, it will cache the entire story)(working title) |
||
Exceptions |
1. There is not enough memory to cache the story. The message will pop up and ask the user to delete some files and try again. |
||
Testing |
1. Open up the app 2. Which goes to the browse view. 3. From the browse view choose the story which you want to save (cache) on your device. This will bring you to the Story View screen 4. In the Story View screen in the top right corner drop-down menu choose "Store in Favs" (It does not matter what fragment your in, it will cache the entire story) 5. Verify that the story is saved on the device or an appropriate "story unable to be cached" message is displayed. The main resson this would fail is if there isn't enough room on the device. |