Test Class Best Practice

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

Comments

Post a Comment