Release Test Checklist Template

This checklist is to track testing tasks that need to be executed prior to a release.  These tests are manual processes (currently) that test the release candidate "package".

 

Test Package

Test result

Notes

 

Download mifos zip package from Hudson. See below for testing on Sourceforge.

 

 

 

Inspect contents of zip package.

(tick)


 

Sub directories - config and sql

(tick)

 

 

Files INSTALL, install-ubuntu.sh, LICENSE, and mifos.war

(warning)


 

View INSTALL file, use directions for installation and test each link mentioned in INSTALL file

(warning)

I

 

In config dir, applicationConfiguration.custom.properties and local.properties

(tick)


 

In config dir, view local.properties file

(tick)


 

Test deployment configurations

 

Notes

 

Deploy Mifos with FR locale and check all strings are translated.

(warning)

Missing translations on MPESA/Audi Bank 'Review & submit' page 

 

Deploy Mifos with CN locale and check all strings are translated.

(warning)


 

Deploy Mifos with ES locale and check all strings are translated.

(warning)


 

Deploy Mifos on Windows server.

(tick)

 

 

Connect to test server via IE 7.  Check layout on new pages, other primary paths (hierarchy, CSE, loans, savings)

(tick)

 

 

Copy default properties file and use as new custom properties file.  Check that any new properties are displayed on Organizational Settings page.

(tick)

 

 

On System Information, check version

(tick)

 

 

On System Information, check database schema version

(tick)

 

 

Run batch jobs, check for errors

(tick)

 

 

Upgrade backup of customer deployments

(tick)

 

 

Add Mpesa and Audi bank plugins to plugins directory and ensure that plugins are available on Import Transactions page.  Also ensure that Organizational Settings page load with plugins in place. 

(tick)

 

 

Test download of Sourceforge package

 

Notes

 

After completion of testing of release candidate on local instance, request developer to upload package and CHECKSUM file to Sourceforge.

 


 

Download package and CHECKSUM file. Confirm CHECKSUM for both MD5 and Sha1 hashes.  Additional notes for validating download package found here.

 

 

 

Check size of downloaded war file, do diff of the war vs. the war that's previously been tested.

 

 

 

When mifos.org has been updated, check the download page links on http://mifos.org/product/download-mifos and http://mifos.org/product/download-mifos/download-form

 

 

 

Download via mifos.org link. Confirm size, CHECKSUM, proper file name.

 

 

 

Expand downloaded file to ensure zip file isn't corrupted.

 

Â