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
Holly HavelkaHolly Havelka 

Help - My Test Class Gives Me ZERO Code Coverage

Hello all - can someone help me with a very basic trigger and test class?

My Trigger:

trigger LeaveBeforeDelete on VBA_CC_Tracking_Leave_Manager__c (before delete)
{
  for  (VBA_CC_Tracking_Leave_Manager__c q: trigger.old)
  
       if (q.Status_of_Request__c != 'Pending')
               
           {
           
           q.adderror('This record cannot be deleted due to the status being other than "Pending". Thank you');
           
           } 
}

My Test Class:

@IsTest
public class LeaveBeforeDeleteTest {

    static void testLeaveBeforeDelete() {
       
        User u = new User();
        u.FirstName = 'Mr';
        u.LastName = 'Tester';
        u.Email = 'mr.tester@va.gov';
        u.Alias = 'mtest';
        u.Username = 'mr.tester@va.gov';
        u.ProfileID = '00et0000000QGuG';
        
        u.TimezoneSidKey = 'America/Denver';
        u.LocaleSidKey = 'en_US';
        u.EmailEncodingKey = 'UTF-8';
        u.LanguageLocaleKey = 'en_US';
        
        insert u;
        
        system.runAs(u){
    
        VBA_CCTracking_Agent_Production_Data__c a = new VBA_CCTracking_Agent_Production_Data__c();
        a.Name = 'MrTester-2016-05-13';
        a.VBA_CC_Date_of_Data__c = date.newInstance(2016, 5, 13);
        
        insert a;                                        
                       
        VBA_CC_Tracking_Leave_Manager__c b = new VBA_CC_Tracking_Leave_Manager__c();        
        b.Agent_Name_Date__c = a.Id;
        b.Status_of_Request__c = 'Approved';
        
               
        insert b;
           
        try
           {
               Delete a;
               System.assert(true);
            }
           catch(Exception e) 
           {
               system.assertEquals('This record cannot be deleted due to the status being other than "Pending". Thank you', e.getMessage());
            }      
        
        }
                        
        
    }

}
Best Answer chosen by Holly Havelka
Rohit K SethiRohit K Sethi

Hi ,

You are writing trigger on "VBA_CC_Tracking_Leave_Manager__c" and in test class you delete the object " VBA_CCTracking_Agent_Production_Data__c " so you need to delete the object "B" which is instance of object VBA_CC_Tracking_Leave_Manager__c.

You need to write this line 
                       delete b;
                    
Thanks.
 

All Answers

Rohit K SethiRohit K Sethi

Hi ,

You are writing trigger on "VBA_CC_Tracking_Leave_Manager__c" and in test class you delete the object " VBA_CCTracking_Agent_Production_Data__c " so you need to delete the object "B" which is instance of object VBA_CC_Tracking_Leave_Manager__c.

You need to write this line 
                       delete b;
                    
Thanks.
 

This was selected as the best answer
Holly HavelkaHolly Havelka
Rohit K Sethi, thank you!  I switched them and am now getting 100% code coverage, BUT now the test is failing.  Any thoughts on this?
Holly HavelkaHolly Havelka
I finally got the test class to pass.  

I switched out: 

 try
           {
               Delete a;
               System.assert(true);
            }
           catch(Exception e) 
           {
               system.assertEquals('This record cannot be deleted due to the status being other than "Pending". Thank you', e.getMessage());


FOR:

try
           {
               Delete b;               
            }
           catch(Exception ex) {}      

Thank you again for the help!
        
Amit Chaudhary 8Amit Chaudhary 8
I hope your assert was failing. Please try below test class
@IsTest
public class LeaveBeforeDeleteTest 
{
    static void testLeaveBeforeDelete() 
	{
        VBA_CCTracking_Agent_Production_Data__c a = new VBA_CCTracking_Agent_Production_Data__c();
        a.Name = 'MrTester-2016-05-13';
        a.VBA_CC_Date_of_Data__c = date.newInstance(2016, 5, 13);
        insert a;                                        
                       
        VBA_CC_Tracking_Leave_Manager__c b = new VBA_CC_Tracking_Leave_Manager__c();        
        b.Agent_Name_Date__c = a.Id;
        b.Status_of_Request__c = 'Approved';
        insert b;
           
		try
		{
			Delete b;
		}
		catch(Exception e) 
		{
			Boolean expectedExceptionThrown =  e.getMessage().contains('This record cannot be deleted due to the status being other than "Pending". Thank you')  ? true : false;
			System.AssertEquals(expectedExceptionThrown, true);
		}
    }

}

Let us know if this will help you

Thanks
Amit Chaudhary
Holly HavelkaHolly Havelka
Amit Chaudhary 8, with your test class you do not have a test user?  Why is that?  
 
Amit Chaudhary 8Amit Chaudhary 8
Hi Holly Havelka,

Yes no need to create a user every time in Test class. We Should create the User only if we added the validation in trigger for profile or User level other wise no need to create new user in test class.

Please test above Test Class and let us know if your code is working fine without any failure .
 
Please check below post to learn about test classes.
1) http://amitsalesforce.blogspot.in/search/label/Test%20Class
2) http://amitsalesforce.blogspot.in/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

Thanks
Amit Chaudhary