To avoid the issues faced during the last upgrade to DHIS 2.38, extended performance testing, simulating similar loads to the ones that PSI's production server has, will be conducted. Still, it is important for country administrators and super users to test the new version thoroughly, so we can address any potential issues before the planned upgrade.
Testing PSI’s DHIS2 v40 upgrade is a collaborative effort between the DHIS2 global team and the DHIS2 country administrators. At the central level, the DHIS2 global team will conduct comprehensive performance tests to simulate user loads during common operations such as analytics generation, dashboard loading, web data capture and android synchronisation. This proactive approach aims to prevent issues similar to those encountered after the 2.38 upgrade. On this page, you will find details about what and how country administrators should test DHIS2 v40, along with guidelines for reporting any identified errors.
| Table of Contents | ||
|---|---|---|
|
What to Test in DHIS v40?
Below the list of items that you need to focus your testing:
Capture App for tracker: the tracker capture app can be still be used, but it is now considered legacy. You should be using the new Capture App, and you should ensure that all your program rules fired as expected.
Dashboard loading time when they use Program Indicators: we are aware that some dashboards/ visualisations containing Program Indicators can severely slow the system. Test all your dashboards and visualisations that include Program Indicators. Inform us if you see a degradation on the time of loading when compared to the same dashboard/ visualisation in v2.38.
New user roles: we have implemented streamlined user roles for DHIS2 v40, in line to the revised authorities on that release. Please make sure that your users have the expected access to DHIS2 functionality.
How to test - v40 Testing Bed: 240.psi-mis.org
The main testing environment is already running runs at 240.psi-mis.org. The database on this environment is a copy of production, which we refresh based on the schedule below.
Refresh | DHIS2 version | Planned/ executed date | statusStatus | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Late March | 2.40.3 | March 22nd |
| ||||||||||||
Refresh late April | 2.40.? | April 29th |
| Refresh late May | 2.40.4 (expected) | May 30th |
| ||||||||
Refresh mid June | 2.40.? | June 15th |
| ||||||||||||
DECOMISSIONING | July 5th |
|
What to test?
Below the list of things that you need to focus your testing:
Capture App for tracker: the tracker capture app can be still be used, but it is now considered legacy. You should be using the new Capture App, and you should ensure that all your program rules fired as expected.
Dashboard loading time when they use Program Indicators: we are aware that some dashbaord/ visualizations containing Program Indicators can severely slow the system. Test all your dashbaord and visualizations that include Program Indicators. Inform us if you see a degradation on the time of loading when compared to the same dasbhaord in 238
How to report issues
please include in your ticket at psihelpdesk:
...
URL server
...
username used
...
Reporting Issues with DHIS2 v40
please submit a ticket at PSI Helpdesk with the following information:
URL of server presenting the issue.
username that experienced the issue.
Name of dashboard/ visualisation/ dataset/ tracked entity. If possible, UID of affected DHIS2 object.
Screenshot INCLUDING full URL.
if a multisteps the issue involves a multi-step process, video
v40 Development Server Upgrade (dev.psi-mis.org)
...
please include a short video.