Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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.

v40 Testing Bed: 240.psi-mis.org

The main testing environment is already running at 240.psi-mis.org. The database on this environment is a copy of production, which we refresh based on the schedule below.

Refresh

Planned/ executed date

status

Late March

2.40.3

 March 22nd

DONE

Refresh late April

2.40.?

 April 29th

PLANNED

Refresh late May

2.40.4 (expected)

 May 30th

PLANNED

Refresh mid June

2.40.?

 June 15th

PLANNED

DECOMISSIONING

July 5th

PLANNED

What to test?

Below the list of things that you need to focus your testing:

  1. 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.

  2. 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 PSI Helpdesk :

  • URL server

  • username used

  • Name of dashboard/ visualization/ dataset/ tracked entity. If possible, UID

  • Screenshot INCLUDING full URL

  • if a multisteps process, video

v40 Development Server Upgrade (dev.psi-mis.org)

dev.psi-mis.org will be upgraded to 2.40 on mid June 2024, in preparation to the go live. If you have any configuration in 2.38 that you want to move to production, please do before mid June, otherwise you will have to wait until early July so you avoid version incompatibilities.

  • No labels