• 1 Objective
• 1.1 Goals
• 1.2 Non-Goals 
• 2 Test Schedule
• 3 Test Environments
• 3.1 Mifos Test Server
• 3.2 Test Data
• 3.3 Local Test Environment
  
• 4 Test Approach and Execution
  
• 4.1 New feature testing
• 4.2 Regression testing
• 4.3 Performance and Stress testing
• 4.4 Release Candidate Preview testing
  
• 5 Known/Active bugs
• 6 Resolved bugs requiring verification
• 7. Test Status Monitoring
  
• 8. Release Criteria
  

Objective

For this release, we will perform system-level testing of the Mifos 1.1 project to ensure the new 1.1 features have been implemented as specified.  In addition, the functionality of the 1.0 release must be validated to ensure a consistent experience for existing deployments.  During this testing effort, testers will strive to identify as many issues as possible, and document these issues with clear and concise problem reports.  Testing efforts will be targeted based on project priorities and risks.

Testing Goals

For the 1.1 project, the primary testing goals are as follows:

• Functional testing of version 1.1 features, using documented test plans and test cases.
• Ensure changes to the product for this project have not introduced any serious regression in the Mifos 1.0 functionality. 
• Performance testing will be performed using a representative MFI set of data. 
• Provide a release candidate for early evaluation by MFI’s.

Testing Non-Goals

The following testing areas are considered to be beyond the scope of the 1.1 testing effort.

• Uptime or reliability testing.  Standard architecture and platform being used is considered to be a proven, stable environment.
• Unit/integration testing is not part of this system testing effort.
  
• Localization capability is being built into the product, but no localized testing of Spanish or French translations we be done by the testing team.
• Compatibility testing with other Web servers, databases, browsers will not be a focus of this release’s testing.
• Documentation will be reviewed for accuracy as a separate effort.
• No test case or automation tools will be required for testing.  Primary testing effort for 1.1 will be execution of manual test cases.
  

Test Schedule

The testing effort for v1.1 will be currently planned and executed with the following assumptions:

• Risks will be identified throughout the project which will be used as a basis for feature and test case priorities.  Test results from initial test cycles may influence the priority of test cases in later test cycles.
  
• Schedule will be time boxed so test case development and execution will be done in order or risk priority number with only highest priority areas being covered

The test schedule for v1.1 testing can be found here (in MS Excel format).  The schedule is a working document and will be modified/changed regularly as we finalize our plans.  Please check back regularly for updates.  Please direct any questions you have in this area to the Mifos Developer Mailing List. 

Test Environments

Mifos Test Server

Currently, we have one test environment available for testing the latest code of Mifos.  This server is updated in an automated fashion with the latest build available on the Mifos Build Server.  This server also contains a set of test data which you can add to and modify for testing purposes.  Please note that access to this server is only provided through the application web URL.  We do not provide direct access to the server machine itself or the DB. 

Please view the Mifos Test Server page for more details about accessing and using the test server. We will be adding additional infrastructure in the future to assist with the v1.1 testing effort. 

Please contact the Mifos Developer Mailing List if you would like additional information about our plans in this area or check back here regularly for updates.

Test Data

For basic functional testing, a standard set of test data will be used to ensure consistency and repeatability.  The details of this standard test data will be defined and described in a different document. 

Local Test Environment

Testers on the project team will test Mifos on locally available machines.  These machines will need to host the recommended Mifos environment for 1.1 as described below:

• Windows XP or Windows Server 2003
• Internet Explorer 6.0
  
• Java 2 Standard Edition SDK 5.0
  
• MySQL 5.0
• Tomcat 6
  

Mifos can be installed on a local test environment based on the build and install instructions for developers.

Test Approach and Execution

New feature testing

New feature testing will be scheduled and allocated based on execution progress and bug discovery.  The IBM Bangalore team will perform feature testing as documented in the IBM Bangalore test plan.  This test plan and test case documents for new v1.1 features can be found here in source control. 

Priority of new features, testing ownership, and status of the new feature testing is listed on the test status dashboard.  This dashboard will be updated during the duration of the project.

 

Regression testing

A set of manual test cases from the 1.0 release will be selected to produce a representative set of regression tests.  These regression tests will be prioritized and excuted as part of the overall 1.1 test schedule.  The list of 1.0 test cases will be documented in the IBM Bangalore test plan.  Please contact the Mifos Developer Mailing List if you would like additional information about our plans in this area or check back here regularly for updates.

Performance and Stress testing

Performance and stress testing for version 1.1 is being done by the IBM Dublin team.  The performance testing details will be documented in a subsequent document as these plans are still being developed.  Please contact the Mifos Developer Mailing List

if you would like additional information about our plans in this area or check back here regularly for updates.

Release Candidate Preview testing

The team will schedule a release candidate build that will be available to Mifos existing deployments for evaluation and feedback. 

Known/Active bugs

This list in our issue tracker is a list of all currently active bugs that we plan on fixing in v1.1 of Mifos.  Please note that any issues assigned to 'mifostriage' are still awaiting approval for acceptance for the v1.1 release.

Resolved bugs requiring verification

This list in our issue tracker is a list of all bugs that have been marked as 'resolved' in our issue tracker and are awaiting review and verification by a tester.  All bugs targeted for v1.1 should be verified by project completion.  Please contact the Mifos Developer Mailing List if you would like to assist with verifying these bugs.

Test Status Execution and Monitoring

Test for new features will be executed in order of business priority and availability.  Within a feature area, the following priorities will be designated for test cases:

• 1 (High) - test cases that are run with any new build prior to release, regardless whether any changes were introduced to the feature.
  
• 2 (Medium) - test cases which test major functionality of the features.  These cases are executed with each major project milestone.
  
• 3 (Low) - test cases which will test additional aspects of a feature, but can be skipped later in a project release when a feature is considered stable.
  

We will report test results by monitoring the results of test case execution and issue tracking results. 

Test case pass/fail totals will be tracked weekly, along with reference to issues reported on any test cases.  Test case results should also refer to the build used for test execution.

Issues reported during the 1.1 testing will be monitored to identify the trend of issues being detected and resolved.  On a weekly basis, we will report the number of new, total open (including new), and resolved/closed issues.

Release Criteria

The following release criteria will be met prior to completion of the project:

• All the features targeted for this release are complete and tested to the satisfaction of the entire team. 
• There are no High (P1 or P2) priority open issues targeted for the 1.1 release.  Some high priority issues may deferred based on acceptable workarounds.
• Planned tests have been executed, with all tests passing or having an acceptable workaround.
• Performance tests identify no blocking issues.
• Final release candidate build has been tested and has passed all acceptance tests.