You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a PO, I want to make sure the whole history + favorites screen functionalities work as expected so that the user can have a good experience without bugs.
Testing/Acceptance criteria
This screen has two tabs: "All" and "Favorites"
By default, the content in the "All" tabs is displayed when the user comes to this screen.
The "All" tab has a list view of all the activity sessions that the user has played.
This information is displayed in a card form with the name of the activity, the date-time of when this activity started and 2 icon buttons.
The first button has a heart icon and when clicked, the heart icon is filled and the activity is added to favorites.
The second button has a replay icon and when clicked, the app will automatically start the playtime session using this activity's configuration (no onboarding questions needed).
The "Favorites" tab has a list view of all the activity sessions that the user has saved to favorites.
This information is displayed in a card form with the name of the activity, the date-time of when this activity started, and 3 icon buttons.
The first button has a heart icon that is filled by default and when clicked, the heart icon is unfilled and the activity is removed from favorites and removed from display in this view.
The second button has a replay icon and when clicked, the app will automatically start the playtime session using this activity's configuration (no onboarding questions needed).
The third button has an edit icon and when clicked, a popup modal shows where the user can edit some of the configurations for this saved activity.
In the popup modal, the user can edit the activity name, the activity duration and energy level.
When the user clicks Save/Update button in the popup modal, these changes are saved for this activity.
Notes
This issue needs 2 developers to test all the above scenarios on both Android and iOS.
Nice to have: a short report on what testing scenarios failed and what passed posted in Discord dev channel
The text was updated successfully, but these errors were encountered:
User Story
As a PO, I want to make sure the whole history + favorites screen functionalities work as expected so that the user can have a good experience without bugs.
Testing/Acceptance criteria
This screen has two tabs: "All" and "Favorites"
By default, the content in the "All" tabs is displayed when the user comes to this screen.
The "All" tab has a list view of all the activity sessions that the user has played.
This information is displayed in a card form with the name of the activity, the date-time of when this activity started and 2 icon buttons.
The first button has a heart icon and when clicked, the heart icon is filled and the activity is added to favorites.
The second button has a replay icon and when clicked, the app will automatically start the playtime session using this activity's configuration (no onboarding questions needed).
The "Favorites" tab has a list view of all the activity sessions that the user has saved to favorites.
This information is displayed in a card form with the name of the activity, the date-time of when this activity started, and 3 icon buttons.
The first button has a heart icon that is filled by default and when clicked, the heart icon is unfilled and the activity is removed from favorites and removed from display in this view.
The second button has a replay icon and when clicked, the app will automatically start the playtime session using this activity's configuration (no onboarding questions needed).
The third button has an edit icon and when clicked, a popup modal shows where the user can edit some of the configurations for this saved activity.
In the popup modal, the user can edit the activity name, the activity duration and energy level.
When the user clicks Save/Update button in the popup modal, these changes are saved for this activity.
Notes
This issue needs 2 developers to test all the above scenarios on both Android and iOS.
Nice to have: a short report on what testing scenarios failed and what passed posted in Discord dev channel
The text was updated successfully, but these errors were encountered: