Be a champ in test class. Test classes from start to end.

For development of robust, error-free code, Apex Code requires the creation and execution of unit tests.Unit tests are class methods that verify whether a particular piece of code is working properly.


 Unit tests are written in Apex Code and annotated with the  annotation @testmethod. The test methods must provide at least 75% code coverage. Code coverage is calculated by dividing the number of unique Apex code lines executed during your test method execution by the total number of Apex code lines in all of your trigger and classes.

Defining a Test Method using the testMethod keyword

For defining  an Apex method as a 'test method',Define the method as static and add the keyword testmethod. 
Classes defined with the isTest annotation do not count against your organization limit of 2 MB for all Apex code. Classes annotated with isTest can be declared as private or public. 





@isTest






public class totestClass {
    static testMethod void myTest() {
      
     }
}



Test.startTest/Test.stopTest



These methods, Test.startTestand Test.stopTest, are used when testing governor limits. Or in other words, executing test scenarios with a larger data set.








static testMethod void testTeststartandEnd(){
    // Perform our data preparation.
    List<Account> accounts = new List<Account>{};
        
    for(Integer i = 0; i < 200; i++){
        Account a = new Account(Name = 'limit Account ' + i);
        accounts.add(a);
    }

    // Start the test, this changes governor limit context to 
    // that of trigger rather than test. 
    test.startTest();
  
    // Insert the Account records that cause the trigger to execute.
    insert accounts; 
  
    // Stop the test, this changes limit context back to test from trigger.
    test.stopTest();
  
    // Query the database for the newly inserted records.
    List<Account> insertedAccounts = [SELECT Name, Description 
                                      FROM Account 
                                      WHERE Id IN :accounts];
  
    // Assert that the Description fields contains the proper value now.
    for(Account a : insertedAccounts){
      System.assertEquals(
        'This Account is probably left over from testing. It should probably be deleted.', 
        a.Description);
    }
}












System.runAs()



System.runAs(), lets you write test methods that change user contexts to either an existing user or a new user. All of that user's record sharing is then enforced. 










System.assert()




    

  • System.Assert accepts two parameters, one (mandatory) which is the condition to test for and the other a message (optional) to display should that condition be false.
    • 

  • System.AssertEquals and System.AssertNotEquals both accepts three parameters; the first two (mandatory) are the variables that will be tested for in/equality and the third (optional) is the message to display if the assert results in false.
    • 




public class assertClass {
    public void insertAcct(String name, String extId) {
        Account acc = new Account(Name = name,External_ID__c = externltId);
        insert acc;
        System.assertEquals('Test',acc.Name);
    }
}










HttpCalloutMock For Apex Test Class





Check the below example nothing better then this :



https://developer.salesforce.com/blogs/developer-relations/2013/03/testing-apex-callouts-using-httpcalloutmock.html



http://www.joe-ferraro.com/2014/04/apex-unit-testing-test-data-and-test-setmock/






















@TestSetup







Any DML statement within the context of @testSetup will not count against your overall test class limits but SOQL statements will.









@iSTest
public class setupTest {   

    
    @testsetup
    static void createLead(){
        List<Lead> lstLead = new List<Lead>();        
        for(Integer i = 0 ; i<200 ; i++) {
            lstLead.add(new Lead(lastName = 'setup'+i , Company = 'SF'));
        } 
        insert lstLead ;
    }
    
   //Check whether records created in test method
   //is accessible or not
    public static testMethod void test(){
        System.assertEquals(200, [SELECT COUNT() FROM Lead Where company = 'SF']);
    }
}




Resource : Salesforce documentation










































Comments











Post a Comment



















Popular posts from this blog









Apex Trigger  Framework in Salesforce with best practise




















Image







                                                                  Trigger framework is not just needed for having single object per trigger guidance but also helps in different other reasons.     According to the trigger framework :     1) Create a single trigger for each object. 2) A handler class which will call Action or Apex Interface based Trigger Framework Implementation      One Trigger -One Object Policy    Framework Implementation    Bulkified Code     Avoid SOQL Queries or DML statements inside FOR Loops     Using Collections, Streamlining Queries, and Efficient For Loops      No  Hardcoding IDs        Types of Framework available :   1.Handler/Controller Framework   2.Lightweight Apex Trigger Framework (Source:  http://chrisaldridge.com/triggers/lightweight-apex-trigger-framework/ )       Handler Framewo...








Read more










Apex Classes as REST  Web Services in Salesforce





















       Introduction to Apex REST    Salesforce platform is amazing and its lets your create your own lightweight  REST API using Apex. You can use this REST API to access force.com data, by authenticating the caller/consumer of API using standard oAuth and return data format support JSON/XML, purely depends how you want return back the data    A few useful bits of information related to these REST APIs:   Use standard HTTP verbs: GET, POST, PUT, PATCH, DELETE, and HEAD.  You can use either HTTP or HTTPS.  Use standard security to authenticate your REST calls via OAuth 2.0.  Serialize your data in either XML or JSON format.    This is done by defining your Apex class with the  @RestResource  annotation to expose it as a REST resource. Similarly, add annotations to your methods to expose them through REST. For example, you can add the @HttpGet  annotation to your method to expose it as a REST resource that can be called by an HTTP  GET  request.       Ap...








Read more










Apex CPU Limit Error : after running into an Apex CPU limit error  whether anything is committed to the database 





















 In a batch that updates an object that then activates a trigger,  would it stop at the object level or at the trigger level or does it depend on  when the apex limit is hit?     Any governor limit, including Apex CPU timeouts, reverts all changes to the database for the  entire  transaction. That means no records are created, updated, deleted, undeleted, merged, converted, etc. The  only  exception to this rule is that any logs that are enabled will be preserved (in Setup > Monitoring > Debug Logs).    In the case of a batch, if it occurs in the start method, the entire batch is aborted, while '   if it occurs during an execute function, only that single batch is aborted (but prior batches are already committed, and future batches may still successfully commit), and    in the finish method, a governor limit would prevent chaining calls, sending emails, etc.      








Read more