Testing Feedback module - PSI Android Fork

This comprehensive guide is designed to assist you in efficiently and precisely conducting testing for the Feedback module on the PSI Android Fork application. It focuses specifically on critical aspects of the application. If you require guidance for conducting an overall Android test, a dedicated testing guide has been created. It covers the testing procedures for configuring data elements, programs, and the items that need to be tested. To access the testing guide, please click here.

Table of contents:

PSI Android Fork testing should be conducted on an Android v.6+ device. Do not attempt to conduct this testing via your web browser. We do not recommend testing on Android emulators as some functions may give false negatives during testing.


Testing concepts

In the testing field, some concepts and standards are necessary to conduct comprehensive testing. At a minimum, this includes:

  • Test case: a test case is a detailed set of conditions developed to verify the functionality of a specific feature.

  • Pre-conditions: specific criteria that must be met to execute the test case.

  • Test environment: The test environment contains all items to test.


What servers and users to use

Server

Description

Credentials to be used

Server

Description

Credentials to be used

The server is a copy of the production environment, which is copied nightly and overwritten every day. It is the perfect environment for testing because configuration changes will last for one day.

Use the same real-life community, workers, providers, supervisor. Just change the password.

If the account doesn’t work, request account activation via

Soporte

 

 

This server is a stable copy of the production environment, which is copied approximately every 2–3 months

The accounts on this server are different from those on the production server. If you don't have a user account, please request one by clicking on the following link. Soporte

  • Do not use production server - you don't want to mess the data in production.

Recommendation:

The android app is not optimized for accounts with extensive access to numerous programs and datasets, resulting in prolonged login times when using the DHIS2 Android application. Therefore, it is advisable to avoid assigning an excessive number of programs to a single user, as this may significantly impact performance and efficiency


General behavior

Verify that the programs are loaded correctly

Pre-conditions:

HNQIS2

RDQA

HNQIS2

RDQA

Log in using a user account that has been assigned a HNQIS2 program.

Log in using a user account that has been assigned a RDQA program.

Steps:

  1. Once you are logged into the PSI Android Fork, the data will be synchronized. Note that this process may take a few minutes.

2. Verify that all programs have been loaded correctly.

Expected result:

The application should display all programs assigned to the user for both HNQIS2 and RDQA.

 


HNQIS2

Start an assessment

The initial test in HNQIS2 is to verify whether the application allows the creation of a new assessment.

Pre-conditions:

1

Successful login

Log in using a user account that has been assigned a HNQIS2 program.

Steps:

  1. Select a program from the list.

  2. Tap on the Search button

3. Select an assessment date

4. Tap on the “magnifying glass” icon.

5. Tap on the Create new button

6. Select an organization unit

7. Tap on the Accept button

8. Select an enrollment date

9. Tap on the Accept button

10. Check the values displayed are the same as those entered the previous step

In the attributes section sometimes the organization unit is not shown, this is not an issue of the PSI Android Fork application because the same issue happens in the data capture application. Remember that the PSI Android Fork have the same feature that Data capture app.

10. Select an assessment date

11. Tap on the Accept button

 

Expected result:

The application should allow you to start an assessment, and all items should load correctly; in the enrollment data section, the fields should autofill with the information entered.


Verify the child sections in the assessment

Sections can be configured to have child sections based on answers.

Pre-conditions:

1

Successful login

Log in using a user account that has been assigned a HNQIS2 program.

2

Identify Assessment

Select an assessment that have child sections.

3

Access assessment

Begin completing the assessment.

Steps:

  1. Select the option that has been configured to show the new sections in the assessment.

3. Check that the child sections are displayed.

Expected results:

The child sections should be shown when the configured option is selected; otherwise, the section should be hidden.


Verify the conditional logic questions.

Some sections of the assessment contain questions with conditional logic. Conditional logic means that based on the response to specific questions, additional questions may be added.

Pre-conditions:

1

Successful login

Log in using a user account that has been assigned a HNQIS2 program.

2

Identify Assessment

Select an assessment that have child sections.

3

Access assessment

Begin completing the assessment

Steps:

  1. Enrollment in the assessment that contains the program rule.

  2. Check that the conditional logic questions are displayed.

Expected results:

