function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Web Team 9Web Team 9 

Test Class to be able to deploy Update/Insert Triggers

Hello, I'm looking for assistance writing a test class so that I can deploy 2 triggers to my production environment.  The issue is, I still don't fully understand what the test class is, what it needs to do, and how to write it.

I have 2 triggers, which are before insert/update, both are very similar updating a lookup field on a custom object (Animal__c) from the Contact object. 

Any help writing a test class, with perhaps an explanation as to what it does would be greatly appreciated.

One of my Triggers: 
trigger setFosterLead on Animal__c (before insert, before update)
{
    Map<Id,Id> cases = new Map<Id,Id>();

    List<Contact> listGL = new List<Contact>();
    Set<Id> caseIds = new Set<Id>();
    for (Animal__c a : Trigger.new)
    {
        caseIds.add(a.Foster__c);
    }
    system.debug(caseIds+'@@'+caseIds.size());
    listGL = [Select Id, Foster_Team_Lead__c from Contact where Id In :caseIds];
    system.debug('@@@'+listGL);
    for(Contact objCase: listGL)
    {
            if(!cases.containsKey(objCase.Id)  && objCase.Foster_Team_Lead__c != null)
            cases.put(objCase.Id,objCase.Foster_Team_Lead__c);
    }
    for (Animal__c a : Trigger.new)
    {
            if(cases.containsKey(a.Foster__c))
            a.Foster_Team_Lead2__c = cases.get(a.Foster__c);
    }
}

 
Best Answer chosen by Web Team 9
Mahesh DMahesh D
Hi 

Please find some of the useful information about the Test Class:

Please check below post for test classes. I hope that will help you
1) http://amitsalesforce.blogspot.com/search/label/Test%20Class (http://amitsalesforce.blogspot.com/search/label/Test%20Class" target="_blank)
2) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html (http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html" target="_blank)
3) https://developer.salesforce.com/page/An_Introduction_to_Apex_Code_Test_Methods


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 .


Also I am writing a Test Class for your trigger:
  
@isTest
public class TestSetFosterLead {
	@isTest
	public static void testOne() {
		Account acc = new Account();
        acc.Name = 'Test Acc';
        acc.AccountNumber = '9876';               
        insert acc;
		
		Contact con = new Contact();
        con.AccountId = acc.Id;
        con.FirstName = 'test first name';
        con.LastName = 'test last name';
        con.Email = 'test@test.com';
		con.Foster_Team_Lead__c = 'Test Lead'; // If it is a Text field.
        insert con;
		
		Animal__c ani = new Animal__c();
		ani.Foster__c = con.Id;
		insert ani;
		
		Animal__c aniNew = [Select Id, Foster_Team_Lead2__c from Animal__c where Id =: ani.Id LIMIT 1];
		System.assertEquals(con.Foster_Team_Lead__c, aniNew.Foster_Team_Lead2__c);
	}
}


Please do let me know if it helps you.

Regards,
Mahesh

All Answers

JeffreyStevensJeffreyStevens
A test class is a class (not a trigger), that is called whenever you try to deploy any code (other classes, triggers, etc.).  It's called automatically - or you can specify a specific test class(es) to cal. 

For each trigger that you are trying to deploy - you have to have AT-LEAST one line in the trigger executed by a test class.  AND you have to have AT-LEAST 75% of all custom code lines covered. If I read your trigger correctly - you have 8 executable lines - and the trigger is the only custom code you have deployed - then you'll need to execute at-least 6 of those 8 lines in your test class. The test class has the @istest directive before the class definition. The test class then should have a static method of the type testmethod.

So, you have to write another class that creates a Animal__c record. And then updates it.    And, if you want line #16 to get covered in your test classes - then you'll need to have a Contact record, and put that Contact id in the Foster__c field when you're building your Animal__c record. AND, if you add a contact - you should probably add an Account - but probably not required (don't remember for sure.  Soooo, when your test class writes the Animal__c record - the setFosterLead trigger will get called.  

In order to test this while still in sandbox - use developer console - Do test - New test run - then select your test class and run it.  Then you'll be able to see what lines of your trigger are being covered.  If you're using eclipse - you can also run the test class from there also. 
Mahesh DMahesh D
Hi 

Please find some of the useful information about the Test Class:

Please check below post for test classes. I hope that will help you
1) http://amitsalesforce.blogspot.com/search/label/Test%20Class (http://amitsalesforce.blogspot.com/search/label/Test%20Class" target="_blank)
2) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html (http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html" target="_blank)
3) https://developer.salesforce.com/page/An_Introduction_to_Apex_Code_Test_Methods


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 .


Also I am writing a Test Class for your trigger:
  
@isTest
public class TestSetFosterLead {
	@isTest
	public static void testOne() {
		Account acc = new Account();
        acc.Name = 'Test Acc';
        acc.AccountNumber = '9876';               
        insert acc;
		
		Contact con = new Contact();
        con.AccountId = acc.Id;
        con.FirstName = 'test first name';
        con.LastName = 'test last name';
        con.Email = 'test@test.com';
		con.Foster_Team_Lead__c = 'Test Lead'; // If it is a Text field.
        insert con;
		
		Animal__c ani = new Animal__c();
		ani.Foster__c = con.Id;
		insert ani;
		
		Animal__c aniNew = [Select Id, Foster_Team_Lead2__c from Animal__c where Id =: ani.Id LIMIT 1];
		System.assertEquals(con.Foster_Team_Lead__c, aniNew.Foster_Team_Lead2__c);
	}
}


Please do let me know if it helps you.

Regards,
Mahesh

This was selected as the best answer
Web Team 9Web Team 9
Thank you so much Mahesh!  This worked like a charm, once I added in some of my additional required fields for contacts and animals.
All the additional information you provided is super useful and I thank you for taking the time to create this for me.