You need to sign in to do that
Don't have an account?
HARSHIL U PARIKH
Is bulk testing is necessary or you can test via single record - get enough (>= 75%) code coverage and deploy it?
Hello Developers!
Need some advice on trigger testing. I had simple trigger 8 to 9 line worth. I wrote a test cases by passing single record (con.FirstName = 'Jon' rather than creating a for loop and add con.FirstName = 'Jon' + i).
I am getting 87% of code coverage by this single record passing and testing.
Do you guys think that I would be able to deploy it into the production OR I need to test trigger with bulk records and then only be able to deploy it. (well, I can try to deploy and see it but I am still developing my app further)
Thank you!
Need some advice on trigger testing. I had simple trigger 8 to 9 line worth. I wrote a test cases by passing single record (con.FirstName = 'Jon' rather than creating a for loop and add con.FirstName = 'Jon' + i).
I am getting 87% of code coverage by this single record passing and testing.
Do you guys think that I would be able to deploy it into the production OR I need to test trigger with bulk records and then only be able to deploy it. (well, I can try to deploy and see it but I am still developing my app further)
Thank you!
For e.g.: lets say you trigger has a DML statement inside of a loop
The above code will work fine if you are executing 1 record at a time but if you are doing a data import or something you will get
caused by: System.Exception: Too many SOQL queries: 101
Your trigger will break since you hit the the limit
(Refer this link for all the limits - https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_gov_limits.htm)
So if you write your test class in such a way that it tests for bulk record, positive test and negative test with assertions to make sure you always get expected results you are less lilkely to run into problems in production.
All Answers
Please check below post to learn about test classes and sample test class for every type if test classes
1) http://amitsalesforce.blogspot.com/search/label/Test%20Class
2) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html
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 .
Please let us know if this post will help you
You can deploy the trigger to production without testing the trigger for bulk. Salesforce will not stop you if your trigger is not tested for bulk. But I would strongly suggest to test your trigger for bulk as you will be sure that going into production your code will not break when it has to process upto 200 records at a time.
The reason I am little concern is that I have few trigger on the app that I am building and I have single record test cases for both of them.
For e.g.: lets say you trigger has a DML statement inside of a loop
The above code will work fine if you are executing 1 record at a time but if you are doing a data import or something you will get
caused by: System.Exception: Too many SOQL queries: 101
Your trigger will break since you hit the the limit
(Refer this link for all the limits - https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_gov_limits.htm)
So if you write your test class in such a way that it tests for bulk record, positive test and negative test with assertions to make sure you always get expected results you are less lilkely to run into problems in production.