Activity › Forums › Salesforce® Discussions › What are the best practices while writing test classes in Salesforce?

Tagged: , , , , , , , , , , ,

  • Avnish Yadav

    Member
    August 7, 2018 at 5:56 am

    Hi Anjali,

    The Apex Test Class Best Practices:-

    1.  Use @isTest at the Top for all the test classes
    2. Always put assert statements for negative and positive tests
    3. Use the @testSetup method to insert the test data into Test class that will flow all over the test class.
    4. Always use Test.startTest() and Test.stopTest() doing this it will increase the governor limit of salesforce. We also use this to increase the governor limit.
    5. Use System.runAs() method to test the functionality in user Context.
    6. Do not put (seeAllData = true) in test class otherwise, use it for exceptional cases.
    7. Avoid Using Hard Coding Ids anywhere in test Class or any apex class.
    8. Please make sure that each class has a minimum of 75% coverage and also the main functionality has been covered. If possible increase code coverage up to 95%.
    9. All class method must be tested for at least 200 records and keep the real scenarios in mind.
    10. Only one Test.startTest() and Test.stopTest() statement can be in a method, and no of Test.startTest() and Test.stopTest() statement in any test class depend upon the test methods.

    Thanks.

  • Parul

    Member
    September 23, 2018 at 8:49 am

    Please follow below salesforce Best Practice for Test Classes :-

    1. Test class must start with @isTest annotation if class class version is more than 25
    2. Test environment support @testVisible , @testSetUp as well
    3. Unit test is to test particular piece of code working properly or not .
    4. Unit test method takes no argument ,commit no data to database ,send no email ,flagged with testMethod keyword .
    5. To deploy to production at-least 75% code coverage is required
    6. System.debug statement are not counted as a part of apex code limit.
    7. Test method and test classes are not counted as a part of code limit
    9. We should not focus on the percentage of code coverage ,we should make sure that every use case should covered including positive, negative,bulk and single record .
    Single Action -To verify that the the single record produces the correct an expected result .
    Bulk action -Any apex record trigger ,class or extension must be invoked for 1-200 records .
    Positive behavior : Test every expected behavior occurs through every expected permutation , i,e user filled out every correctly data and not go past the limit .
    Negative Testcase :-Not to add future date , Not to specify negative amount.
    Restricted User :-Test whether a user with restricted access used in your code .
    10. Test class should be annotated with @isTest .
    11 . @isTest annotation with test method is equivalent to testMethod keyword .
    12. Test method should static and no void return type .
    13. Test class and method default access is private ,no matter to add access specifier .
    14. classes with @isTest annotation can't be a interface or enum .
    15. Test method code can't be invoked by non test request .
    16. Stating with salesforce API 28.0 test method can not reside inside non test classes .
    17. @Testvisible annotation to make visible private methods inside test classes.
    18. Test method can not be used to test web-service call out . Please use call out mock .
    19. You can't send email from test method.
    20.User, profile, organization, AsyncApexjob, Corntrigger, RecordType, ApexClass, ApexComponent ,ApexPage we can access without (seeAllData=true) .
    21. SeeAllData=true will not work for API 23 version eailer .
    22. Accessing static resource test records in test class e,g List<Account> accList=Test.loadData(Account,SobjectType,'ResourceName').
    23. Create TestFactory class with @isTest annotation to exclude from organization code size limit .
    24. @testSetup to create test records once in a method and use in every test method in the test class .
    25. We can run unit test by using Salesforce Standard UI,Force.com IDE ,Console ,API.
    26. Maximum number of test classes run per 24 hour of period is not grater of 500 or 10 multiplication of test classes of your organization.
    27. As apex runs in system mode so the permission and record sharing are not taken into account . So we need to use system.runAs to enforce record sharing .
    28. System.runAs will not enforce user permission or field level permission .
    29. Every test to runAs count against the total number of DML issued in the process .

  • William

    Member
    February 27, 2019 at 6:15 am

    Test methods and test classes are not counted as part of Apex code coverage.

    While only 75% of your Apex code must be covered by tests, your focus shouldn't be on the percentage of code that is covered. Instead, you should make sure that every use case of your application is covered, including positive and negative cases, as well as bulk and single records. This should lead to 75% or more of your code being covered by unit tests.

    1.      These classes should all use the @isTest annotation.

    2.      All test methods should be put in a separate class from the actual class where the method to be tested resides.

    3.      Test data creation should be done in a separate Utility class or in a test method annotated as ‘@testSetup‘.

    4.      Each test method should follow the signature — ‘@isTest static void myTest()‘ or ‘static testMethod void myTest()‘.

    5.      Always put assert statements for negative and positive tests

    6.      Use the @testSetup method to insert the test data into Test class that will flow all over the test class.

    7.      Always use Test.startTest() and Test.stopTest() doing this it will increase the governor limit of salesforce. We also use this to increase the governor limit.

    8.      Only one Test.startTest() and Test.stopTest() statement can be in a method, and no of Test.startTest() and Test.stopTest() statement in any test class depend upon the test methods.

    9.      Use System.runAs() method to test the functionality in user Context.

    10.  Do not put (seeAllData = true) in test class otherwise, use it for exceptional cases.

    11.  Avoid Using Hard Coding Ids anywhere in test Class or any apex class.

    12.  Please make sure that each class has a minimum 75% coverage and also the main functionality has been covered. If possible increase code coverage up to 95%.

     

Log In to reply.

Reply

Subscribe

Popular Salesforce Blogs

Popular Salesforce Videos

Report

Harassment or bullying behavior
Harassment or bullying behavior
Contains mature or sensitive content
Contains misleading or false information
Mobile App Reported Contents
Contains abusive or derogatory content
Contains spam, fake content or potential malware

Block Member?

Please confirm you want to block this member.

You will no longer be able to:

  • See blocked member's posts
  • Mention this member in posts
  • Invite this member to groups
  • Message this member
  • Add this member as a connection

Please note: This action will also remove this member from your connections and send a report to the site admin. Please allow a few minutes for this process to complete.

Report

You have already reported this .