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
mritzmritz 

How to write Test Class for this Apex Class?

I have an apex class which takes project Id from the URL of VF Page and displays all tasks assigned to it. The VF Page is opened from a custom button on Standard SFDC project object layout
(Sample URL: https://<sfdc instance>/apex/TaskPage?id=<projectId>)
I need help to write test class for this Apex Class

Apex Class
public class TaskClass{
	Id projectId;
	String errorMessage{get;set;}
	public List<Task__c>  taskList{get;set;}
	
	public TaskClass(){
		projectId = ApexPages.currentPage().getParameters().get('id');
		if(projectId!=null){
			try{
				taskList = [Select id,Name from Task__c where project__c =: projectId];
			}catch(Exception e){
				errorMessage = 'No records found';
			}
		}
		else
			errorMessage = 'Invalid URL';
	}
	//other functions
}

 
Mani RenusMani Renus
Hi,

Try to add the follow things in your test class! 

public project__c p=new project__c ();

p.name='Test';
'
'
'
so on add all mandatory fields

Insert p;

public TaskClass tc;

tc.projectId = System.currentPageReference().getParameters().put('Id', p.Id);

Hope it works for you!!
Amit Chaudhary 8Amit Chaudhary 8
PLease check below post
http://amitsalesforce.blogspot.in/search/label/Test%20Class (http://amitsalesforce.blogspot.in/search/label/Test%20Class http://amitsalesforce.blogspot.in/2015/06/best-practice-for-test-classes-sample.html)
http://amitsalesforce.blogspot.in/2015/06/best-practice-for-test-classes-sample.html (http://amitsalesforce.blogspot.in/search/label/Test%20Class http://amitsalesforce.blogspot.in/2015/06/best-practice-for-test-classes-sample.html)

 
@isTest 
public class TaskClassTest 
{
	static testMethod void testMethod1() 
	{
		Account testAccount = new Account();
		testAccount.Name='Test Account' ;
		insert testAccount;

		project__c project = new project__c ();
		// add all required field here
		insert project;
		
		Task__c tsk = new Task__c();
		// add all required field;
		tsk.project__c  = project.id;
		
		Test.StartTest(); 
		
			ApexPages.currentPage().getParameters().put('id',project.id);
			TaskClass obj = new TaskClass();
		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
Prem Anandh 1Prem Anandh 1
Hi Mritz, 

I have updated the Test Class as per your scenario. Please check with below code.

Controller:  I have done a bit modification on your controller.
 
public class TaskClass{
	Id projectId;
	public String errorMessage{get;set;}
	public List<Task__c>  taskList{get;set;}
	
	public TaskClass(){
		projectId = ApexPages.currentPage().getParameters().get('id');
		if(projectId!=null){
			try{
				taskList = [Select id,Name from Task__c where project__c =: projectId];
				
				//Just to cover the Catch block 
				if(Test.isRunningTest())
				Integer c = 5/0;
			}catch(Exception e){
				errorMessage = 'No records found';
			}
		}
		else
			errorMessage = 'Invalid URL';
	}
	//other functions
}

Test Class Code:
 
@isTest
Private class TaskClass_Test {
    
    Private Static testmethod void TaskClass_Test()
    {
        //Create Project with Mandatory fields
        Project__c objProject = new Project__c(Name = 'Test');
        insert objProject;
        
        //Create Task records with Madatory fields
        Task__c objTask = new Task__c(Project__c = objProject.Id);
        insert objTask;
        
        //Put your parameter name to pass your controller. 
        System.currentPageReference().getParameters().put('Id', objProject.Id);
        
        //Invoking Controller Constructor
        TaskClass objTaskClass = new TaskClass();
        
        //To check the list is retived created task record or not
        System.assertNotEquals(null, objTaskClass.taskList);
        
        
        //Put wrong parameter name to pass your controller. 
        System.currentPageReference().getParameters().remove('Id');
        //To call our else condition If(ProjectId != null)
        TaskClass objTaskClass1 = new TaskClass();
        
        System.assertEquals('Invalid URL', objTaskClass1.errorMessage);
        
        
        
    }

}

It's working fine for me. Please let me know if you are facing any issues. 

Thanks,
Prem Anandh
Mahesh DMahesh D
Hi Mritz,

Please find the below class:
 
public class TaskClass {
    Id projectId;
    public String errorMessage{get;set;}
    public List<Task__c>  taskList{get;set;}
    
    public TaskClass() {
        projectId = ApexPages.currentPage().getParameters().get('id');
        if(projectId != null) {
            try {
                taskList = [Select id,Name from Task__c where project__c =: projectId];
            } catch(Exception e){
                errorMessage = 'No records found';
            }
        }
        else
            errorMessage = 'Invalid URL';
    }
    //other functions
}

Test Class:
 
@isTest
public class TaskClassTest {
    @isTest
    public static void testMethodOne() {
        Project__c proj = new Project__c();
        proj.Name = 'Test Proj';
        insert proj;
        
        Task__c tas = new Task__c();
        tas.Name = 'Test Task';
        tas.Project__c = proj.Id;
        insert tas;
        
        ApexPages.currentPage().getParameters().put('id', tas.Id);
        TaskClass tc = new TaskClass();
        System.assertEquals(null, tc.errorMessage);
    }
    
    @isTest
    public static void testMethodTwo() {
        Project__c proj = new Project__c();
        proj.Name = 'Test Proj';
        insert proj;
        
        Task__c tas = new Task__c();
        tas.Name = 'Test Task';
        tas.Project__c = proj.Id;
        insert tas;
        
        TaskClass tc = new TaskClass();
        System.assertEquals('Invalid URL', tc.errorMessage);
    }
}

Also tested the above code and it looks good.

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 do let me know if it helps you.

Regards,
Mahesh