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
subodh chaturvedi 17subodh chaturvedi 17 

i want to write a test class for a trigger if the child object have records & i am trying to delete a parent object so it should throw an Error can not delete

My trigger:-
trigger accountDelete on Account (before Delete) {
    List<Account> accs=[select id,(select id from contacts ) from Account where id in:Trigger.old];
    for(Account a:accs){
        if(a.contacts.size()>0)
            a.addError('Account cannot be deleted where it has contacts');
    }
}
Best Answer chosen by subodh chaturvedi 17
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

Please check below for sample test classes
1) 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 controller to access (in this case it looks like Account records)
- Instantiate the Trigger - Delete Account record
- Execute a method/methods :- Delete account record
- Verify the behaviour with asserts.

The fact that the class is used as a controller is fairly immaterial.


Sample text class to start
@isTest
public class accountDeleteTest 
{
	static testMethod void myUnitTest() 
	{
		Account acc = new Account();
		acc.name = 'test';
		insert acc; 
		
		Contact Cont = new contact();
		Cont.FirstName = 'test';
		Cont.lastName = 'test';
		Cont.AccountId = acc.Id;
		insert Cont ;

		try{
			delete acc;
		}
		catch(Exception ee){
			Boolean expectedExceptionThrown =  e.getMessage().contains('Account cannot be deleted where it has contacts')) ? true : false;
			System.AssertEquals(expectedExceptionThrown, true);
		}
	}
}




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

sfdcMonkey.comsfdcMonkey.com
Hi Subodh,
use this test class for 100% code coverage 
 
@isTest

public class testSample {
static testMethod void validateHelloWorld() {
   account acc = new account();
    acc.name = 'test';
    insert acc; 
   contact cc = new contact();
    cc.lastName = 'test';
    cc.AccountId = acc.Id;
    insert cc ;
    
    delete acc;
       
}
}

i hope it helps you.
   Let me inform if it helps you and kindly mark it best answer if it helps you so it make proper solution for others
thanks 
sfdcmonkey.com  (http://sfdcmonkey.com )
 
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

Please check below for sample test classes
1) 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 controller to access (in this case it looks like Account records)
- Instantiate the Trigger - Delete Account record
- Execute a method/methods :- Delete account record
- Verify the behaviour with asserts.

The fact that the class is used as a controller is fairly immaterial.


Sample text class to start
@isTest
public class accountDeleteTest 
{
	static testMethod void myUnitTest() 
	{
		Account acc = new Account();
		acc.name = 'test';
		insert acc; 
		
		Contact Cont = new contact();
		Cont.FirstName = 'test';
		Cont.lastName = 'test';
		Cont.AccountId = acc.Id;
		insert Cont ;

		try{
			delete acc;
		}
		catch(Exception ee){
			Boolean expectedExceptionThrown =  e.getMessage().contains('Account cannot be deleted where it has contacts')) ? true : false;
			System.AssertEquals(expectedExceptionThrown, true);
		}
	}
}




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
AchtungAchtung
I have a Trigger that works almost similar with it and trying to create a test class for before delete. 
Trigger SAJobsDeletion on Support_Contract__c (before delete) {
    try{    
         
        for(Support_Contract__c sa : Trigger.old)
        {          
            List <Job__c> j = [SELECT Id, Service_Agreement__c FROM Job__c WHEREService_Agreement__c =: sa.Id];
            if(j.size() > 0)
            {             
                sa.adderror('Service Agreement is currently associated with a Job and cannot be deleted.');
            }
        } 
    } Catch(Exception ex){  }
}

And here's my test class that returns 0% coverage:
@isTest
public class SAJobsDeletion_TestClass {
     
    static testMethod void CheckServiceAgreement(){  
        Test.startTest();
         
        Support_Contract__c a = new Support_Contract__c();
        a.Client__c = '0035D0000067lJrQAI';
        a.Funding_Type__c = 'Cash';
        a.Funding_Management__c = 'Participant';
        a.Start_Date__c = Date.newInstance(2018, 03, 01);
        a.End_Date__c = Date.newInstance(2019, 03, 01);
        insert a; 
         
        Job__c j = new Job__c();
        j.Service_Agreement__c = a.Id;
        j.Contact__c = '0035D0000067lJrQAI';
        j.Region__c = 'Australia';
        j.Duration__c = 60;
        insert j;  
         
        try{
            delete a;           
        }Catch (DMLException e){
            System.assert(e.getMessage().contains('Service Agreement cannot be deleted.'), 'Service Agreement cannot be deleted.');
        }
        Test.stopTest();       
    }
}

Can anyone advise me how to revise my test class to reach the required code coverage? Thanks.