Name: Annie Martin
Date: Dec 16
Version: 3.0.0
Server: Thai (using test areas)
RVL-108: Mark structure as inactive IN PROGRESS
Step | Detail | Result |
---|---|---|
User | Login | bvbd_mhealth |
Plan | Select in hamburger menu |
|
Location | Select in hamburger menu |
|
Add location 1 | Add a new residential structure | Done |
Mark location as inactive 1 | Long press and mark as inactive. | Long press pop-up generates confirmation text. Note - I think the long press is too sensitive and should be extended to twice the length - thoughts? |
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. | Confirmed. However, I think we may want to differentiate the error message. Right now the error message is ‘Loading failed, this structure does not have a task assigned to it for the Plan Thailand test site BVBD’. Since this structure will never have a task assigned, I think a more appropriate message is ‘This location is not active and will not have tasks assigned to it in this plan or future plans.’ https://smartregister.atlassian.net/browse/RVL-754 NEED TO CHECK WEB |
Add location 2 | Add a new mosquito collection point | Done. |
Mark location as inactive 2 | Long press and mark as inactive | Done. |
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. | Confirmed NEED TO CHECK WEB |
Add location 3 | Add a new breeding site |
|
Mark location as inactive 3 | Long press and mark as inactive |
|
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. | Confirmed NEED TO CHECK WEB |
Add location 4 | Add a new PAOT |
|
Mark location as inactive 4 | Long press and mark as inactive |
|
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. | Confirmed - we may want to change this to black instead of grey. https://smartregister.atlassian.net/browse/RVL-755 NEED TO CHECK WEB |
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 |
|
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. | Confirmed NEED TO CHECK WEB |
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. |
|
RVL-11: Marking task ineligible IN PROGRESS
Step | Detail | Result |
---|---|---|
User | Login | bvbd_mhealth |
Plan | Select in hamburger menu |
|
Location | Select in hamburger menu |
|
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. | The first question does appear. However, it appears as a popup and without the second question asking about why the structure ineligible. Tracked in https://smartregister.atlassian.net/browse/RVL-731 Structue does turn black when inelgible. We may want this to be gray instead. https://smartregister.atlassian.net/browse/RVL-755 NEED TO CHECK WEB |
Confirm skip logic | Review the data dictionary and check that all downstream skip logic is appropriate (if not eligible, all other fields should hide) | Issue with downstream skip logic if answer is ‘not eligible’ |
Submit form/Confirm | Tap submit, save form (when an eligible house). | When eligible, submission of family and head registration works fine. |
Check card | Select the structure on the map. Confirm card view. | Card view shows as expected. |
Step | Detail | Result |
---|---|---|
User | Login | bvbd_mhealth |
Plan | Select in hamburger menu |
|
Location | Select in hamburger menu |
|
(pre-registered) Select household | Select a household that is already registered with tasks incomplete |
|
Mark one member ineligible | Navigate to task tab and select blood screening task. Verify that first question asks about eligibility, and the default value is ‘yes’. Mark as ineligible. |
Confirmed. |
Confirm skip logic | Review the data dictionary and check that all downstream skip logic is appropriate (if not eligible, all other fields should hide) | Does not incorporate follow up question on reason why ineligible. |
Submit form | Tap save form | Done. Note that once marked as not eligible, the form cannot be edited. NEED TO CHECK WEB |
Check family task view | Confirm that task button is black and reads ‘ineligible’ | Reads ‘Not eligible’. I think this is fine. |
Repeat for new household. | Repeat steps above but register a household and members from scratch | Job family.
|
Step | Detail | Result |
---|---|---|
User | Login | bvbd_mhealth |
Plan | Select in hamburger menu |
|
Location | Select in hamburger menu |
|
(pre-registered) Select household | Select a household that is already registered with tasks incomplete. | Frifa 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. |
|
Confirm skip logic | Review the data dictionary and check that all downstream skip logic is appropriate (if not eligible, all other fields should hide) |
|
Submit form | Tab submit, save form |
|
Check task view | Confirm that task button is black and reads ‘ineligible’ |
|
Repeat for new household. | Repeat steps above but register a household and members from scratch | Job family.
|
RVL-143: Ability to delete family membersIN PROGRESS
Step | Detail | Result |
---|---|---|
User | Login | bvbd_mhealth |
Plan | Select in hamburger menu |
|
Location | Select in hamburger menu | Thailand test site BVBD 2 |
Select household with multiple members | Select a household with multiple members | Test 2 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 | Mem 2 Mem 1, Male |
Archive | Tab the three dot menu in the upper right, select ‘archive’ and ‘confirm’. |
NEED TO CHECK HOLDING TABLES. |
Confirm member gone | Go to family member view and confirm that member no longer appears |
|
Repeat for member with completed tasks | Repeat above steps. Confirm business logic changes as necessary. | Confirmed. P family Joyce Test2 - had RACD task done (no other members had this), so house was purple. I archived Joyce so there were no RACD tasks done. I had to wait for the app to sync (I pressed sync and waiting <1 min) and the colour reverted to pink. |
Confirm you cannot archive household head | Navigate toe the member page for the household held and confirm that the option to Archive is not available. | Test 2 Mem 1 Confirmed cannot archive. |
Step | Detail | Result |
---|---|---|
User | Login | bvbd_mhealth |
Plan | Select in hamburger menu |
|
Location | Select in hamburger menu | Thailand test site BVBD 2 |
Select household | Select a household | Jack Family |
Archive | From the family list view, tap the three dot menu in the upper right, select ‘archive’ and ‘confirm’. |
|
Check map view and list view | Confirm that the structure appears as yellow in both views | House immediately becomes yellow on map. On list view the house is still pink, has the label ‘Jack House’ and reads ‘not visited'. When I select the button, it takes me to a register family screen. If I press sync the list view button it turns yellow, but still has the label ‘Jack House’. Then two minutes later, it is pink again , but says 'not visited’. |
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. | I am able to register, but the family name remains the same as the orignial family, although the the task and member information |