Skip to main content

Loading Test Data ... made my life easier

Hallooo...

I am still here, I forgot that I have a technical blog =)

Okay, I would like to share that something that maybe there for very long time, but I just utilized it recently.

My organization have something that we call Financial Calendar, it is different from our normal life calendar, where by if in our normal life a new year start on every 1 January, our financial start in different month.

Well, it is not big deal except in Salesforce we need to do test class, and most of our classes having logic such the object linked to calendar object, if new quarter come in populate the data etc.

Last time we just use @SeeAllData=true in order to access into this object from test class,but as you and I know it is not advisable as it may lead to other issue.

So we do something like this in our test class.We need to populate record for Financial Calendar in order to use it.

FinancialCalendar__c c1 = new FiscalCalendar__c();
.
.
.

The code goes down , to define the quarter.Oh, FYI, one record in FiscalCalendar store the quarter information such as year,quarter,begin quater date, end quarter date.Imagine if our logic to populate 6 quarter , not to include compare or search the quarter and year by user input plus if we have more than one class using the same object.

But at last, Salesforce introduce this cool stuff. Arrgghh!! Forget whatever code above.I directly query Financial Calendar record, export into .csv format and upload it into Static Resource.

Just to make this code reusable, I put it inside Test Data Factory class.

MyTestDataFactory class.Note FinancialCalendar is Static Resource Name.
@isTest
public class MyTestDataFactory {
    //to create Fiscal Year
    public static void createFinCal (){
         // Load the data from the static resource
         List<financialcalendar__c> lstCal = Test.loadData(FinancialCalendar__c.sObjectType, 'FinancialCalendar');
    
    }
}
MyTestClass
@isTest
public class MyTestClass {

  static testMethod void testReport(){
     Test.startTest();
        List<financialcalendar__c> cals=MyTestDataFactory.createFinCal ();
  //yourcode
  Test.stopTest();
  }
 }

Okay, done.While implementing this, I also faced some difficulty by assuming that the data is not inserted.So I try to put something like

insert lstCal;

right after loadData, and it give me an error because using load data is considered as insert.

*Clap*. Now we can have a mug of hot cocoa with some cookies =)

Comments

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 ) {