+ Start a Discussion
VempallyVempally 

Can anyone help in writting a test class for the following code...

public with sharing class WrapPractice {

     public List<Wrapper> wrap_lst {get; set;}

    public List<Account> acc_lst {get; set;}
    
    public List<Wrapper> selected_lst {get; set;}


    public PageReference showSelected() {
    
        selected_lst = new List<Wrapper>();
        
        for(Wrapper w: wrap_lst)
            if(w.chk == true)
                selected_lst.add(w);
        system.debug(selected_lst);
        
        String lst_serialize = json.serialize(selected_lst);
        system.debug('serialised string  ' + lst_serialize);
        
        Pagereference pg = page.show_accounts;
        pg.getParameters().put('lst_serialize', lst_serialize);
        return pg;
    }

    

    public WrapPractice(){
    
        acc_lst = new List<Account>();
        
        acc_lst = [select id, name, accountnumber from Account];
        
        system.debug('Account List :'+ acc_lst);
        
        wrap_lst = new List<Wrapper>();
        
        for(Account acc : acc_lst)
         wrap_lst.add(new Wrapper(acc));
         
         system.debug('wraplist'+ wrap_lst);
        
    
    }
    
    Public Class Wrapper{
    
        public Boolean chk {get; set;}
        public Account acc {get; set;}
        
        public Wrapper (Account acc){
        
        this.acc = acc;
        chk = false;
        
        
        }
    
    }


}

VisualForce
 
<apex:page controller="WrapPractice">
<apex:form >
 <apex:pageBlock >
     <apex:pageBlockSection >
     
         <apex:commandButton value="show" action="{!showSelected}"/>
         <apex:pageBlockTable value="{!wrap_lst}" var="w">
             <apex:column >
             
                 <apex:inputCheckbox value="{!w.chk}"/>
             </apex:column>
             
             <apex:column >
             
                 <apex:outputField value="{!w.acc.id}"/>
             </apex:column>
             <apex:column >
             
                 <apex:outputField value="{!w.acc.name}"/>
             </apex:column>
             <apex:column >
             
                 <apex:outputField value="{!w.acc.accountnumber}"/>
             </apex:column>
         
         </apex:pageBlockTable>
     
     <apex:pageBlockTable value="{!selected_lst}" var="slst">
             <apex:column >
             
                 <apex:inputCheckbox value="{!slst.chk}"/>
             </apex:column>
             
             <apex:column >
             
                 <apex:outputField value="{!slst.acc.id}"/>
             </apex:column>
             <apex:column >
             
                 <apex:outputField value="{!slst.acc.name}"/>
             </apex:column>
             <apex:column >
             
                 <apex:outputField value="{!slst.acc.accountnumber}"/>
             </apex:column>
         
         </apex:pageBlockTable>
     </apex:pageBlockSection>
 
 </apex:pageBlock>
 </apex:form>
</apex:page>

 
Best Answer chosen by Vempally
Amit Chaudhary 8Amit Chaudhary 8
Pleae check below post to lead 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 try below test class. I hope that will help you
@isTest 
public class WrapPractice Test 
{
	static testMethod void testMethod1() 
	{
		Account testAccount = new Account();
		testAccount.Name='Test Account' ;
		// add all required field here
		insert testAccount;

		Test.StartTest(); 


		WrapPractice  testAccPlan = new WrapPractice ();

		for(WrapPractice.Wrapper w = testAccPlan.wrap_lst)
		{
			w.chk = true;
		}		
		testAccPlan.showSelected();
		
		Test.StopTest();
	}
}
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

Amit Chaudhary 8Amit Chaudhary 8
Pleae check below post to lead 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 try below test class. I hope that will help you
@isTest 
public class WrapPractice Test 
{
	static testMethod void testMethod1() 
	{
		Account testAccount = new Account();
		testAccount.Name='Test Account' ;
		// add all required field here
		insert testAccount;

		Test.StartTest(); 


		WrapPractice  testAccPlan = new WrapPractice ();

		for(WrapPractice.Wrapper w = testAccPlan.wrap_lst)
		{
			w.chk = true;
		}		
		testAccPlan.showSelected();
		
		Test.StopTest();
	}
}
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
VempallyVempally
Hi Amit
Thanks for your response.

What about code coverage...
Your test class gives a 0% code coverage.

User-added image
VempallyVempally
Hi Amit,

It would be helpful if you make me understand the following,

1. What is the need of inserting an account.

2. Where did we get the value for " testAccPlan.wrap_lst "
Amit Chaudhary 8Amit Chaudhary 8
1. What is the need of inserting an account.
Amit:- See you code line 33 where you are getting all account record.
acc_lst = [select id, name, accountnumber from Account];

2. Where did we get the value for " testAccPlan.wrap_lst "
Amit:- After creating the object of "WrapPractice" class automactly below code will execute and you will get value
public WrapPractice(){
    
        acc_lst = new List<Account>();
        
        acc_lst = [select id, name, accountnumber from Account];
        
        system.debug('Account List :'+ acc_lst);
        
        wrap_lst = new List<Wrapper>();
        
        for(Account acc : acc_lst)
         wrap_lst.add(new Wrapper(acc));
         
         system.debug('wraplist'+ wrap_lst);
    }