/
Unit Testing
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
Unit Testing
- anderson.pagtabunan
Owned by anderson.pagtabunan
Please navigate to these pages for specific unit testing scenarios.
Unit testing is done on these Flows and Apex triggers as logical changes were made either to cater a better course of the flow or some technical changes were made on how the flow is ran through.
Unit testing is divided into triggering sObjects below:
, multiple selections available,
Related content
Gift/Pledge Unit Testing
Gift/Pledge Unit Testing
More like this
Enhanced Domain: How to Test
Enhanced Domain: How to Test
Read with this
TAP - 1118 Improve Review Duplicate Outcome case creation
TAP - 1118 Improve Review Duplicate Outcome case creation
Read with this
TAPSS-845/TAP-902: MS Team - To check the logic and any bad code practice for the list of flows mentioned and merge if required
TAPSS-845/TAP-902: MS Team - To check the logic and any bad code practice for the list of flows mentioned and merge if required
Read with this
USYD Updates pledge status if gift/pledge recordtype is Pledge and Pledge Status is Active or Paid (subflow)
USYD Updates pledge status if gift/pledge recordtype is Pledge and Pledge Status is Active or Paid (subflow)
Read with this