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
sreekanth cheerasreekanth cheera 

write a test class for this program?

public class Requirement1 {

    public static void beforeinsert(list<Contact> con){
        
        for(Contact c:con){
            if(string.isblank(c.MobilePhone) && c.Phone!=null && c.Type__c=='prospect'){
                c.MobilePhone=c.Phone;
                
            }
            else{
                if(string.isBlank(c.phone) && c.MobilePhone!=null){
                    c.phone=null;
                }
            
             
            }
        }
    }
    public static void beforeupdate(list<Contact> con1){
     
        for(contact cn:con1){
            if(cn.Office_Phone__c!=null && string.isBlank(cn.Phone)&& string.isBlank(cn.MobilePhone)){
                cn.MobilePhone=cn.Office_Phone__c;
              
            }
        }
     
    }
}
Raj VakatiRaj Vakati
try this
  
@IsTest
public class ContactTrigger_Test {

    

    public testMethod static void contactInsertionFails() {
        Account acct = new Account(name='test account');
        insert acct;

        // Set some  other required fields 
        Contact c = new Contact(AccountId=acct.Id, lastname='testing', firstname='apex',Type__c='prospect',Phone='123123');
        insert c;
		
		Contact c1 = new Contact(AccountId=acct.Id, lastname='testing', firstname='apex',Type__c='prospect',MobilePhone='123123');
        insert c1;

		
		Contact c2 = new Contact(AccountId=acct.Id, lastname='testing', firstname='apex',Type__c='prospect');
        insert c2;
		
		c2.Office_Phone__c='123123';
		update c2 ;
        
        // Set some  other required fields 
		
		
    }

}

 
Amit Chaudhary 8Amit Chaudhary 8
I will recommend you to start using trailhead to learn about test classes
1) https://trailhead.salesforce.com/modules/apex_testing

Pleasse check below post sample test class
1) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html

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

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 Account and Contact )
- Instantiate the Trigger- Insert and Update
- Verify the behaviour with asserts. 
@IsTest
public class Requirement1Test {

    public testMethod static void contactInsertionFails() 
	{
		Account acct = new Account(name='test account');
		insert acct;

		Contact c = new Contact(AccountId=acct.Id, lastname='testing', firstname='apex',Type__c='prospect',Phone='123123');
		insert c;

		c.Office_Phone__c='123123';
		update c ;
		
		List<contact> lstCont = [Select id ,MobilePhone from Contact where id =:c.id ];
		System.assert(lstCont != null);
		System.assert(lstCont[0].Office_Phone__c == '123123' );
    }

}
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

 
Akshay_DhimanAkshay_Dhiman
Hi Sreekanth Cheera,

Try this code.
  
@isTest
public class Requirement1_Test {
      @isTest
    public static void contactTest(){
        Account acc = new Account();
        acc.Name='Dummy Account';
        insert acc;
        
        Contact cont1 = new Contact();
        cont1.AccountId=acc.id;
        cont1.lastname='Test Contact';
        cont1.Type__c='Prospect';
        cont1.Phone='123456';
        insert cont1;     
     
        
        Contact cont2 = new Contact();
        cont2.AccountId=acc.id;
        cont2.lastname='Test Contact2';
        cont2.MobilePhone='12345';
        insert cont2;
        
        Contact cont3 = new Contact();
        cont3.AccountId=acc.id;
        cont3.lastname='Test Contact2';
        insert cont3;
        
        cont3.Office_Phone__c='123456';
        update cont3;
        
        contact c1=[select id, lastName,MobilePhone from contact where id=:cont1.id];
        System.assertEquals(c1.MobilePhone,'123456');
        
        contact c3=[select id, lastName,MobilePhone from contact where id=:cont3.id];
        system.assertEquals(c3.MobilePhone, '123456');
         
    }
}


Hope it will help you.
Mark this as best answer if you find it helpful.

Thanks
Akshay