Versions Compared

Old Version 4

changes.mady.by.user Reuben Kaponde

Saved on

compared with

New Version 5

changes.mady.by.user Reuben Kaponde

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

Navigate to task tab and

Step

Detail

Expected Result

User

Login

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

/ 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

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.

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

Tap save form

Check family 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.

Repeat for new household.

Repeat steps above but register a household and members from scratch

...

Review the data dictionary and check that all downstream skip logic is appropriate. Select the appropriate answer to the question on testing.

  • if NO, the only question should be asking why the person was not tested. Select the reason why the person was not texted.

  • If YES, the next question about the type on test will show. Select the type of test used.

  • If MICROSCOPY, a question requiring the slide number and results follows. Pick the the applicable results.

    • If RDT, the RDT result question will follow. Pick the appropriate answer.

    Step

    Detail

    Expected Result

    User

    Login

    Plan

    Select in hamburger menu

    Location

    Select in hamburger menu

    (pre-registered) Select household

    Select a household that is already registered with tasks incomplete

    Conduct blood screening

    Navigate to task tab and select blood screening task. Verify that first question asks about eligibility, and the default value is ‘yes’. Proceed to answer the other questions.

    • Select the type of blood screening.

    • Select if person has slept outside within the past two weeks.

    • Select if the person was testing or not.

    • Select if the person was tested or not.

    Confirm skip logic

    Submit form

    Tap save form

    Check family task view

    Confirm that task button has green text which reads ‘COMPLETE’

    Repeat for new household.

    Repeat steps above but register a household and members from scratch

    ...

    Step

    ...

    Detail

    ...

    Result

    ...

    User

    ...

    Login

    ...

    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 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’

    Note, though scoped to read ‘ineligible’ this reads ‘not eligible’ which should also be acceptable.

    ...

    Repeat for new household.

    ...

    Repeat steps above but register a household and members from scratch

    Step

    Detail

    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

    Plan

    Select in hamburger menu

    Location

    Select in hamburger menu

    (pre-registered) Select household

    Select a household that is already registered with tasks incomplete

    Conduct blood screening

    Navigate to task tab and select blood screening task. Verify that first question asks about eligibility, and the default value is ‘yes’. Proceed to answer the other questions.

    • Select the type of blood screening.

    • Select if person has slept outside within the past two weeks.

    • Select if the person was testing or not.

    • Select if the person was tested or not.

    Confirm skip logic

    Review the data dictionary and check that all downstream skip logic is appropriate. Select the appropriate answer to the question on testing.

    1. if NO, the only question should be asking why the person was not tested. Select the reason why the person was not texted.

    2. If YES, the next question about the type on test will show. Select the type of test used.

    3. If MICROSCOPY, a question requiring the slide number and results follows. Pick the the applicable results.

    4. If RDT, the RDT result question will follow. Pick the appropriate answer.

    Submit form

    Tap save form

    Check family task view

    Confirm that task button has green text which reads ‘COMPLETE’

    Repeat for new household.

    Repeat steps above but register a household and members from scratch

    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

    Plan

    Select in hamburger menu

    Location

    Select in hamburger menu

    (pre-registered) Select household

    Select a household that is already registered with tasks incomplete.

    Complete bednet Mark ineligible for distributionbetnet

    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’

    Note, though scoped to read ‘ineligible’ this reads ‘not eligible’ which should also be acceptable.

    Repeat for new household.

    Repeat steps above but register a household and members from scratch

    ...

    Go to family member view and confirm that member no longer appears

    Confirm web UI and holding tables update.

    Step

    Detail

    Expected Result

    User

    Login

    Plan

    Select in hamburger menu

    Location

    Select in hamburger menu

    Select household with multiple members

    Select a household with multiple members

    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

    Archive

    Tab the three dot menu in the upper right, select ‘archive member’ and ‘confirm’.

    Confirm member gone

    Repeat for member with completed tasks

    Repeat above steps. Confirm business logic changes as necessary.

    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.

    Step

    Detail

    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

    Plan

    Select in hamburger menu

    Location

    Select in hamburger menu

    (pre-registered) Select household

    Select a household that is already registered with tasks incomplete.

    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 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’

    Note, though scoped to read ‘ineligible’ this reads ‘not eligible’ which should also be acceptable.

    Repeat for new household.

    Repeat steps above but register a household and members from scratch

    RVL-143: Ability to delete family members IN PROGRESS

    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

    Plan

    Select in hamburger menu

    Location

    Select in hamburger menu

    Select household with multiple members

    Select a household with multiple members

    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

    Archive

    Tab the three dot menu in the upper right, select ‘archive member’ and ‘confirm’.

    Confirm member gone

    Go to family member view and confirm that member no longer appears

    Confirm web UI and holding tables update.

    Repeat for member with completed tasks

    Repeat above steps. Confirm business logic changes as necessary.

    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.

    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

    Plan

    Select in hamburger menu

    Location

    Select in hamburger menu

    Select household

    Select a household

    Archive

    From the family list view, tap the three dot menu in the upper right, select ‘archive household’ and ‘confirm’.

    Check map view and list view

    Confirm that the structure appears as yellow in both views

    Confirm web UI and holding tables update.

    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.

    ...