+ Start a Discussion
Rom_Rom_ 

Code Coverage for simple update Trigger

Not a developer, but somehow managed to write a working trigger in sandbox. Trying to deploy to production, says no code coverage. Can someone please help. What do I need to do to successfuly deploy to prodution. 
Trigger:
trigger updateRelatedLead on Task (after insert,after update) {

 List<Id> LeadIds = new List<Id>();
 List<Lead> LeadList = new List<Lead>();

  for(Task t :trigger.new)
    {
	if(t.whoId!=null)
	{
        Schema.SObjectType tType= t.whoId.getSObjectType();
        if(tType == Lead.Schema.SObjectType)
        {
            LeadIds.add(t.WhoId);
        }
    }
	}
	//Querying the related Lead based on whoId on Task
	Map<Id,Lead> LeadMap =  new Map<Id,Lead>([select id,Latest_Follow_Up__c,Task_Subject__c,Task_Comment__c from Lead where id in:LeadIds]);
	
	for(Task t :Trigger.new)

		for(Lead l : LeadMap.Values())
		{
			l.Latest_Follow_Up__c = t.Due_Date_Time__c;
            l.Task_Subject__c = t.Subject;
            l.Task_Comment__c = t.ISOOffice__Comment__c;
			LeadList.add(l);
		}
	// updating the Lead
    if(LeadList.isEmpty() == false) update LeadList;
	}

 
Best Answer chosen by Rom_
Amit Chaudhary 8Amit Chaudhary 8
Please check below post. I hope that will help you :-
1) http://amitsalesforce.blogspot.com/search/label/Test%20Class
2) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html
@isTest
private class updateRelatedLeadTest 
{
    public static testMethod void testTrigger()
	{
		Lead l = new Lead();
		l.FirstName = 'CRM Testing First';
		l.LastName = 'CRM Testing Last';
		l.Company = 'CRM Testing INCtest';
		l.description = 'Test descr';
		l.city = 'test';
		l.street = 'test';
		l.state = 'CA';
		l.country = 'United States';
		l.status = 'Qualified';
		l.email = 'test@testcrm.com';
		l.website = 'www.testcrm.com';
		insert l;

	
        Task t = new Task();
        t.OwnerId = UserInfo.getUserId();
        t.Subject='No Subject';
        t.Status='Not Started';
        t.Priority='Normal';
		t.whoId = l.id ;
		//t.Due_Date_Time__c = System.today();
		//t.ISOOffice__Comment__c = 'demo comment';
        insert t;       
    }
}




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


 

All Answers

Swayam@SalesforceGuySwayam@SalesforceGuy
Hi,

Its very Simple :

Just Create a  Test Class to create a Task 
 
@isTest
private class testMyTaskTrigger {
  
    public static testMethod void testTTrigger(){
      
      
        
        Task t = new Task();
        t.OwnerId = UserInfo.getUserId();
        t.Subject='No Subject';
        t.Status='Not Started';
        t.Priority='Normal';
       

        insert t;       
    }


}

Hope this help

--
Thanks,
Swayam
Rom_Rom_
Thanks for the help Swayam. Can I include that in the trigger or does it need to be in it's own class? Also, when Deploying in production, will it allow me to only test this test class eventhough it's not deployed yet? (I have old development that is erroring on default and local validations)
Sumit Kumar Singh 9Sumit Kumar Singh 9
Hi Rom,
First of all, your code must include proper exception handling and null check. What id LeadMap is null??
 It should be a seperate class. You need to include all the required fields while inserting the Task Record, otherwise it would get failed.
I would also suggest you to include Assert Statements in the test class. Test classes are intendent to test not just to cover the code. 

@isTest
private class UpdateRelatedLead_Test { 
    static testMethod void testUpdateRelatedLead() {
            Task t = new Task();
            t.OwnerId = UserInfo.getUserId();
            t.Subject='No Subject';
            t.Status='Not Started';
            t.Priority='Normal';
            t.customField__c = 'my custom value'; (Assuming customField__c  on Task is a manadatory field.)
            (You should include all the manadotory fields whether it is custom or Standard.)
            insert t;    
            
            //As your trigger is being fired on Update too, ou should update the record too.  
            // System.assertEquals(t.Status, 'Not started');
            t.Status='Started';
            update t;
           // Verify that record got updated
           // System.assertEquals(t.Status, 'Started');
     }
}

Thanks,
Sumit Kumar Singh

 
Amit Chaudhary 8Amit Chaudhary 8
Please check below post. I hope that will help you :-
1) http://amitsalesforce.blogspot.com/search/label/Test%20Class
2) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html
@isTest
private class updateRelatedLeadTest 
{
    public static testMethod void testTrigger()
	{
		Lead l = new Lead();
		l.FirstName = 'CRM Testing First';
		l.LastName = 'CRM Testing Last';
		l.Company = 'CRM Testing INCtest';
		l.description = 'Test descr';
		l.city = 'test';
		l.street = 'test';
		l.state = 'CA';
		l.country = 'United States';
		l.status = 'Qualified';
		l.email = 'test@testcrm.com';
		l.website = 'www.testcrm.com';
		insert l;

	
        Task t = new Task();
        t.OwnerId = UserInfo.getUserId();
        t.Subject='No Subject';
        t.Status='Not Started';
        t.Priority='Normal';
		t.whoId = l.id ;
		//t.Due_Date_Time__c = System.today();
		//t.ISOOffice__Comment__c = 'demo comment';
        insert t;       
    }
}




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


 
This was selected as the best answer