To avoid the issues faced during the last upgrade to DHIS 2.38, We plan to run extended performance testing, simulating similar loads to the ones that PSI's production server has , will be conductedon a peak working day. This should allow us to avoid the problems that we had after the 2.38 upgrade. 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.
In this page
| Table of Contents | ||
|---|---|---|
|
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 for v40?
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 dashbaorddashboards/ visualizations visualisations containing Program Indicators can severely slow the system. Test all your dashbaord dashboards and visualizations visualisations that include Program Indicators. Inform us if you see a degradation on the time of loading when compared to the same dasbhaord in 238dashboard/ 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 report issues
please include in your ticket at PSI Helpdesk :
URL of server presenting the issue.
username usedthat experienced the issue.
Name of dashboard/ visualizationvisualisation/ 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.