+ Start a Discussion
ramesh babu 114ramesh babu 114 

best practices for test classes

best practices for test classes
sfdcMonkey.comsfdcMonkey.com
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 .

source : http://amitsalesforce.blogspot.in/2015/06/best-practice-for-test-classes-sample.html

i hope it helps you.
  Let me inform if it helps you and kindly mark it best answer if it helps you
thanks
Matrix ReturnsMatrix Returns
Understanding the workflow .If you understand the workflow you ll easly get 80% code covergare
Deepali KulshresthaDeepali Kulshrestha
Hi ramesh,

Please follow below step Best Practice for Test Classes:-

Make sure your code coverage is above 75%.

Doing so make sure that every use case should be covered in different scenarios mentioned below.

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.

Test method should static and no void return type.

Stating with salesforce API 28.0 test method can not reside inside non test classes.

@Testvisible annotation to make visible private methods inside test classes.

Test method can not be used to test web-service call out. Please use mock call out.

Data in User, profile, organization, AsyncApexjob, Corntrigger, RecordType, ApexClass, ApexComponent ,ApexPage objects can be accessed without (seeAllData=true) .

Accessing static resource test records in test class e,g List accList=Test.loadData(Account,SobjectType,'ResourceName').

Create TestFactory class with @isTest annotation to exclude from organization code size limit.

@testSetup to create test records once in a method and use in every test method in the test class.

Maximum number of test classes run per 24 hour of period is not greater of 500 or 10 multiplication of test classes of your organization.

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.

System.runAs will not enforce user permission or field level permission as the running user.

Refer bellow link:-

https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_testing_best_practices.htm


I hope you find the above solution helpful. If it does, please mark as Best Answer to help others too.

Thanks and Regards,
Deepali Kulshrestha
www.kdeepali.com
Ajay K DubediAjay K Dubedi
Hi Ramesh,

Best practices for writing test classes are:

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 the 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 the salesforce. We also use this to increase the governor's  
   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 methods 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.

I hope you find the above solution helpful. If it does, please mark as Best Answer to help others too.

Thanks and Regards,
Ajay Dubedi
www.ajaydubedi.com
Tien Le 488Tien Le 488
Hi,

Trailheads I've completed many so far recommend naming the test class following the apex class to be tested.  How come this isn't a best practice?  Looks like I will have to ask my developers what is the test class if there is one for a particular apex class under review.

Any feedback is appreciated.

Thanks,
Tien.