The primary objective of this guide is to assist you in effectively navigating Android fork or standard application, as well as provide detailed, step-by-step instructions for performing basic web-based configurations that can be tested within the application itself. By following this guide, you will gain the ability to configure and set up all the essential items required for successful testing.
It is important to note that the configurations that will be shown here are of a basic nature. To test the feedback module, a specific guide has been created for this purpose. To access the specific guide, click here.
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.
Expected result: expected behavior when executing a specific action or input in a system, application or process
What servers and users to use
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 | |
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. https://helppsi.freshdesk.com/es/support/home |
Do not use production server - you don't want to mess the data in production.
Testing data sets
Data entry in DHIS2 is effectively organized using data sets. A data set serves as a collection of data elements grouped together for streamlined data collection. In distributed installations, data sets also define portions of data for seamless export and import between different instances of DHIS2. For example, data can be transferred from a local installation at a district office to a national server. Data sets are not directly linked to the data values themselves, but rather through their associated data elements and frequencies. As a result, modifications, deletions, or additions to a data set can be made at any time without impacting the raw data already captured in the system. However, it is important to note that such changes will naturally affect the process of collecting new data.
Once you have assigned a data set to an organisation unit, that data set will be made available in Data Entry for the organisation units you have assigned it to and for the valid periods according to the data set's period type.
Verify that the data sets assigned to the user are loaded correctly
Pre-conditions:
1 | Log in to the selected server using a user account that has the necessary permissions to create a data set |
|---|---|
2 | Have organization units available for selection in the data sets. |
Create a data set, to create a date access the data set module with the following path:
Maintenance/Data Set/Data SetClick on the
plusbutton.Fill in the form with the corresponding items.
In the organization units section, select the organization units that will have access to this dataset and click on the
savebutton.
5. Log in to the Android fork using a user who has been assigned the selected organization unit in the previous step.
6. Add the user or group of users in the sharing configuration corresponding to the dataset and assign it the option Can capture and view
7. Log in to the Android Fork using the user that was added in the sharing settings.
Expected results: The datasets assigned to the user should load accurately upon logging into Android Fork.
Verify that the category and category combination are visible on the application
This test verifies the successful assignment of user permissions to view the category and category combination.
Pre-conditions:
1 | Log in to the selected server using a user account that has the necessary permissions to create a data set |
|---|---|
2 | Create a dataset successfully |
Add the user or user group to the sharing settings.
Assign permissions to the user to view the category and category combination.
3. Log in to Android Fork using the user that was added to the sharing settings
4. Open the dataset containing the configured category
Expected results: The user can view the category and the category combination, but cannot modify the text.
Verify the validation rules
1 | Log in to the selected server using a user account that has the necessary permissions to create a data set |
|---|---|
2 | Create a dataset successfully |
3 | Create validation rule successfully |
Log in to Android Fork using the user that has access to the created dataset.
Open the Data set
Verify the validation rules
Expected results: The application should display a validation message and highlight the fields that do not comply with the validation rule.
Saving data sets without internet connectivity
Testing Programs
Testing Analytics
if you use andoird analtycis, ensure that the rendering is correct, and that the representations change as you update data