The conditional logic questions should be shown when the configured option is selected; otherwise, the questions should be hidden.


Feedback module

This is one of the most important features of the PSI Android Fork. The feedback module allows you to review the answers to the questions performed in the assessment.

Pre-conditions:

1

Log in using a user account that has been assigned a HNQIS2 program.

Steps:

  1. Select or create an assessment.

  2. In the dashboard, tap on the three dots menu in the top right corner.

3. Check that the questions are filtered correctly by the following tabs: All, Critical and Non-critical.

All

Critical

Non-critical

All

Critical

Non-critical

 

 

 

4. Check the sections, all the sections should have their score.

All

Critical

Non-critical

All

Critical

Non-critical

 

 

 

5. Check show only failed; each section should only show the failed questions.

All

Critical

Non-critical

All

Critical

Non-critical

 

 

 

6. Tap on the share button, the application should allow sharing the feedback through different social media.

 

Expected results:

The questions should be filtered by the tabs mentioned above correctly, in addition the application should allow sharing the information, and also the application should show only failed questions when you check this function.


RDQA

Enrollment in the RDQA program

Pre-conditions:

1

Log in using a user account that has been assigned a RDQA program.

Steps:

  1. Open RDQA program

  2. Click on the search button and select a health area, all available sanitary areas must be shown.

  3. Tap on the “magnifying glass” icon

  4. Click on the Create new button

  5. Select an organization unit and click on the Accept button

6. Select a date

7. Click on the Accept button

8. Check the enrollment data fields are autofilled.

9. Check the following fields are mandatory:

  • RDQA - Health Area

  • RDQA - Reporting Period Start

  • RDQA - Reporting Period End

  • Do you want to do an M&E assessment?

Expected results:

The application must allow enrollment in the RDQA program correctly, and the fields in the enrollment data section are autofilled correctly.


Action plan-Header title

Pre-conditions:

1

Log in using a user account that has been assigned a RDQA program.

2

Enroll in the RDQA program

Steps:

  1. Add a new action plan

  2. Select an event date and an organization unit

  3. Tap on the next button

4. Type an action item

5. Verify the header title

Expected results:

The action item entered should appear in the header title of the action plan.


Data verification-Header title

Pre-conditions:

1

Log in using a user account that has been assigned a RDQA program.

2

Enroll in the RDQA program

Steps:

  1. Add a new Data verification

  2. Select an event date and an organization unit

  3. Tap on the next button

4. Select an indicator

5. Verify the header title

Expected results:

The indicator selected should appear in the header title of the Data verification.


Feedback module

This is one of the most important features of the Android Fork, this module allows you to review the answers to the questions performed in the assessment.

Pre-conditions:

1

Log in using a user account that has been assigned a RDQA program.

2

Enroll in the RDQA program

Steps:

  1. Tap on the settings menu (three dots) in the top right corner.

  2. Select Feedback

  3. Verify the feedback module displays two sections: By indicator and By technical area

4. Select By indicator tab.

5. Check that the added indicators are displayed and that each indicator has seven dimensions.

6. Verify that each dimension displays a text when the arrow is clicked.

7. Select By technical area tab.

8. Check that within each dimension the aggregated indicators are shown.

9. Verify that each dimension displays a text when the arrow is clicked.

10. Check show only failed, each section should only show the questions that were failed.

By indicator

By technical area

By indicator

By technical area

 

 

11. Tap on the share button, the application should allow sharing the feedback through different social media.

 

Expected results:

The questions should be filtered by the tabs mentioned above correctly, in addition the application should allow sharing the information and also the application should show only failed questions when you check this function.


Charts and indicators

The application has a section dedicated to charts and indicators corresponding to the RDQA program.

1

Log in using a user account that has been assigned a RDQA program.

2

Enroll in the RDQA program.

3

Open the charts and indicators section.

Steps:

  1. Check that the indicators are correctly displayed.

  2. Check that the charts are displayed correctly.

3. Tap on the three dots in the upper right corner of the chart.

4. Change the view of the chart.

View as bar

View as table

View as value

View as line

View as bar

View as table

View as value

View as line

 

 

 

 

Expected results:

The indicators are displayed correctly, and the charts allow changing the type of display.