+ Start a Discussion
LuLu(non-developer)LuLu(non-developer) 

0% Code Coverage on Trigger

Hi All - I was so excited I was able to create this very "simple" trigger (so new to this) and when I went to deploy it to Prod I received a 0% Code Coverage error. Could someone please help me understand this code coverage madness and what I actually need to do? Is it an Apex Class? I'm so lost...any help is much appreciated, my trigger below for reference.

trigger AttachmentCount on Attachment (after insert)
{

List<lead> co = [select id, Attachment_Added__c from lead where id =:
Trigger.New[0].ParentId];
if(co.size()>0)
{
co[0].Attachment_Added__c = True;
update co;
}
}
Best Answer chosen by LuLu(non-developer)
Arvind KumarArvind Kumar
Hi Lulu,

For deploy any trigger in production you have to write test class. Test class will give the code coverage to the trigger.

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 Document)

- Execute a method/methods

Please try below code.
@isTest
public class TestLead
{
    Static testmethod void insertRecord()
   {
               Lead LdObj = new Lead();
               LdObjName = 'Test';
               LdObj.Company = 'Test Company';
               LdObj.Status = 'Open - Not Contacted'
               
               insert LdObj;

               LdObj.Attachment_added__c = True;
               update LdObj;
   }

}



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.

If it solves your problem then mark as a best anwer.

Thanks,

Arvind Kumar

All Answers

KalyanGKalyanG
@LuLu, You have to create a Test Class for that trigger. Test Class will call your trigger and the lines executred by your test class is your code coverage. check: https://developer.salesforce.com/page/An_Introduction_to_Apex_Code_Test_Methods and https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_methods_system_test.htm
Arvind KumarArvind Kumar
Hi Lulu,

For deploy any trigger in production you have to write test class. Test class will give the code coverage to the trigger.

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 Document)

- Execute a method/methods

Please try below code.
@isTest
public class TestLead
{
    Static testmethod void insertRecord()
   {
               Lead LdObj = new Lead();
               LdObjName = 'Test';
               LdObj.Company = 'Test Company';
               LdObj.Status = 'Open - Not Contacted'
               
               insert LdObj;

               LdObj.Attachment_added__c = True;
               update LdObj;
   }

}



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.

If it solves your problem then mark as a best anwer.

Thanks,

Arvind Kumar

This was selected as the best answer
Arvind KumarArvind Kumar
Hi Lulu,

Use LdObj.LastName = 'Test'; instead of LdObjName = 'Test';

It would be helpful for you.

Thanks,
Arvind Kumar
LuLu(non-developer)LuLu(non-developer)
@KalyanG - Thank you for the information!
LuLu(non-developer)LuLu(non-developer)
@Avind Kumar - Thank you so, so, so very much for the information. This is extremely helpful and I am super humble you took the time to put all of that together - HUGE thank you!
Arvind KumarArvind Kumar
Welcome Lu Lu

I am very happy for helping you 
LuLu(non-developer)LuLu(non-developer)
I got very close to making this work with your help @Arvind Kumar. Unfortunately, I am getting this "MISSING_ARGUMENT, Id not specified in an update call: []" I did a bit of research on this errpr message but it all left me even more confused. Below is my test class & trigger for reference, again any help is much appreciated.

Test Class:  (had to edit line 11 from "insert LdObj;" to jst semicolon since it was giving me an error)

User-added image

Trigger:
trigger AttachmentCount on Attachment (after insert)
{

List<lead> co = [select id, Attachment_Added__c from lead where id =:
Trigger.New[0].ParentId];
if(co.size()>0)
{
co[0].Attachment_Added__c = True;
update co;
}
}
Arvind KumarArvind Kumar
Hi Lulu,

You have to write insert ldobj at line 11 after that your test class will run. 

Use steps which I have mentioned below.
In line 9 write as ldobj.status = 'open - not contacted';
In line 11 write as insert ldobj;


Use it. I will work for you.


Thanks 
LuLu(non-developer)LuLu(non-developer)
Arvind - When I do that I get a Compile Error: unexpected token: "insert" at line 11 column 15. But when I just leave it with smicolon it let's me save

User-added image
LuLu(non-developer)LuLu(non-developer)
Totally did not see I was missing a semicolon on line 9...how do you guys do this development madness for a living?!? Hats off to all developers out there...my goodness. THANK YOU again Arvind!
Arvind KumarArvind Kumar
Hi Lulu,

Has been resolved your problem or not?

Thanks,
Arvind Kumar
LuLu(non-developer)LuLu(non-developer)
Well not sure. I am still not able to successfully push the trigger to prod. I'm still getting a code coverage error. I added the apex class, trigger and new field to the change set and I am still getting this error. I'm so lost.
User-added image
Arvind KumarArvind Kumar

Hi Lulu,

It is code coverage error.You have to your test class after that you can deploy the trigger in production.

Please follow the below steps for run Test class.
1.) Go on your Test class Attachment Count.
2.) Click on Run Test button.
3.) While running process is complete.
4.) Refresh your trigger page.
5.) You will get code coverage on Trigger page.
6.) Now deploy your change set from sandbox to production.


If you will get any error please let me know.

Thanks

LuLu(non-developer)LuLu(non-developer)
Hi Arvind - I followed the steps above and I am still getting 0% code coverage on the trigger itself. All the test runs have been successful but the tigger code coverage has not changed, please see below. Should I still try to deply the change set?
User-added image
Arvind KumarArvind Kumar
I will give you another solution please give 1 hour for this.

 
Arvind KumarArvind Kumar
I have made new test class for you.

