Learn how to use dependency injection to mock read-only fields, such as formula fields and child relationships in your tests.
A while ago we explored the Mock Data Layer Pattern, which allows us to mock virtually any relationships between records within your tests. This is especially handy when trying to improve the performance of these tests - more details here.
Now, how can we mock formula fields and read-only child relationships if they are, well, read-only fields? 🤔
Mocking values in read-only fields
For this exploratory project, we will use a not-so-realistic scenario with parent and child accounts, but the intent is to create a test for the Account Trigger Handler that will use a Mock Field Reader and a Mock Data Layer.
The Mock Field Reader will be used so we can mock two read-only fields on the Account object.
Child_Accounts__r, a read-only child relationship on the parent record
External_URL__c, a formula field on the child record
The trigger handler logic will update the following field:
Based on the following formula field:
⚙️ Files used in this project
force-app main default classes ◦ AccountTriggerHandler ◦ AccountTriggerHandlerTest ◦ FieldReader ◦ IFieldReader ◦ MockFieldReader ◦ TestUtils triggers ◦ AccountTrigger
⚡️ Show me the code!
To respect the injected dependency, these methods must be present on both the real instance of the field reader (
FieldReader ) and the mock instance of the field reader (
Object getFieldValue(SObject record, String fieldName)
This method is used to retrieve the mock values of formula fields. It returns an
Object that can later be casted as different types, such as
SObject getFieldRecord(SObject record, String fieldName)
This method is used to retrieve the mock values that represent a single record. It returns an
List<SObject> getFieldRecords(SObject record, String fieldName)
This method is used to retrieve the mock values that represent a list of records, such as a child relationship. It returns a list of
There's only one method used to set the values, and it's only present on the mock instance of the field reader (
addValueToField(SObject record, String field, Object value)
This method adds the field/value pair to a map of mocked values, indexed by the record Id.
In the repository on Github you will find a trigger handler class and its respective test class with the usage of this Mock Field Reader.
Snippet from the AccountTriggerHandler: pay attention to how the following methods are being used:
And in the AccountTriggerHandlerTest you can see how these read-only fields can be mocked, using the method
With this code and the Mock Field Reader, it becomes easy to mock read-only fields used in the tests.
I hope that helps!
Originally published on matheus.dev
Top comments (0)