Upgrade Testing

Owned by Jeff Brewster (Unlicensed)
Last updated: Mar 28, 2011 by KojoGVersion comment
1 min read

When testing a Mifos release, we need to test the upgrade process from prior versions.

General considerations

  1. Typically an upgrade from one release to another has one or more database upgrades.  Database upgrade testing have changed with the new database upgrade process introduced in the G release.  
  2. Upgrades from1.x require an upgrade to 2.0 before proceeding to upgrade to newer versions. 2.0 upgrade will handle migration from older survey and custom fields to Question Groups.
  3. New or removed custom properties
  4. Custom chart of accounts
  5. Custom BIRT reports and admin documents
  6. Batch jobs. Have jobs been removed or added with upgrade? Does old task.xml file still work with batch jobs?

Release G Database upgrade testing notes

Notes from testing mifos production DB upgrade/rollback process

Upgrade testing was performed with the 2.1 database. I then manually expanded the database using changeSet id="MIFOS-4633_1" from head master build 146.

Scenarios:

  1. G war and F database that's upgraded on startup. Ran G war. Confirmed DATABASECHANGELOG has update to database and that Mifos is up and running with no problems.
  2. G war and F database that's upgraded manually.
  3. expanded db manually, ran with G war. no problems.
  4. Contraction was verified regarding removing tables and columns.