function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Nagma KhanNagma Khan 

how to write a test method of the Trigger ?

hi please any how to write a test method ?

// trigger on the case object and count the sum of the related case of the particual Account.
trigger coundSumofCase on Case (after insert,after update) {
    set<id> setid=new set<id>();
    if(trigger.isInsert){   
    for(case c:trigger.new){
        setid.add(c.accountid);
    }
    list<Account> listAccount=[select id,sum_of_case__c from account where id in:setid];
    list<case> listCont=[select id from case where accountid in:setid];
        for(account a:listAccount){
            a.sum_of_case__c=listCont.size();
        }
        update listAccount;
}
    if(trigger.isUpdate){
        for(case c:trigger.new){
            setid.add(c.accountid);
        }
        list<account> listAccount=[select id,sum_of_case__c from account where id in:setid];
        list<case> listcont=[select id from case where accountid in:setid];
        for(account a:listAccount){
            a.sum_of_case__c=listcont.size();
        }
        insert listAccount;
    }
}
BALAJI CHBALAJI CH
Hi Nagma,
You just need to create a case with Account in Test Class for code coverage. As you are also using Update event, you need to update the Case in the Test Class for code covergare.
Please find below Test Class which gives code coverage for above Trigger:
@isTest
public class coundSumofCase_Test {
    
    @testSetup 
    public static void datasetup() 
    {
        Account ac = new Account(Name = 'Test Account');
        Insert ac;
    }
    
    public static testmethod void method1()
    {
        Account ac = [select id, name, sum_of_case__c from Account limit 1];
        Case c = new Case(subject ='Test', AccountId = ac.id);
        insert c;
    }
}



Let us know if that helps you.

Best Regards,
BALAJI
Nagma KhanNagma Khan
hi BALAJI CH

its not coverage update part only show 58 %
 
Amit Chaudhary 8Amit Chaudhary 8
I will recommend you to start using trailhead to learn about test classes
1) https://trailhead.salesforce.com/modules/apex_testing

Also please check below post
1) https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_qs_test.htm
2) https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_testing_example.htm
3) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html

You write a test class for this the same way that you would any other:

- Set up some data for the Trigger to access (in this case it looks like account and case)
- Instantiate the Trigger.
- Verify the behaviour with asserts.

Please try below code
@isTest
public class coundSumofCaseTest 
{
    public static testmethod void method1()
    {
        Account ac = new Account(Name = 'Test Account');
        Insert ac;

        Case c = new Case(Status ='New', Priority = 'Medium', Origin = 'Email',subject ='Test', AccountId = ac.id);
        insert c;
		
		update c;
		
    }
}



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
Nagma KhanNagma Khan
its fine code Amit Chaudhary
Arvind KumarArvind Kumar
Hi Nagma,

In above trigger (trigger.isUpdate​) :
You must be use update listAccount instead of insert listAccount in trigger update action (trigger.isUpdate​). 

This is test class for your trigger. It will give 100% code coverage. Implement this test class for your trigger code coverage.
@isTest
   public class TestRollupHelper
   {
          public static testmethod void createRecords()
          {
                 Account accObj = new Account();
                 accObj.Name = 'TestAccount';
                 insert accObj;
                 
                 Case csObj = new Case(Status ='New', 
                                       Priority = 'Medium', 
                                       Origin = 'Email', 
                                       accountId = accObj.Id);
                 insert csObj;
                 
                 csObj.Status ='New';
                 csObj.Priority = 'Low';
                 csObj.Origin = 'Phone'; 
                 
                 
                 update csObj;
          }
   }


Please mark as best answer to my answer. If it is helpful for you.

Thanks,
Arvind Kumar

Suresh(Suri)Suresh(Suri)

Hi Nagma,

In your trigger using after insert and after update So if you facing any DML exceptions add one line code in your trigger for above test class

Test class will never fail
 

try {
            // If you can't manipulate the Apex methods input or database state to cause a
            // DMLExcpetion then you can deliberately cause the DMLException to improve your
            // code coverage and check the functionality of the exception handling.
            // You could also use a flag set from your test method to indicate that the 
            // exception should be thrown
            if(!Test.isRunningTest()) {
            insert listAccount;
            }
        }

    catch (DMLException ex) {
    // Existing exception handling.        
    }
Thanks,
Suresh