“Testing stands as a pivotal phase within the Salesforce development lifecycle. When engaging in Salesforce coding endeavors, a direct promotion to production is averted. Instead, we conduct testing akin to Quality Assurance practices, albeit by scripting code. This avenue is made possible through the utilization of test classes, with the outcomes of these tests gauged in the form of percentages. Should the test result percentage meet or exceed 75%, only then is the code deemed suitable for deployment to production. This meticulous process is instituted to safeguard against any potential code disruptions.
Developers undertake testing, commonly referred to as unit tests, with the dual objectives of verifying code functionality and ensuring seamless project operation, free from errors. Unit tests encompass a range of elements or components, including:
- Apex classes
- Apex batches, queueable, and future methods
- Apex triggers
- Custom controllers”
“Benefits of Test Classes”
- “Test classes guarantee the desired functionality of our code.
- They facilitate conducting tests in bulk.
- They contribute to delivering superior-quality code to production organizations.
- They mitigate the expenses associated with bugs.”
“Approaches Employed in Test Classes”
“Test.startTest() and Test.stopTest() Methods
- startTest(): Marks the initiation of our test scenario.
- stopTest(): Marks the conclusion of our test scenario.
- System.Assert()
- System.AssertEquals()
- System.runAs()
- Test.isRunningTest()
- Test.LoadData()”
“Optimal Approaches for Crafting Test Classes”
“Guidelines for Constructing Effective Test Classes
- The minimum required code coverage for test classes is 75%, but it’s advisable to aim for complete coverage at 100%.
- Encompass both positive and negative scenarios during testing.
- Approach test class creation with a ‘load testing’ mindset by crafting data lists, inserting records, and evaluating functionality. Opt for list-based operations with DML statements rather than single records.
- Precede test classes with the @isTest annotation.
- Refrain from relying on existing data; generate new data within the test class context.
- Employ Test.StartTest() and Test.StopTest() in each test function.
- When testing multiple scenarios, consider utilizing distinct methods instead of amalgamating all logic into a single method. This approach enhances control over test class execution and facilitates result analysis on a per-method basis.
- Exclude integrations or email sending validations from test classes, reserving them for actual execution rather than testing.”
“Foundational Example Code for Apex Test Class”
“Apex Handling Class for Campaign Field Update:”
public class CampaignFieldUpdate {
public static void FieldUpdate(list<campaign> campaignlist){ //created a list of campaigns in method
for(campaign VarCampaign:campaignlist){ //applied for loop
if(VarCampaign.Generate_Webform__c==True){ //applied if condition
VarCampaign.Web_form_Url__c='https://www.algoworks.com/contact-us/'; //if condition true then field will be updated with this message
}
}
}
}
“Apex Trigger Implementing the Mentioned Handler Class:”
trigger CampaignFieldUpdateTrigger on Campaign (before insert,before update) {
if(Trigger.isinsert || Trigger.isupdate){
CampaignFieldUpdate.FieldUpdate(trigger.new);
}
}
“Test Class Targeting the Previously Mentioned Trigger:”
@istest
public class CampaignFieldUpdateTestClass {
public static testmethod void CampaignTest(){
campaign VarCampaign=new campaign(name='Test campaign',Generate_Webform__c=true);
test.startTest();
insert VarCampaign;
test.stopTest();
}
}