Thanks to developments in the community, such a verbose pattern is no longer necessary to mock in Apex.
As a first stop, I recommend checking out UniversalMock.
As a second stop, I recommend checking out dml-base where I've repurposed the pattern in this repository, streamlined it, to this new world order!
Salesforce APEX is unique to other OO Languages in that we can use SOQL/SOSL or DML in-line anywhere within the code base. Developers can quickly and immediately author a query, or insert a collection of records in the class they are currently working.
With great power comes great catastrophe.
With some discipline, data access in Apex can be streamlined to a single pattern. This pattern allows for the collocation of all queries and dml statements in Data Access Modules, by SObject. Each module is four Apex Classes. The classes are named for the SObject and their role in the module. Each module extends a core DmlInterface Module.
Nearly all SObjects support DML operations of INSERT, UPDATE, UPSERT, and DELETE. In support of this, the DML Module describes an SObject generic method for each of these DML statements. The DML Module is a closed interface, extended by your SObject DAI.
DmlInterface describes the four DML methods available to SObjects.
Extended by your DAI Interface.
public interface DmlInterface {
void insertRecords(List<SObject> newRecords);
void updateRecords(List<SObject> records);
void upsertRecords(List<SObject> records);
void deleteRecords(List<SObject> records);
}DmlBase is the runtime implementation of the Dml methods.
Extended by your DA class.
public abstract class DmlBase implements DmlInterface {
public void insertRecords(List<SObject> newRecords) {
insert newRecords;
}
public void updateRecords(List<SObject> records) {
update records;
}
public void upsertRecords(List<SObject> records) {
upsert records;
}
public void deleteRecords(List<SObject> records) {
delete records;
}
}DmlBaseMock is the mock implementation of the Dml Methods. This class is a complete mock of the database DML implementation. For example, an inserted record should be given an ID or an updated record must have an ID. Data is stateful within the Mock and passed by reference to the associated DAMock.
Extended by your DAMock class.
public abstract class DmlBaseMock implements DmlInterface {
protected Map<Id, SObject> Records;
public MockSObjectBuilder Builder;
private static final String ID_FIELD = 'Id';
public DmlBaseMock(Map<Id, SObject> records, Schema.SObjectType objectType) {
this.Records = records;
this.builder = new MockSObjectBuilder(objectType);
}
public List<SObject> getRecords() {
return this.Records.values();
}
public void insertRecords(List<SObject> newRecords) {
for (SObject record : newRecords) {
if (record.get(ID_FIELD) != null) {
throw new DmlException('Cannot insert a record with an ID.');
}
Id recordId = builder.getMockId();
record.put(ID_FIELD, recordId);
this.Records.put((Id)recordId, record);
}
}
public void updateRecords(List<SObject> records) {
for (SObject record : records) {
if (record.get(ID_FIELD) == null) {
throw new DmlException('Records to update must have a record Id.');
}
this.Records.put((Id)record.get(ID_FIELD), record);
}
}
public void upsertRecords(List<SObject> records) {
for (SObject record : records) {
if (record.get(ID_FIELD) == null) {
Id recordId = builder.getMockId();
record.put(ID_FIELD, recordId);
}
this.Records.put((Id)record.get(ID_FIELD), record);
}
}
public void deleteRecords(List<SObject> records) {
for (SObject record : records) {
if (record.get(ID_FIELD) == null) {
throw new DmlException('Records to delete must have a record Id.');
}
this.Records.remove((Id)record.get(ID_FIELD));
}
}
}Test class for the DmlBase class.
@isTest
private class DmlBaseTest {
// Test Methods for the DMLBase implementation.
}In following this pattern, developers will create/edit/maintain the four following classes per SObject for each Data Access Module.
The Interface which defines the method signatures that the DA and DAMock implementations are responsible for.
Note that the DAI extends the DmlInterface. This means that any class that implements the AccountDAI (AccountDA/AccountDAMock) must implement both the queryLimittedAccounts and searchAccounts methods as well as the methods on the DmlInterface. However, the DmlBase and DmlBasemock contain the implementation for the DmlInterface - so the AccountDA and AccountDAMock can extend these respectively to satisfy their complete interface contract with the AccountDAI.
AccountDAI describes the queries that must be implemented by AccountDA and AccountDAMock.
public interface AccountDAI extends DmlInterface {
// Adds the query methods to the list of methods from DmlInterface
List<Account> queryLimittedAccounts(Integer limitter);
List<Account> searchAccounts(String searchString);
}The runtime implementation for Data Access. Methods are implemented per the DAI.
Implements the queries described in AccountDAI, and extends the DmlBase to satisfy the DmlInterface that AccountDAI extends.
AccountDA uses SOQL Queries to get recent accounts from the Salesforce Database.
public inherited sharing class AccountDA extends DmlBase implements AccountDAI {
public static final Integer MAX_RESULTS = 5;
public List<Account> queryLimittedAccounts(Integer limitter) {
limitter = Integer.valueOf(limitter);
return [
SELECT Id,
Name
FROM Account
ORDER BY CreatedDate ASC
LIMIT :limitter];
}
public List<Account> searchAccounts(String searchString) {
String escapedTerm = String.escapeSingleQuotes(searchString) + '*';
List<List<SObject>> results = [
FIND :escapedTerm IN ALL FIELDS
RETURNING
Account (Id, Name)
LIMIT :MAX_RESULTS];
return results[0];
}
}A Mock Implementation for Data Access. Methods are implemented per the DAI. Class is annotated @isTest.
Implements the queries described in AccountDAI, and extends the DmlBaseMock to satisy the DmlInterface which AccountDAI extends.
AccountDAMock returns fake account data instead of hitting the Database.
@isTest
public inherited sharing class AccountDAMock extends DmlBaseMock implements AccountDAI {
public Map<Id, Account> Accounts;
public Boolean IsSuccess = true;
private static final Schema.SObjectType ACCOUNT_TYPE = Schema.Account.SObjectType;
private static final String ACCOUNT_NAME = 'Account';
public AccountDAMock() {
super(new Map<Id, Account>(), ACCOUNT_TYPE);
this.Accounts = (Map<Id, Account>)super.Records;
}
public List<Account> queryLimittedAccounts(Integer limitter) {
isQueryException();
List<Account> foundAccounts = new List<Account>();
Integer count = 0;
for(Account acc : Accounts.values()) {
if (count < AccountDA.MAX_RESULTS) {
foundAccounts.add(acc);
}
count++;
}
return foundAccounts;
}
public List<Account> searchAccounts(String searchString) {
isQueryException();
List<Account> foundAccounts = new List<Account>();
Integer count = 0;
for(Account acc : Accounts.values()) {
if (count < AccountDA.MAX_RESULTS && acc.Name.contains(searchString)) {
foundAccounts.add(acc);
}
}
return foundAccounts;
}
private void isQueryException() {
if (!IsSuccess) {
throw new QueryException('Forced Exception from AccountDAMock.');
}
}
}A Test for the runtime Data Accessor (DA).
@isTest
private class AccountDATest {
// ...Unit Tests for AccountDA
}