+ Start a Discussion
Saad Ahmad 27Saad Ahmad 27 

Can someone explain to me how to write a text class for the following apex trigger

Hi All,

I'm new to apex coding and wrote my first trigger. I'm not sure how to go about writing a test class. I read up a couple of different forums but haven't been able to figure it out.

trigger OpenRepairs on Repair_History__c (before insert, before update) {
    for (Repair_History__c R: Trigger.new) {
        if (R.Status__c == 'Closed') {
            R.OpenRepair__c = null;
        } else if (R.Status__c == 'Closed - Traded In') {
            R.OpenRepair__c = null;
        } else if (R.Status__c == 'Closed - Return Unrepair') {
            R.OpenRepair__c = null;
        } else if (R.Account__c != null) {
            R.OpenRepair__c = R.Account__c;
        }
    }
}
Best Answer chosen by Saad Ahmad 27
Amit Chaudhary 8Amit Chaudhary 8
Hi
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 Repair_History__c )
- Instantiate the Trigger- by creating Repair_History__c  record
- Execute a method/methods
- Verify the behaviour with asserts.

Please try below code in your code
@isTest
private class OpenRepairsTest 
{
	
	static testMethod void testMethod1()
	{
		Repair_History__c repObj = new Repair_History__c();
		repObj.Name = 'j0' ;
		repObj.Status__c = 'Closed';
		insert repObj;
		
		repObj.Status__c = 'Closed - Traded In';
		update repObj;

		repObj.Status__c = 'Closed - Traded In';
		update repObj;

		repObj.Status__c = 'Closed - Return Unrepair';
		update repObj;

		repObj.Status__c = 'Closed - Traded In';
		update repObj;
		
	}
	
	
}



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

SalesFORCE_enFORCErSalesFORCE_enFORCEr
You just need to create a Repair_History__c record in your test class and set the status as these different values so that everytime you update the status in test class, it covers each if condition.

Also, just curious Why did not you create a process builder to achieve this functionality?
Grant Ongstad 3Grant Ongstad 3
Hey Saad, I would refer to the trailhead. This helped me understand it: https://trailhead.salesforce.com/en/modules/apex_testing/units/apex_testing_triggers


 
Nithesh NNithesh N
Hi Saad, 

Try this code.... Add the necessary required values of Repair History object when initializing the object.
 
@isTest
private class openRepairsTest {
	
	@isTest static void test_method_Closed() {
	Repair_History__c r = new Repair_History__c(Name = 'j0' ,Status__c = 'Closed');
    insert r; // Triggers Before Insert
    r.Name = 'Test Closed';
    update r; // Triggers Before update    
	}
	
	@isTest static void test_method_TradedIn() {
	Repair_History__c r = new Repair_History__c(Name = 'j1' ,Status__c = 'Closed - Traded In');
    insert r; // Triggers Before Insert
    r.Name = 'Test Traded In';
    update r; // Triggers Before update    
	}
  
  @isTest static void test_method_Unrepair() {
	Repair_History__c r = new Repair_History__c(Name = 'j2' ,Status__c = 'Closed - Return Unrepair');
    insert r; // Triggers Before Insert
    r.Name = 'Test Return Unrepair';
    update r; // Triggers Before update   
	}
  
  @isTest static void test_method_other() {
	Repair_History__c r = new Repair_History__c(Name = 'j3' ,Status__c = 'Open'); //Another picklist value  other than the three listed above
    insert r; // Triggers Before Insert
    r.Name = 'Test Other';
    update r; // Triggers Before update
	}
	
}
Let me know if it works.

Best.
Nithesh
 
Amit Chaudhary 8Amit Chaudhary 8
Hi
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 Repair_History__c )
- Instantiate the Trigger- by creating Repair_History__c  record
- Execute a method/methods
- Verify the behaviour with asserts.

Please try below code in your code
@isTest
private class OpenRepairsTest 
{
	
	static testMethod void testMethod1()
	{
		Repair_History__c repObj = new Repair_History__c();
		repObj.Name = 'j0' ;
		repObj.Status__c = 'Closed';
		insert repObj;
		
		repObj.Status__c = 'Closed - Traded In';
		update repObj;

		repObj.Status__c = 'Closed - Traded In';
		update repObj;

		repObj.Status__c = 'Closed - Return Unrepair';
		update repObj;

		repObj.Status__c = 'Closed - Traded In';
		update repObj;
		
	}
	
	
}



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
Saad Ahmad 27Saad Ahmad 27
Thanks everyone for responding and helping me with this request. I was able to implement this using process builder. However, I will definitely try the code posted by Nithesh and Amit in oder to learn more and will post my results.