Please use it & follow the above-mentioned steps. It class will give you 100% code coverage.

You can deploy your trigger in Producation.
 
Test class:
@isTest
public class TestAttachmentCount
{
    Static testmethod void insertRecord()
   {
               Lead LdObj = new Lead();
               LdObj.LastName = 'Test';
               LdObj.Company = 'Test Company';
               LdObj.Status = 'Open - Not Contacted';
               
               insert LdObj;

           
               Attachment attachment = new Attachment(Name='An attachment',body=blob.valueof('b'),parentId=LdObj.Id);
             
           try{
               insert attachment;

               LdObj.Attachment_added__c = True;
               update LdObj;
               
               }
               
               catch(exception e)
               {}

   }

}

If you have any query please mail me.

Thanks,
Arvind Kumar
LuLu(non-developer)LuLu(non-developer)

Arvind - Your latest test class worked in conjuction with the steps below I found on LinkedIn. THANK YOU - THANK YOU - THANK YOU!

1) Open Developer Console.
2) Click the panel "Query Editor" Tab at the bottom of the screen
3) Write the following Query in Query Editor.
SELECT Id, NumLinesUncovered FROM ApexCodeCoverageAggregate
4) Check the checkbox "Use Tooling API" at the bottom of the screen.
5) Click "Execute".
6) Select all rows and delete them from "Query Results".
7) Make sure there are no records of ApexCodeCoverageAggregate
8) Clear all Test history (Setup | Developer | Apex Test Execution -> View Test History -> Clear Test Results)
9) Compile all classes
10) Perform "Run All test".

Arvind KumarArvind Kumar
Welcome Lulu,

It is good steps.
Brian Roberts 2Brian Roberts 2
Guys,not too savi with this could you help me with mine please
trigger FX_Ticket_InAccrual on FX5__Ticket__c (after insert, after update) {
  Boolean stopTrigger = false;
  FX5__Status__c TicketInAccrualStatus = null;
  Map<Id,List<FX5__Ticket_Item__c>> TicketInAccrualTktItemMap = new Map<Id,List<FX5__Ticket_Item__c>>();

  // Sequences the Ticket Items when a Ticket has been moved to the "Ticket_in_Accrual" status
  try {   
    TicketInAccrualStatus = [select Id,Name,Status_Developer_Name__c from FX5__Status__c where FX5__SObject__c='Ticket__c' and Status_Developer_Name__c='Ticket_in_Accrual' LIMIT 1];
  }
  catch (System.QueryException e) {
    // This Stop Trigger catch was added so that ticket unit tests won't fail when no statuses are inserted as part of the test.
    stopTrigger = true;
  }

  if (!stopTrigger) {  
    // find the Ticket in Accrual tickets that need their ticket items sequenced.
    for(FX5__Ticket__c t : trigger.new) {
      if (TicketInAccrualStatus != null && t.FX5__Status__c != null && t.FX5__Status__c == TicketInAccrualStatus.Id) {
        TicketInAccrualTktItemMap.put(t.Id,new List<FX5__Ticket_Item__c>());
      }
    }
    string sortText = FX5__FX_Settings__c.getOrgDefaults().TicketItemSort__c;
    if(sortText == null) sortText = 'FX5__Ticket__c,Record_Type_Sort_Index__c,Name';
        
    if (TicketInAccrualTktItemMap.size() > 0) {
      // finish out the map of Ticket Item Sets for sequencing
      /*List<FX5__Ticket_Item__c> tktItems = [
        select 
          Id,FX5__Ticket__c,FX5__Sequence_Number__c,
          EXPRO_SAP_Item_Number__c,
          Record_Type_Sort_Index__c
        from 
          FX5__Ticket_Item__c 
        where 
          FX5__Ticket__c in :TicketInAccrualTktItemMap.keySet()
        order by 
          FX5__Ticket__c,Record_Type_Sort_Index__c,Name];
      */
      set<id> TicketInAccrualTktItemSet = TicketInAccrualTktItemMap.keySet();
      string query = 'select ';
      query += 'Id,FX5__Ticket__c,FX5__Sequence_Number__c,EXPRO_SAP_Item_Number__c,Record_Type_Sort_Index__c ';
      query += 'from FX5__Ticket_Item__c ';
      query += 'where FX5__Ticket__c in :TicketInAccrualTktItemSet ';
      query += 'order by ' + sortText;
      
      List<FX5__Ticket_Item__c> tktItems = database.query(query);
      
      if (tktItems != null) {
        for(FX5__Ticket_Item__c tktItem : tktItems) {
          TicketInAccrualTktItemMap.get(tktItem.FX5__Ticket__c).add(tktItem);
        }
        
        // Sequence the Ticket Items in the list
        List<FX5__Ticket_Item__c> tktItemsToUpdate = new List<FX5__Ticket_Item__c>();
        for(Id tktId : TicketInAccrualTktItemMap.keySet()) {
          Integer seq = 10;
          for(FX5__Ticket_Item__c tktItem : TicketInAccrualTktItemMap.get(tktId)) {
            tktItem.EXPRO_SAP_Item_Number__c = seq;
            seq = seq + 10;
            tktItemsToUpdate.add(tktItem);  
          }
        }
        
        update tktItemsToUpdate;
        
      }
    }
  }
}