Uploaded image for project: 'mod-data-import'
  1. mod-data-import

Set up Rancher env for EDIFACT invoice testing



    • Template:
    • Sprint:
      Folijet Sprint 108
    • Story Points:
    • Development Team:
    • Confidence factor:


      Set up Rancher env with modules and data needed for EDIFACT invoice testing. Thunderjet can help if questions about setting up any of the acq apps.

      • UI for orders, invoices, data import, finance, organizations, inventory (receiving?)
      • Finance app (and all the sample finance data from the hosted ref envs? or other sample data from TAMU?)
      • Organizations app (with vendors representing the 12 vendors with default profiles in https://docs.google.com/spreadsheets/d/1D2KW4zdurrYueoPLeu7P_J0wfdnAl6OMwm3KdOIC9xo/edit?usp=sharing)
      • Orders app, (with orders for each of the 12 vendors (some one-time, some ongoing))
      • Invoice app
      • Make sure sample invoices have POLs, titles, and vendor ref numbers that match the open orders

      Scenarios to test:

      • Thin thread: An invoice with one-time orders, no adjustments, all lines match to POLs, use the fund distribution from the POL)
      • An invoice with lines for one-time orders
      • An invoice with lines for ongoing orders
      • An invoice with invoice-level adjustments
      • An invoice with invoice line-level adjustments
      • An invoice with an exchange rate
      • An invoice with lines matching via vendor reference number instead of POL
      • An invoice with some lines matching via POL and some via vendor reference numbers
      • An invoice with some or all lines that do not match to POLs or vendor ref numbers (so the "else" field mapping logic for Description kicks in; if the invoice line is then linked to a POL, the POL title should update the invoice line description)
      • An invoice with an invoice line that matches to multiple POLs (no POL on the invoice, and the vendor ref number of the invoice line matches several POLs; in this case we would want the invoice line info to load without a POL link, and the user would link to the appropriate POL manually)
      • An invoice with a line that matches to an incorrect POL (so the invoice line needs to be unlinked and relinked to the correct POL, which will update the invoice line description and possibly fund distribution info)
      • An invoice with many lines that match to incorrect POLs (so the invoice lines need to be unlinked and relinked to the correct POLs, which will update the invoice line description, and possibly fund distribution info)
      • An invoice with fund distribution from the invoice, rather than the POL
      • An invoice that matches to POLs that do not have fund distributions (so the fund distribution info would need to be added manually to the invoice lines before approval)
      • An invoice with several invalid/missing POLs
      • An invoice with prices higher than available in the assigned funds (assigned budget will not have enough money in it; should not cause a problem until the invoice is approved, right?)
      • An invoice with lots of lines (serials renewal?)
      • An invoice that is a credit, or contains a credit
      • A duplicate invoice
      • An EDIFACT file with multiple invoices in it (to be sure that they are broken into separate invoices with the proper invoice lines)

        TestRail: Results


            Issue Links



                VRohach Volodymyr Rohach
                abreaux Ann-Marie Breaux
                0 Vote for this issue
                2 Start watching this issue



                    TestRail: Runs

                      TestRail: Cases