You need to sign in to do that
Don't have an account?
swain 10
How to write test class for this apex class and can anyone explain the trick to write test class
Apex class:
public class multiAddCEx {
public multiAddCEx(ApexPages.StandardSetController controller) {
}
public multiAddCEx(ApexPages.StandardController controller) {
}
List <Expense_Line_Item__c> CExList;
public Id cID = ApexPages.currentPage().getParameters().get('Id');
public Id getID {get; set;}
public PageReference reset() {
CExList = [select name, Expense__c, Expense_Head__c, Amount__c, Date__c, Sub_Expense__c, Payment_Type__c, Cost_Head__c from Expense_Line_Item__c where Expense__c =: cID order by createddate limit 15 ];
return null; }
public List <Expense_Line_Item__c> getCExs() {
if(CExList == null) reset();
return CExList;}
public void setAccounts(List <Expense_Line_Item__c> cexs) {
CExList = cexs;}
public PageReference save() {
upsert CExList;
ApexPages.Message myMsg = new ApexPages.message(ApexPages.Severity.Info, 'Records Saved Successfully');
return null;}
public PageReference add() {
CExList.add(New Expense_Line_Item__c(Expense__c= cID));
return null; }
}
public class multiAddCEx {
public multiAddCEx(ApexPages.StandardSetController controller) {
}
public multiAddCEx(ApexPages.StandardController controller) {
}
List <Expense_Line_Item__c> CExList;
public Id cID = ApexPages.currentPage().getParameters().get('Id');
public Id getID {get; set;}
public PageReference reset() {
CExList = [select name, Expense__c, Expense_Head__c, Amount__c, Date__c, Sub_Expense__c, Payment_Type__c, Cost_Head__c from Expense_Line_Item__c where Expense__c =: cID order by createddate limit 15 ];
return null; }
public List <Expense_Line_Item__c> getCExs() {
if(CExList == null) reset();
return CExList;}
public void setAccounts(List <Expense_Line_Item__c> cexs) {
CExList = cexs;}
public PageReference save() {
upsert CExList;
ApexPages.Message myMsg = new ApexPages.message(ApexPages.Severity.Info, 'Records Saved Successfully');
return null;}
public PageReference add() {
CExList.add(New Expense_Line_Item__c(Expense__c= cID));
return null; }
}
1-basic of test class http://www.sfdc99.com/2013/05/14/how-to-write-a-test-class/
2-All about test classes https://developer.salesforce.com/page/An_Introduction_to_Apex_Code_Test_Methods
3- summarized information https://developer.salesforce.com/forums/?id=906F0000000BYwzIAG (https://developer.salesforce.com/forums/?id=906F0000000BYwzIAG )
I hope this information is informative,
Thanks varun
All Answers
then call all the method and see what coverage you got.
also you have to create a List <Expense_Line_Item__c>.
Please go through Amit chaudhary's answer in this (https://developer.salesforce.com/forums/?id=906F0000000BYwzIAG) thread, he has summarized most of the best practices for writing test classes.
These are the 29 points that he has mentioned:
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 .
Hope this helps,
Sandeep
when u are writing a test class u need some test data , which will not reflect on actual data
Note any record created in test class in not updated in real database
you can create test data in @testSetup meathod (best practice)
then create testMeathod and call the class and check for assert
in the below case i called a custom controler to check if records are creted properly
check the following link It has the proper code for it
https://developer.salesforce.com/forums/ForumsMain?id=9060G000000BfnuQAC
you have to create aa record of Expense__c
cretae Expense_Line_Item__c item and set Expense__c
ApexPages.CurrentPage().getParameters().Put('Id'Expence__c);
ApexPages.StandardController sc = new ApexPages.StandardController(pass id of Expence__c);
multiAddCEx mu= new multiAddCEx (sc);
//then call all methods
mu.rest();
mu.add();
mu.save();
Test Class
@isTest
public class multiAddCExTest{
public static testMethod void methodMultiadd(){
insert Expense__c ;
insert Expense_Line_Item__c item with Expence__C
then do other things
ApexPages.CurrentPage().getParameters().Put('Id'Expence__c);
ApexPages.StandardController sc = new ApexPages.StandardController(pass id of Expence__c);
multiAddCEx mu= new multiAddCEx (sc);
//then call all methods
mu.rest();
mu.add();
mu.save();
Test Class
}
}
I Hope this is helpful for You Select my answer as best.
Ask fell free if you have any doubt.
Let us know if this will help you
1-basic of test class http://www.sfdc99.com/2013/05/14/how-to-write-a-test-class/
2-All about test classes https://developer.salesforce.com/page/An_Introduction_to_Apex_Code_Test_Methods
3- summarized information https://developer.salesforce.com/forums/?id=906F0000000BYwzIAG (https://developer.salesforce.com/forums/?id=906F0000000BYwzIAG )
I hope this information is informative,
Thanks varun
- every test class in salesforce follows the same pattern:
- starts with @isTest
- You need to set the test data
- start the test by calling Test.startTest()
- Calling your class/method
- Stopping the test by calling Test.stopTest() to reset the governor limits and allow for any async jobs to finish.
- Asserting that your changes have worked
- If you have made any change o the record, you need to query for the updates
- Run System.assert, System.assertNotEquals,System.assertEquals to verify that you got the correct data
For complete detail, on test class, you can check test class in Salesforce| developer Guide (https://sfdcwisdom.com/test-class-in-salesforce/)