Skip to main content

Experiment : Test.loadData . Upload test data with static resources

Test.loadData is a method that enables us to create test data by using Static Resource. This was released quite sometimes but I haven't use it intensively. I experienced using it to load data in bulk because I wanted to test governor limit.

Recently we plan to use this on our project instead of using test data factory.Pushing test data using csv files are much easier compare to code insertion and define relationship.

I did some simple proof of concept using code below :

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
@isTest
private class DataUtil {
    static testmethod void testLoadData() {
        // Load the test accounts from the static resource
        List<sObject> ls = Test.loadData(Account.sObjectType, 'AccountData');
        // Verify that all 3 test accounts were created
        System.assert(ls.size() == 3);

        // Get first test account
        Account a1 = (Account)ls[0];
        String acctName = a1.Name;
        System.debug(acctName);
        
        a1.Name ='New Name';
        
        update a1;
        
        Account a2 =[Select Id,Name from Account Where Name ='New Name'];
        
  //check if account get updated
        system.debug('After update a2 '+ a2.Name);
        
        Contact contact =new Contact (FirstName='TestContact',LastName='Lasting',AccountId=a2.Id);
        insert contact;
        
        Contact contact1=[select FirstName from Contact Where AccountId=:a2.Id];
        
        //yes , able to create contact on the account
        system.debug('After update contact1'+ contact1.FirstName);
        
        delete a2;
        
        List<Account> listAccount=[select Id from Account where Name='New Name'];
        //yes, able to delete
        system.assertEquals(0,listAccount.size());

    }
}

1. Can I update the record that I have loaded?
    Yes
2. Can I create child to the record that I have loaded?
     Yes
3. Can I delete the record that I have loaded?
    Yes.
4. Will insert trigger cover using Test.loadData?
    Yes, but validation rules is still applied.
5. Can I define relationship for example between Account, Opportunity and Contact?
     Yes you can.You can define it with mockup id in the column like below

When defining relationship, make sure that you run loadData method in proper order : master first then follow by child.In the example below, load Account first then Opportunity then Contact.

1
2
3
4
        // Load the test data  from the static resource in proper order
        List<sObject> lstAccount = Test.loadData(Account.sObjectType, 'AccountData');
  List<SObject> lstOpportunity = Test.loadData(Opportunity.sObjectType,'OpportunityData');
        List<SObject> lstContact = Test.loadData(Contact.sObjectType,'ContactData');

Some useful links to check out  :


Hope this help.

Comments

  1. This comment has been removed by a blog administrator.

    ReplyDelete
  2. does test.UploadData() also run Triggers and Process Builders that are link to the object? I guess i'm not fully understanding if test.uploadData() actually uploads the data or is it just a static code that does not effect triggers and process builders what so ever.

    ReplyDelete

Post a Comment

Popular posts from this blog

Search Solution Basics

When is it a good time to create a customized search solution? You're developing an external knowledge base for user support. You're in the mood for a fun Friday night. The sales reps just started using the Sales Cloud in Lightning Experience. You want to put your company branding in the search bar. What differentiates SOSL from SOQL? Syntax SOSL searches the search index instead of the org database. SOSL searches more efficiently when you don't know in which object the data resides. All of the above. SOSL works with: REST only SOAP only REST, SOAP, and Apex SOQL only What does a search for a single object look like in SOSL? FIND {cloud} RETURNING Account FIND in ACCOUNT RETURNING "cloud" FIND "cloud" in ACCOUNT FIND (cloud) RIGHT NOW! What does a search for multiple objects look like in SOSL? FIND {sneakers} RETURNING ALL ARTICLES FIND {sneakers} in ALL OBJECTS FIND {sneakers} RETURNING Product2, Content

Process Builder is not fired when field update is called from Approval Process

Scenario In Final Approvals section ; in Approval Process we have field update to update Status field. In Process Builder , we have some action that need to be done when Status field is updated in Approval Process.However this process builder is not fired. Solution To handle this, in Field Update in Approval Process , check Re-evaluated Workflow Rules after Field Change as picture below. What happen if field updated from Approval Process. Workflow - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Process Builder - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Trigger - will fire if conditions are matched This is explained in article here  . Field Updates That Re-evaluate Workflow Rules If  Re-evaluate Workflow Rules After Field Change  is enabled for a field update action, Salesforce  re-evaluates all workflow rules on the object if the field update results in a change to the value of the fi

Tips and Tricks : Test class for Invocable method

Issue : I got 100% coverage in my sandbox but when run validation for deployment it returns 0% coverage It turn out that in my sandbox, I am depending on Process Builder to Invocable Apex class, as long I manipulate test data that fire Process Builder it will call Invocable class. This is not useful when deploying it to Production although it gets deployed together with Process Builder. The correct way is to direct call Invocable method inside test class itself. Example of class : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 global class MyCustomObject_StatusUpdate_Util { @InvocableMethod ( label = ' Update Quote Status ' ) public static void updateQuote ( Request [] requests ) { Set < Id > setOppId = new Set < Id >(); List < SBQQ__Quote__c > listQuoteToUpdate = new List < SBQQ__Quote__c >(); for ( Request request : requests ) {