+ Start a Discussion
Ben Merton 15Ben Merton 15 

Test Class issue

I am trying to create a test class for the following:
public class CreateIndentController{
    string workOrderId;
    string productId;
    string woquantitylist;
    decimal woquantity;
    decimal sequenceno;
    datetime wocompletiondate;
    datetime requireddate;

    public CreateIndentController()
        workOrderId = ApexPages.currentPage().getParameters().get('id');
        productId = ApexPages.currentPage().getParameters().get('productId');
        List<unifize__Work_Order__c> woquantitylist = [select unifize__Completion_Date_Time__c, unifize__Quantity__c FROM unifize__Work_Order__c WHERE unifize__Product__c = :productId];
        wocompletiondate = woquantitylist[0].unifize__Completion_Date_Time__c;
        List<unifize__BOM_Item__c> cycletimesequencelist = [select unifize__Cycle_Time__c, unifize__Sequence_No__c FROM unifize__BOM_Item__c WHERE unifize__Product__c = :productId];
        System.debug('Product ID 1' + productId);
        System.debug('Work Order ID 1' + workorderId);
        System.debug('Work Order Quantity' + woquantity);
This is how far I have got so far.  I realise I am completely way off, but it is hours and I am completely frustrated.  The main problem is that the variable is 'invisible', presumably because it is being assigned to a list.  Also, I don't really understand the method of actually testing whether the if clause passes or fails.  Please help!
public class TestCreateIndentController{
static testMethod void testIndentController()


CreateIndentController abc = new CreateIndentController();
List<unifize__Work_Order__c> woquantitylist = new List<unifize__Work_Order__c>{'system.now()','1'};
abc.woquantity = 1.0;
abc.sequenceno = 1.0;
abc.wocompletiondate = system.now();
abc.requireddate= system.now();
ApexPages.currentPage().getParameters().put('abc.id', 'a0M1500000UGHdo');
Apexpages.currentpage().getparameters().put('abc.productId' , 'a041500000amOvl');

    //if (string.IsBlank(abc.productId))
    //    {
    //        ApexPages.addMessage(new ApexPages.message(ApexPages.Severity.ERROR, 'No product selected on the Work Order'));
            //return null;
    //    }
    // System.debug('Product ID 1' + abc.productId);   

Chandra Sekhar CH N VChandra Sekhar CH N V
First thing I notice is there is no '@isTest' annotation.

You need to just insert test records for unifize__Work_Order__c & unifize__BOM_Item__c objects which should do the job!!!


Abhishek BansalAbhishek Bansal
Hi Ben,

Test classes are used to test the code that we write in salesforce.
So in order to test the code we have to create first create the dummy data in our test class and than we will call our methods to test the coverage of our code.
Please follow the below steps to get started with your test class :

1. Create Work Order and Product in your test class
2. Set the Page to your visual force page and than set the parameters which you are gettting in class.
3. call the class and methods to test the coverage.

Please take help from the links given below :

I you still face any issue and need help than feel free to ask.

Abhishek Bansal.
Amit Chaudhary 8Amit Chaudhary 8
Please check below post for test classes. I hope that will help you
1) http://amitsalesforce.blogspot.com/search/label/Test%20Class
2) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html
Please to create your test class like below
public class TestCreateIndentController 
	static testMethod void testMethod1() 
		Account testAccount = new Account();
		testAccount.Name='Test Account' ;
		insert testAccount;

		unifize__Product__c prod = new unifize__Product__c();
		// add all required here
		insert prod;
		unifize__Work_Order__c workOrder = new unifize__Work_Order__c();
		// add all required field here
		//workOrder.unifize__Product__c = prod.id;
		insert workOrder;

			PageReference pageRef = Page.AccountPlan; // Add your VF page Name here
			pageRef.getParameters().put('id', String.valueOf(testAccount.Id));
			pageRef.getParameters().put('productId', String.valueOf(prod.Id));

			CreateIndentController testAccPlan = new CreateIndentController();
			//testAccPlan.save(); call all your function here
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