Module Standup

  • Configuration has been defined and validated, and it appears to be working properly.
    • Parameters
      • Do the parameters in DEV or TEST match with REF?
        • Ron needs Dan Clark's help for this.
    • Maintenance Values (see exceptions below)
      • Some values exist in REF and some still exist in templates (Data Conversion Team KFS_SOURCE_OF_DATA.xlsx)
        NOTE: If there is a "Y" the values are pulled from REF and put back into a template.
  • Workflow and User Access has been validated.
    • This means that we have verified that a person assigned to a particular role receives the appropriate workflow requests, and has the appropriate access to KFS & docs.
    • This does NOT mean that the people who are assigned to these roles are the ultimate individuals who will have the role (in other words, we did NOT define the specific individuals who will be in those roles).
  • Batch processes for the modules are functioning properly.
    • Primarily Sherry
  • Customizations that were available in Dev by 1/14 have been validated and are either in Test or are ready to migrate to Test.
  • Data Conversion that was complete and available in Dev by 1/14 has been validated.
  • All customizations have been identified and are listed on one of the Customizations HQ pages.

Smoke Tests

"Smoke test" a (non-production) environment after rebuild or refresh

Basic

This will tell you if KFS and Cynergy are working
Main Menu > Transactions > Financial Processing > Distribution of Income and Expense
Description = "test edoc"
under 'From' click "Add"
Account = "G254700"
Object = "6100"
Amount = "50.00"
under 'To' click "Add"
Account = "G254200"
Object = "6100"
Amount = "50.00"
click "Save"
click "Submit"
Backdoor log in as the Approver for the edoc you just created: "rmy1"
click "Action List"
click on the edoc you created
click "Approve"

Identity (Sarah)
  • Add a person to a Role
  • Search for a person by Role
  • Change Role to Inactive
Chart of Accounts (Dave & Shelley)
  • Beginning balances on operating accounts are correct
  • Monthly activity is correct (all available months)
  • A&L account mapping is correct
  • A&L account beginning balances are correct
    • These first 4 Dave uses Brio queries so he would probably need to continue
  • Account Roles (Fiscal Officer,Account Supervisor, Account Manager)
    • Could be automated may already have scenario
  • Org structure
    • Could be automated, but Dave would need to verify the amounts
  • Sub Fund and Higher Ed Function tables
    • Could be automated, but Dave would need to verify the amounts
  • Validate Maintenance e-docs
  • Validate Account, Sub-Account, Sub-Object Code e-docs
  • Check route log
  • Check action list
  • Check Accounts for sufficient data: Fiscal Officer, Account Supervisor, Account Manager
    • Could be automated may already have scenario (see above too)
      NOTE: Shelley is working with Sarah to get the roles worked out (ex. Account Delegate & Org Reviewer)
Financial Processing (Sherry)
  • User access for non-employees
  • Use e-docs to create transactions
    • Advance Deposits - to ensure the bank parameters came in correctly
    • Internal Billing - send it through for approval (that is where the backdoor comes in
    • JV - checks on the roles (again backdoor in)
  • Backdoor in and approve transactions
    Note: Create e-docs that will support smoke testing for Capital Assets and Contracts and Grants
Financial Processing (Cathy)
  • Does the calendar widget work?
    • Doc search: does it default to today when I just hit search
    • Can I use the calendar wizard to select docs prepared by date
    • Verify that docs before the refresh are gone
  • Use e-docs to create transactions?
    • Disbursement Voucher, can I select an employee to pay?
    • Is the bank showing?
    • Save a doc and make sure pending entries are created
    • Transfer of Funds looking at Transfer object rules, MT subtype and TN subtype
  • Backdoor in and approve transactions
    • Select accounts by Fiscal Officer
    • Then Back Door as Fiscal Officer
PURAP (Susan)
  • Validate values for all PURAP and PDP maintenance values
  • Create a Requisition for an APO, run it through Payment Request
  • Try saving a Requisition with bad data, like phone number, and get an error message
    • Search for the Requisition and see if you get the error message in your Search Results
  • Create a Requisition for a non-apo run it through PDP (as far as you can)
    (In our testplan, we will indicate the Scenarios that are part of the "smoke" test to include those above as specific tests)
    Note: Create e-docs that will support smoke testing for Capital Assets and Contracts and Grants
Labor Distribution (Greg)
  • Validation requires data being loaded (Venky)
    • Replicated the data to represent the 12 periods
    • Added benefits rows
    • Changed the flat $100 salary to some random number
    • Random numbers used for benefits
  • Create Salary Expense Transfer (Bob)
Capital Assets (Rina)
  • Validate the maintenance values for the module have been set up as per https://confluence.cornell.edu/x/jhYUBw
  • Validate CA Module parameters related to batch jobs
  • Validate Capital Asset Builder GL Transactions (coordinate to ensure Financial Transactions have occurred in advance)
  • Validate Capital Asset Builder AP Transactions edoc (coordinate to ensure Capital Assets have been purchased in advance)
  • Validate actions on an existing asset
  • Validate conversion of asset data
  • Validate permission, work flow and roles
Contracts and Grants (Rina)
  • Validate maintenance values for the module.
  • Validate conversion of proposals and awards
  • Validate manual creation of proposals
  • Validate manual creation of awards
Effort Certification (Rina)
  • Validate the maintenance values for the module have been set up as per https://confluence.cornell.edu/x/eQEUBw
  • Validate EC Module parameters related to batch jobs
  • Run EC Extract Batch Job (using sjc37 for running batch jobs)
  • Validate `Effort Certification Extract Build' report
  • Run EC Create Batch Job (using sjc37 for running batch jobs)
  • Validate Effort Certification edocs created
  • Validate approval of Effort Certification
  • Validate permission, workflow and roles

End to End

Modules

  • No labels