Release test checklist 2.3.1

Test Package	Test Result	Notes
Download mifos zip package from Hudson. See below for testing on Sourceforge.
Inspect contents of zip package.
Sub directories - config and db
Files INSTALL, install-ubuntu.sh, LICENSE, and mifos.war
View INSTALL file, use directions for installation and test each link mentioned in INSTALL file
In config dir, applicationConfiguration.custom.properties and local.properties
In config dir, view local.properties file
Test deployment configurations	Manual Test	Result
Deploy Mifos with FR locale and check all strings are translated.		http://mifosforge.jira.com/browse/MIFOS-5490 Heading text in the left navigation bar have missing translations and REST Api Approval, Import Client data link and page are not translated.
Deploy Mifos with CN locale and check all strings are translated.		http://mifosforge.jira.com/browse/MIFOS-5490 Heading text in the left navigation bar have missing translations and REST Api Approval, Import Client data link and page are not translated.
Deploy Mifos with ES locale and check all strings are translated.		http://mifosforge.jira.com/browse/MIFOS-5490 Heading text in the left navigation bar have missing translations and REST Api Approval, Import Client data link and page are not translated.
Deploy Mifos on Windows server.
Connect to test server via IE 8. Check layout on new pages, other primary paths (hierarchy, CSE, loans, savings)
Copy default properties file and use as new custom properties file. Check that any new properties are displayed on Organizational Settings page.		No information about the loaded plugins.
On System Information, check version
On System Information, check database schema version
Run batch jobs, check for errors
Upgrade backup of customer deployments
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.