This is a test script for the release of Reveal 3.2.0. <If there are steps missing from this script, please update the master template. Please copy this for each round of testing you do.>
...
Step | Detail | Expected Result / Pass Criteria Update for each workflow/feature.
(List criteria and primary verification method: “Manual”, will need notes and observations taken against criteria. “Auto” should be tested n automated testing but notes should be taken if fail in manual testing) | Pass? Complete for each iteration/run of workflow.
(Y/N)
| Notes. Complete for each iteration/run of workflow. Include details on which user used, which family registered, and capture initial bug notes. |
---|---|---|---|---|
User | Login | Manual - existing username and password should login successfull | Y | username use: bvbd_mhealth |
Location | Select in hamburger menu | Manual - After login locations should load. Select one. OAs loads immediately the app is loaded. | Y | Thailand test site BVBD 1 |
Plan | Select in hamburger menu | Manual - Plans available for the area should load ( observed fastest load takes about 30 seconds, highly network dependent) | Y | A1 Thailand test site BVBD 1 2020-02-06 RMK release 3.2.0 testing plan. |
Add location 1 | Add a new residential structure | Added structure should appear on the map in yellow | Y | |
Mark location as inactive 1 | Long press and mark as inactive. | Mark location inactive confirmation pop up should show. | Y | |
Confirm location is inactive | Check map view - structure should be grey and cannot tap on it. Should not appear on list view. Check the web dashboards and confirm the location is no longer counted. | Structure turned grey. When tapped a pop up shows notifying the user the structure has no tasks for the plan. XXXXXX | Y N | Repeated on 5 structures.. The dashborad showed 2 of 22 structures progress for family registration. Even after marking some structures as inactive, the denominator did not change despite synic multiple times and the mobile client indicated syncing was complete. ( This observation was withing a period of 5 minutes.) |
Add location 2 | Add a new mosquito collection point | Added point appearing on map with correct icon | Y | structure name: Sangenjo |
Mark location as inactive 2 | Long press and mark as inactive | Mark location inactive confirmation pop up should show. | Y | |
Confirm location is inactive | Check map view - structure should be grey and cannot tap on it. Should not appear on list view. Check the web dashboards and confirm the location is no longer counted. | Structure turns grey XXXX | Y N | newly added not reflecting on dashboard after syncing and observing for 5 minutes. To be updates after its verified. |
Add location 3 | Add a new breeding site | Added structure showing on map with correct icon. | Y | |
Mark location as inactive 3 | Long press and mark as inactive | Mark location inactive confirmation pops up. | Y | |
Confirm location is inactive | Check map view - structure should be grey and cannot tap on it. Should not appear on list view. Check the web dashboards and confirm the location is no longer counted. | Point turns grey XXXXX | Y N | 3 larva sites before adding 2 new ones and syncing, observed for 5 minutes. data not reflecting on dashboard. To be revisited and updated later after data sycs. |
Add location 4 | Add a new PAOT | added point show on map | Y | |
Mark location as inactive 4 | Long press and mark as inactive | Mark location inactive confirmation pops up. | Y | |
Confirm location is inactive | Check map view - structure should be grey and cannot tap on it. Should not appear on list view. Check the web dashboards and confirm the location is no longer counted. | Point turn grey Indicator not on the web UI yet. To be revisited. | Y | |
Mark already-there location but with no data entered as inactive. | Long press one of each location type that is already enumerated and mark as inactive | Residential structure turns grey. Mosquito collection point turns grey Larval breeding site point turns grey PAOT point turns grey | Y Y Y Y | |
Verify location with data cannot be marked inactive | Long press one of each location type with task info already collected confirm you are unable to mark as inactive. | Residential structures does not allow marking as inactive. Mosquito collection point does not allow marking as inactive. Larval breeding site point does not allow marking as inactive. PAOT point does not allow marking as inactive. | Y Y Y Y | |
...
Step | Detail | Expected Result / Pass Criteria Update for each workflow/feature.
(List criteria and primary verification method: “Manual”, will need notes and observations taken against criteria. “Auto” should be tested n automated testing but notes should be taken if fail in manual testing) | Pass? Complete for each iteration/run of workflow.
(Y/N) | Notes. Complete for each iteration/run of workflow. Include details on which user used, which family registered, and capture initial bug notes. |
---|---|---|---|---|
User | Login | Manual - existing username and password should login successfull | Y | username use: bvbd_mhealth |
Plan | Select in hamburger menu | Manual - After login locations should load. Select one. OAs loads immediately the app is loaded. | Y | Thailand test site BVBD 1 |
Location | Select in hamburger menu | Manual - Plans available for the area should load | Y | A1 Thailand test site BVBD 1 2020-02-06 RMK release 3.2.0 testing plan. |
Select household | Tap a yellow household structure. Verify that first question to display asks about if the structures is eligible (mark as not eligible) and why not if not. | Mark location Ineligible pop up appears | Y | out of the available options, selected Not Eligible: Currently Unoccupied, that saved and the structure on the map turned grey. |
Confirm skip logic | Review the data dictionary and check that all downstream skip logic is appropriate (if not eligible, all other fields should hide)Check data dictionary | Y | ||
Submit form/Confirm | Tap submit, save form (when an eligible house). | |||
Check card | Select the structure on the map. Confirm card view. | Card should display not eligible | Y | The card displays not eligible on the card. |
...
Step | Detail | Expected Result / Pass Criteria Update for each workflow/feature.
(List criteria and primary verification method: “Manual”, will need notes and observations taken against criteria. “Auto” should be tested n automated testing but notes should be taken if fail in manual testing) | Pass? Complete for each iteration/run of workflow.
(Y/N) | Notes. Complete for each iteration/run of workflow. Include details on which user used, which family registered, and capture initial bug notes. |
---|---|---|---|---|
User | Login | Manual - existing username and password should login successfull | Y | username use: bvbd_mhealth |
Location | Select in hamburger menu | Manual - After login locations should load. Select one. OAs loads immediately the app is loaded. | Y | Thailand test site BVBD 1 |
Plan | Select in hamburger menu | Manual - Plans available for the area should load. | Y | A1 Thailand test site BVBD 1 2020-02-06 RMK release 3.2.0 testing plan. |
(pre-registered) Select household | Select a household that is already registered with tasks incomplete. | Able to select household | Y | Reci family |
Mark ineligible for betnet | Navigate to task tab and select bednet task. Verify that first question asks about eligibility, and the default value is ‘yes’. Mark as ineligible. | First question asks about eligibility Eligible set as default | Y Y | |
Confirm skip logic | Review the data dictionary and check that all downstream skip logic is appropriate (if not eligible, all other fields should hide) | Check dictionaryY | If set to not ineligible all the other question fields do not show. Only question that shows is why the structure is not eligible. | |
Submit form | Tab submit, save form | Able to save | Y | |
Check task view | Confirm that task button is black and reads ‘ineligible’ Note, though scoped to read ‘ineligible’ this reads ‘not eligible’ which should also be acceptable. | Distribute bednet task shows not eligible | Y | |
Repeat for new household. | Repeat steps above but register a household and members from scratch | Distribute bednet task button turns to black text “NOT ELIGIBLE” for newly registered family. | Y | |
...
Step | Detail | Expected Result / Pass Criteria Update for each workflow/feature.
(List criteria and primary verification method: “Manual”, will need notes and observations taken against criteria. “Auto” should be tested n automated testing but notes should be taken if fail in manual testing) | Pass? Complete for each iteration/run of workflow.
(Y/N) | Notes. Complete for each iteration/run of workflow. Include details on which user used, which family registered, and capture initial bug notes. |
---|---|---|---|---|
User | Login | Manual - existing username and password should login successfull | Y | username use: bvbd_mhealth |
Location | Select in hamburger menu | Manual - After login locations should load. Select one. OAs loads immediately the app is loaded. | Y | Thailand test site BVBD 1 |
Plan | Select in hamburger menu | Manual - Plans available for the area should load. | Y | A1 Thailand test site BVBD 1 2020-02-06 RMK release 3.2.0 testing plan. |
(pre-registered) Select household | Select a household that is already registered with tasks incomplete. | Able to select household | Y | Reci family |
Complete bednet for distribution | Navigate to task tab and select bednet task. Verify that first question asks about eligibility, and the default value is ‘yes’. Mark as eligible. | First question asks about eligibility Eligible set as default | Y Y | |
Confirm skip logic | Review the data dictionary and check that all downstream skip logic is appropriate | Check dictionaryY | When set eligible all the other question fields remain open for data entry | |
Submit form | Enter data,tap submit, save form | Able to save | Y | |
Check task view | Confirm that task button is green and reads ‘Complete’ | Distribute bednet task shows complete | Y | |
Repeat for new household. | Repeat steps above but register a household and members from scratch | Distribute bednet task button turns to green text “COMPLETE” . | Y | Distribute bednet tast turns to green and reads COMPLETE when data is entered and saved. |
...
Step | Detail | Expected Result / Pass Criteria Update for each workflow/feature.
(List criteria and primary verification method: “Manual”, will need notes and observations taken against criteria. “Auto” should be tested n automated testing but notes should be taken if fail in manual testing) | Pass? Complete for each iteration/run of workflow.
(Y/N) | Notes. Complete for each iteration/run of workflow. Include details on which user used, which family registered, and capture initial bug notes. |
---|---|---|---|---|
User | Login | Manual - existing username and password should login successfull | Y | username use: bvbd_mhealth |
Location | Select in hamburger menu | Manual - After login locations should load. Select one. OAs loads immediately the app is loaded. | Y | Thailand test site BVBD 1 |
Plan | Select in hamburger menu | Manual - Plans available for the area should load. | Y | A1 Thailand test site BVBD 1 2020-02-06 RMK release 3.2.0 testing plan. |
Select household with multiple members | Select a household with multiple members | select a structure with multiple members | Y | Ten family |
Select household member (no tasks) | Select a non family head household member that has no tasks complete, so you navigate to the screen for that member | Tab on family member to go to member screen | Y | selected member You Ben |
Archive | Tab the three dot menu in the upper right, select ‘archive member’ and ‘confirm’. | Confirm archive family member | Y | |
Confirm member gone | Go to family member view and confirm that member no longer appears Confirm web UI and holding tables update. | Member not listed on residents and tasks. Confirm when data syncs | Y | |
Repeat for member with completed tasks | Repeat above steps. Confirm business logic changes as necessary. | Member not listed on residents and tasks. | Y | Test CR Family, Archived member INDEX ICC 303 |
Confirm you cannot archive household head | Navigate to the member page for the household held and confirm that the option to Archive is not available. | Archive Member does not show for household head. | Y | Test CR family, HH Head: Test CR ICC 303 |
...
Step | Detail | Expected Result / Pass Criteria Update for each workflow/feature.
(List criteria and primary verification method: “Manual”, will need notes and observations taken against criteria. “Auto” should be tested n automated testing but notes should be taken if fail in manual testing) | Pass? Complete for each iteration/run of workflow.
(Y/N) | Notes. Complete for each iteration/run of workflow. Include details on which user used, which family registered, and capture initial bug notes. |
---|---|---|---|---|
User | Login | Manual - existing username and password should login successfull | Y | username use: bvbd_mhealth |
Location | Select in hamburger menu | Manual - After login locations should load. Select one. OAs loads immediately the app is loaded. | Y | Thailand test site BVBD 1 |
Plan | Select in hamburger menu | Manual - Plans available for the area should load. | Y | A1 Thailand test site BVBD 1 2020-02-06 RMK release 3.2.0 testing plan. |
Select household | Select a household | Tap on a structure with family registration data | Y | |
Archive | From the family list view, tap the three dot menu in the upper right, select ‘archive household’ and ‘confirm’. | Confirm household archival pop up. Confirm to Archive. | Y | |
Check map view and list view | Confirm that the structure appears as yellow in both views Confirm web UI and holding tables update. | Structiure on the map shows yellow. When taped a pop up for structure eligibility shows up.XXXX Revisit after dat syncs. | Y | Boxa family, Cr TEST 2 family, Guy family |
Reregister against that structure, complete tasks. | Tap the structure and complete a new family registration. Complete all tasks against that structure and confirm it behaves as expected. | Registration of new family works. | Y | Kaponde family, Mwape family, kawanda family. Issues observed: https://smartregister.atlassian.net/projects/RVL/issues/RVL-867 https://smartregister.atlassian.net/projects/RVL/issues/RVL-866 |
...