6. Verification - Pug-Life-INFO-461/allowance-gamification-app GitHub Wiki
Verifications will be tested before each commit and after integrating new components into our application. When acomponent is done or assistance is requested on implementation issues, the person responsible should notify theteam by sending a message on our Facebook messenger group. Any request for assistance about certain areas incode, the responsible team member will tell the team where to refer in the Github repo or send a code snippetin our #pug_life channel to get more specific help. Team members will respond back on messenger to verify thatcomponents are verified. In weekly meetups, a summary of development work will be held and any additional verificationthat has not been completed will be verified here. Following this system will allow us as a team to verify thatour requirements for this application have been completed and function as expected.
The tests will go in the order listed. Once the steps of test are verified or have failed, the testing environmentwill be reset. The test user account and the family group created in Firebase will be removed. This is requiredto create an account with the same email and password repeatedly. When the family group is deleted, all the subtasks and rewards will also be removed.
User - Both Child user and Parent user
Parent - Parent user, has admin privileges, can create and delete tasks and rewards.
Child - Child User, limited privileges, can only accept tasks and redeem rewards
Requirements |
Verification |
User must be able to click anywhere in the input fields (email, password, full name, family name)and type anything. |
|
There will be placeholder text in all input fields when the user has not typed anything. The fullname input field will have “first and last name”, the group name input field willhave “group name”, email input field will have the placeholder: “ [email protected] ”, the password input field will have the placeholder: “password” |
|
Below the input field for full name, there will be radio buttons for selected the type of user (parentor child). None of them are checked at first, but pressing on one of them will fill the radiobutton with blue color. Only one of them can be filled in at a time. |
|
When there is text typed into the input fields, the placeholder text should disappear. The replacedtext should be whatever the user has typed in. |
|
If the input fields are emptied when the user deletes all of its contents (e.g. hitting the backspaceto delete all text), then the placeholder text in the input fields reappear. |
Case 1: Variable Backspace
Case 2: Delete all characters at once
|
When all valid inputs are correct, pressing the create button will start up the spinner (shows verifyingbuffering time) and will display the task view and the task tab will be highlighted on the bottomnavigation bar. |
|
If nothing is entered into the input fields and the create button is pressed, red text should appearnotifying users which input fields are not completed (or invalid) or none of them are filledout. |
Case 1: User is missing an input
Case 2: User is missing all input fields (Full name, family name, email, and password)
Case 3: User has inputted invalid input field (email)
|
Requirements |
Verification |
User must be able to click anywhere in the input fields (email and password) and type anything. |
|
There will be placeholder text in all input fields when the user has not typed anything. The emailinput field will have the placeholder: “ [email protected] ” and the password input field will have the placeholder: “password” |
|
When there is text typed into the input fields, the placeholder text should disappear. The replacedtext should be whatever the user has typed in. |
|
If the input fields are emptied when the user deletes all of its contents (e.g. hitting the backspaceto delete all text), then the placeholder text in the input fields reappear. |
Case 1: Variable Backspace
Case 2: Delete all characters at once
|
When login credentials are correct, pressing the login button will start up the spinner (shows verifyingbuffering time to authenticate) and will display the task view and the task tab will be highlightedon the bottom navigation bar. |
* Pre Requirement : There must be an account id: “ [email protected] ” pw: “123456”
|
When login credentials are incorrect (properly filled email but non incorrect input), pressing thelogin button will start up the spinner (shows verifying buffering time to authenticate) and thespinner disappears which then displays red text to notify the user that the authentication hasfailed. The user stays on the sign in page and the red text disappears. |
*Pre Requirement : There must be an account id: “ [email protected] ” pw: “123456”
|
When login credentials are typed incorrectly (invalid filled email), pressing the login button willstart up the spinner (shows verifying buffering time to authenticate) and the spinner disappearswhich then displays red text to notify the user that “You have entered an invalid emailaddress”. The user stays on the sign in page and the red text disappears. |
*Pre Requirement : There must be an account id: “ [email protected] ” pw: “123456”
|
If nothing is entered into the input fields and the login button is pressed, red text should appearnotifying users which input fields are not completed or none of them are filled out. |
Case 1: User is missing an input to login
Case 2: User is missing both input fields (email and password)
|
Requirements |
Verification |
User can log out and return to sign-in page |
*Pre Requirement : There must be an account id: “ [email protected] ” pw: “123456”
|
Requirements |
Verification |
User is able to view user profile |
*Pre Requirement : There must be a user created and logged in
|
User is able to edit user profile |
*Pre Requirement : There must be a user created and logged in
|
Requirements |
Verification |
User must be able to change views by clicking on the different icons |
Case 1: User is on “Rewards” tab and switches views to the “Task” tab
Case 2: User is on “Task” tab and switches views to the “Rewards” tab
|
Requirements |
Verification |
For creating tasks parents click the Add sign ‘+’ which takes them to a form to fill out: |
*Pre condition: Parent have to be in Task tab in the bottom navigation
|
Parent is able to Click ‘edit’ to edit task |
*Pre condition: Parent have to be in Task tab in the bottom navigation, one or more task is already created and displayedon the task list
|
Parent is able to Click ‘delete’ to delete task |
*Pre Requirement : There must be one or more tasks created.
|
View Task Details |
*Pre Condition : There must be one or more tasks that are already created
|
If there are more tasks on the screen, the parent is able to scroll on the list and view more tasks |
|
Tasks that are accepted by child will be moved to In Progress tab |
*Pre Condition : There must be one or more tasks that are already created
|
Once child completes the tasks on their end, the completed tasks will be moved to Completed tab in Parents view |
*Pre Condition : There must be one or more tasks that are already created
|
Requirements |
Verification |
View Task Details |
* Pre Requirement : There must be one or more tasks created.
|
If there are more tasks on the screen, the user is able to scroll on the list and view more tasks |
|
Child can Accept a Task |
*Pre condition: There must be one or more task created to choose from.
|
Child can only Accept one task at a time |
* Pre Requirement : There must be one or more tasks created.
|
Once a child Accepted a task it will disappear from available task list view |
*Pre Requirement : There must be one or more tasks created with name “task 1”.
|
A child can mark task as ‘ completed’ while in ‘ In Progress ’ mode |
*Pre Requirement : There must be one or more tasks created.
|
A child can cancel in progress task while in ‘ In Progress’ mode |
*Pre condition: a task has to be accepted and user has to be ‘ In Progress” mode
|
Completed tasks will be moved to Completed tab |
*Pre condition a task has to be in ‘In progress’ mode.
|
Child is only able to see all the tasks completed by him/herself |
*Pre condition a task has to be completed by Child1 Case 1 - There is completed task
Case 2 - There is no completed task
|
Child receive points automatically after completing the task |
*Pre condition there need to be a task and that task has to be opened in ‘In progress’ mode.
|
Requirements |
Verification |
For creating reward parents click the Add sign ‘+’ which takes them a form to fill out: |
*Pre condition: user(Parent) have to be in Reward tab in the bottom navigation
|
Parent is able to Click ‘edit’ to edit reward |
*Pre condition: Parent have to be in Reward tab in the bottom navigation, one or more reward is already created anddisplayed on the reward list
|
Parent is able to Click ‘delete’ to delete reward |
*Pre Requirement : There must be one or more reward created.
|
View reward Details |
*Pre Condition : There must be one or more reward that are already created
|
If there are more reward on the screen, the parent is able to scroll on the list and view more reward |
|
Claimed rewards will be moved to Claimed tab |
*Pre Condition : There must be one or more reward that are already created, and the child has enough points to redeemthe reward
|
Requirements |
Verification |
View earned points |
Case 1 - No Points
Case 2 - earned 50 points *Pre Requirement: Child must have completed a task of 50 points
|
View Reward Details |
* Pre Requirement : There must be one or more reward created.
|
If there are more tasks on the screen, the child is able to scroll on the list and view more tasks |
|
Child can Redeem a reward |
*Pre condition: There must be one or more reward created to choose from. Case 1 - has enough points
Case 2 - Not enough points
|
Once a child Redeems a task it will disappear from available reward list view |
*Pre Requirement : There must be one or more reward created with name “reward 1”. The child has enoughpoints to redeem the reward.
|
Claimed rewards will be moved to Claimed tab |
*Pre condition one or more reward has to be already created, Child1 has enough points to redeem reward. There isChild2 account.
|
Child is only able to see all the rewards claimed by him/herself |
*Pre condition a reward has to be claimed by Child1 Case 1 - There is claimed reward
Case 2 - There is no claimed reward
|
After successfully claiming the reward, the points used to claim the reward will be deducted from the earned points |
*Pre condition one or more reward has to be already created, Child1 has 100 points.
|
https://docs.google.com/document/d/1hEAYKUo_MnW0ay7YbwKW5rp-hNO4wNCyqVe-vm--oeA/edit?usp=sharing