BI 1.0 Report Testing Status
This page summarizes report testing for BI release 1.0. Each report shipped, testing consists of the following test processes:
Developer testing using the report acceptance criteria
Walk through of report with PM and QA before story is done
Automated tests for any ETL used by report - results
Automated acceptance test for report to validate report below UI level. - results
Manual functional test verification using Pentaho User Console, stories moved to "ready for showcase" for each report Used smaller . See test notes for reports in table below
Verification of specific bugs logged on reports. Mifosforge BI 1.0 issues.
Release Testing - See below
Report Name | Issues/comments? | Ready for Release? | Tester |
|---|---|---|---|
Due Vs Collected Branch | Due vs collected by Branch and by Loan OfficerManual test notes | Yes | Jeff/Lukasz/GM |
Due Vs Collected Loan Officer | Manual test notes | Yes | Jeff/Lukasz/GM |
Loan Officer Detailed | Manual test notes | Yes | Jeff/Lukasz/GM |
Loan Officer Summary | Manual test notes | Yes | Jeff/Lukasz/GM |
Loan Classification Report by Product | Manual test notes | Yes | Jeff/Lukasz/GM |
Outstanding Balance by Funds | Yes | Lukasz | |
Funds Movement | Yes | Lukasz | |
MFI Progress Report | Manual test notes | Yes | Jeff/Lukasz/GM |
Mifos Transactions - Detailed | Yes | Jeff | |
Mifos Transactions - Summary | Yes | Jeff | |
|
|
| |
Release Testing
Validate the 1.0 release package.
1. On Download release candidate from hudson - https://ci.mifos.org/hudson/job/bi-1.0.x-archive/lastStableBuild/ (need link for sourceforge)
2. follow steps on BI install document
3. verify that packaged ETL and reports will produce dw, reports. For 1.0, key measure is testing the initial cloud MFI instances. Run each report for current day to ensure ETL has been executed on current day. Validate that report parameters and data appear for appropriate MFI.