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

Gift/Pledge 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 26 Next »

Processes/Sub-flows


USYD Automate task for GA for Pledge (subflow)

Background of issue:

  • Task record is created multiple times after Gift Plege Status changed to Pending Review

  • Hard-coded Id is used in creating the Task record and must be queried dynamically

Unit testing:

  1. Open an existing Gift record on an account where Pledge Status is not Pending Review

    1. Update Pledge Status to Pending Review

  2. Check that a Task record is created for Gift Administration group


USYD AQC Donor Contact Type Auto-Updater (subflow)

Background of issue:

  • Found that changes will be made even if change on field is not exactly changed.

Fix/Change:

Specific testing on this flow’s added criteria to check if Usyd_Gift_Driver_Derivation__c = false can only be done through debug of the flow as this is set to false when flow execution gets to USYD Gift Driver Derivation (subflow).

Unit testing:

  1. Open a gift record and set Usyd_Gift_Driver_Derivation__c to false through anonymous apex.

update new AQB__Gift__c(
 Id = '[GIFTRecord_Id]',
 Usyd_Gift_Driver_Derivation__c = false
);

2. Open debug on this flow.

3. Debug on your Gift record and set the Record_Prior to a Gift record where related Account record is different.

4. Confirm that test path is as follows.


USYD Update Related Gift Implementation

Background of issue:

  • Found that an update on GIft Implemetation record will still be done even if prior Stage is equal to 5. GI - Kick Off.

Fix/Change:

  • Add a Filter Condition in getGiftImp (Get Record): where Stage does not equal to 5. GI - Kick Off.

Unit testing:

  1. Open a GIft Implementation record and make sure Stage is not 5. GI - Kick Off and Gift Pledge field is NOT populated with a GIft record.

  2. Navigate to the related Opportunity record and open any of its related Gift record.

  3. Do an update on the Gift record on any fields and save.

  4. Check the Gift Implementation record that the Stage is updated to 5. GI - Kick Off and Gift/Pledge field is populated.


USYD Updates pledge status if gift/pledge recordtype is Pledge and Pledge Status is Active or Paid (subflow)

Background of issue:

  • Logic is in a containing flow and must be subdivided for a more clear view of its function.

Fix/Change:

  • Translated in its own flow(subflow).

Unit testing:

Record Conditions

Result

Gift : Gift Type is Pledge OR
       Record Type is Pledge or Matching Gift
Gift : Balance Due is 0
Gift : Payments is greater than 0
Gift : Pledge Status is Active
Gift : Recurring Gift Link is null 

Gift : Pledge Status is updated to Paid

Gift : Gift Type is Pledge OR 
       Record Type is Pledge or Matching Gift
Gift : Balance Due is 0
Gift : Payments is greater than 0
Gift : Pledge Status is Active
Gift : Recurring Gift Link is NOT null
Gift : Recurring Gift Link Date Ended > Date Ended is NOT null, Current/Past Date

Gift : Pledge Status is updated to Paid

Gift : Gift Type is Pledge OR
       Record Type is Pledge or Matching Gift
Gift : Balance Due is 0
Gift : Payments is greater than 0
Gift : Pledge Status is Active
Gift : Recurring Gift Link is NOT null
Gift : Recurring Gift Link Type is Continuity Pledge with End Date

Gift : Pledge Status is updated to Paid

Gift : Gift Type is Pledge OR
       Record Type is Pledge or Matching Gift
Gift : Balance Due is greater than 0
Gift : Pledge Status is Paid

Gift : Pledge Status is updated to Active

Gift : Gift Type is Pledge OR
       Record Type is Pledge or Matching Gift
Gift : Balance Due is greater than 0
Gift : Pledge Status is null

Gift : Pledge Status is updated to Active

On testing, either an update is done using AQ’s batch payments insertion or through record update. This steps are done through simple record update.
  1. Open a Gift record and update fields with the following field values.

  2. Check that result are according to table result values.


USYD Update Credited Contacts and GRC Rollup (subflow)

Background of issue:

  • Logic is in a containing flow and must be subdivided for a more clear view of its function.

Fix/Change:

  • Translated in its own flow(subflow).

Unit testing:

  1. Create a Household account through Account Create and provide contacts with appropriate legal credit.

  2. Run a batch through AQ Batch with a gift or pledge and close the batch once all required fields are fulfilled.

  3. Once batch closes, check that the created gift record has Credited Contacts field is populated and GRC roll-up field is also populated(GRC roll-up may not be visible on page layout).

USYD Update Text Area Description (subflow)

Background of issue:

  • Logic is in a containing flow and must be subdivided for a more clear view of its function.

Fix/Change:

  • Translated in its own flow(subflow).

Unit testing:

  1. Open an existing Gift record and update its Description field.

  2. Check to see that Text Area Description field is updated(field may not be on page layout).

  • No labels