Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Current Owner:

Jeff Brewster

Test Plan: MIFOS Interface to Tally

Pre-test setup

  1. Install Tally 9, version 1.82 on test server "testgreen.mifos.org".
  2. Create branches, groups, and ledgers in Tally to match attached Light chart of accounts.
  3. Set up automatic numbering of vouchers in Tally

Todo:

  1. Data set with "Light MF" data
  2. Pentaho server - create testing area on Pentaho
  3. Report (test artifact)
  4. Finalize xml spec (Kay)

Generate data for report

  • generate report for 1st day of month, a single branch transactions
    • loan disbursal
    • loan repayment
  • generate report for 1st day of month, a two branch transactions
  • generate volume report - e.g. 1000 users, 1000 transactions
  • with mutliple GL's, have multiple loan products that point to two different ledgers

*data needs

    • disbursals, loan repayments, fee repayments (loan and client), adjustments, loan writeoff, reschedule, (reschedule means adjustments)

Test Cases - report generation = GL Interface Report

  • Generate reports to XML
    • XML file format can be downloaded and viewable (*nix file vs. windows file?)
    • compare to expected result. TBD - specific cases
  • Generate reports to PDF, default pentaho output.
    • check the data is accurate in the import xml file. - Rollup as the right amount.; right voucher type goes with with right transactions - receipt; payment; and journal. Refer to kay's spreadsheet on these proper mappings.
    • want xml to be generated correctly - just import to tally? Review xml to see if it matches specification
    • what if we import to a "badly configured" tally - what happens?

make sure the GL interface report matches spec.

Test cases - import to Tally

  • import daily report - date range 1 day
    • multiple days of transactions per import date
    • single branch
    • two branch
  • one bad branch; two good branches
    • large transaction report
    • large xml file - e.g. 2 week range of dates
    • transactions that are entered day late are the only ones that get reported for previous day - e.g. aug 31 txns entered on sept 1
    • 999 rounding - goes to it's own ledger
  • Criteria
    • response time - less than 10 sec?
    • accuracy of imported data - see below
    • appropriate ledger accounts updated
  • Import errors
    • import twice denied?
    • import invalid range - to<from
    • multiple days?
    •  

Test cases - Check vouchers in tally

  • Criteria
    • TBD - what to validate in Tally? - work with Kay
  • No labels