TAP-1200/1222/1219 Issues Unit Testing

Background of issue:

• Batch processing in closing an AQ Batch record are causing these issues

  • Multiple updates on triggering record and is causing Apex CPU Limit to exceed.

  • Multiple updates on triggering record and is causing duplicate updates on a single record.

  • Multiple updates on triggering record and is causing SOQL Limit to exceed.

  • Multiple updates on triggering record and is causing SOQL Limit to exceed.

• Joining accounts using the Join Utility on Contact page is causing Apex CPU Limit to exceed.

Unit testing:

• This unit testing steps can produce multiple gift and transaction records that would typically fail on the last build before this Jira’s fix

• This unit testing aims to check that no errors and failures of the above issues would come out of the testing

1. Intial records creation

   1. Create a single batch record and create multiple batch item records across multiple accounts

      1. different Entry Types

      2. different Schedule Types, this is to sample multiple Transaction records to be created

         Open

         

   2. Confirm that the batch successfully closes

   3. if the batch fails, Utility log log record will be created

2. Payment batch creation

   1. Create a single batch record to create a payment across all created transactions under all the gift records in all the accounts from the intial batch created

   2. Confirm that the batch successfully closes

      1. confirm to see that all gift records' balances are 0 and transactions are created to act as payment to the intial transaction records created

   3. if the batch fails, Utility log log record will be created

3. Payment reversal batch creation

   1. Create a single batch record to create reversal payment across all created transactions under all the gift records in all the accounts from the payment batch created

   2. Confirm that the batch successfully closes

      1. confirm to see that all gift records' balances are 0 and transactions are created to act as payment to the intial transaction records created

   3. if the batch fails, Utility log log record will be created

Write Off Process:

1. Select or create a new Open Batch

2. Click on Batch Items

3. Select an Account that has a suitable Gift/Pledge record to be written off

4. Select Pledge Write Off as Entry Type

5. Select any value as the Write Off Notation

6. Once a Write Off Notation, a screen will pop up with the Open Pledges associated with the chosen Account. Select the Pledge record/s

   Open

   

7. Click on Write Off checked Transactions

8. A screen will pop up to enter the amount that is to remain if it is just a partial Write Off. If it is a full Write Off, leave the Balance as 0.00 and click on Write Off Transaction

9. Go back to the Batch record and click on Close Batch

10. Confirm Close

11. Once the Batch has finished processing, navigate to the Gift/Pledge record that has been written off and go to its Related tab

12. On the Transactions related list, there should be at least two records. One for the original Pledge amount, and another for the Write Off transaction.

13. Both records will have the Write Off? Checkbox checked

14. The chosen Write Off Notation will be reflected on the Write Off Transaction’s Pledge Write Off Notation field