Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au
Skip to end of banner
Go to start of banner

TAP-1200/1222/1219 Issues Unit Testing

Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

« Previous Version 4 Next »

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:

  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

    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

  • No labels