BI 1.1 Test Status

Owned by Jeff Brewster (Unlicensed)
Last updated: Feb 16, 2011Version comment
2 min read

This page summarizes report testing for BI release 1.1.  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.1 issues.
  • Release Testing - See below

Report Name

Issues/comments?

Ready for Release?

Tester

Group Collection Sheet (MPESA)

1. No acceptance test.(added by Jakub)

(tick)

Lukasz

Branch Expected Cash Flow

1. MIFOSBI-242        (scheduled for 1.2)       
2. MIFOSBI-256        (scheduled for 1.2)  

(tick)

Lukasz

Due vs Collected by Center

1. MIFOSBI-255        (scheduled for 1.2)   
2. MIFOSBI-258        (scheduled for 1.2)  

(tick)

Lukasz

PPI Data Export in Excel and Enhancements

 

(tick)

Jeff

Client Exit

1. MIFOSBI-254       (scheduled for 1.2)       
2. MIFOSBI-255       (scheduled for 1.2)       

(tick)

Lukasz

Loans To Be Disbursed

1. MIFOSBI-256       (scheduled for 1.2)    

(tick)

Lukasz

Loans Pending Approval

1. MIFOSBI-256       (scheduled for 1.2)    

(tick)

Lukasz

Outstanding Balances

1. Slow performance on large pdf - MIFOSBI-231              (scheduled for 1.2)

(tick)

Jeff

MPESA reports

 

(tick)

Lukasz

Loan Officer Performance Summary (Cumulative)

 

(tick)

 

Loan Officer Performance Summary (During Period)

 

(tick)

 

Release Testing

Validate the 1.1 release package. (Branch for 1.1 assumed)

1. On Download release candidate from hudson - https://ci.mifos.org/hudson/job/bi-1.1.x-archive/lastStableBuild/  (need link for sourceforge)

   Verify file against Checksums.

2. follow steps on BI install document

3. run BI server, load each report.  For BI 1.1, 18 reports should be included.

For each report: 

  • parameters are populated
  • report generates in PDF, HTML, and Excel,
  • Version is 1.0 for unchanged reports (check with Kay) and 1.1 for new or updated reports.
  • Reports each load, viewable

(16 Feb 2011) Release Results for 1.1: 

  - all reports executable for downloaded package

 - reports by versions:

1.1:

  • balanceOutstanding.
  • branchExpectedCashFlow.
  • centerCollectionSheet.
  • clientExit.
  • dueVsCollectedBranch.
  • dueVsCollectedCenter.
  • dueVsCollectedLoanOfficer.
  • groupCollectionSheetMPESA.
  • loanClassificationProduct.
  • loanOfficerDetailed.
  • loanOfficerPerformanceSummaryCumulative.
  • loanOfficerPerformanceSummaryDuringPeriod.
  • loansPendingApproval.
  • loansToBeDisbursed.
  • mfiProgress.
  • PESALoanDisbursalsExportSummary.

1.0 reports (version still shows 1.0 in i18n/org/mifos/bi/reports/*.properties):

  • balanceOutstandingBySourceOfFunds.
  • fundsMovement.
  • mifosTransactions.

Deployment Testing

  1. For cloud BI test instances, deploy using BI install document
  2. 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.
  3. Check version number for each report.

Reference

Master List