You need to sign in to do that
Don't have an account?
d.tejdeep@nicomatic.in
cant able to test file extension on test class?
visuaforce page:
test class :
Cant able to cross this section of code in code coverage :
I tried many possible to cross code coverage but still it is at that point .Please help me in this regard.
Thanks in advance
<apex:page sidebar="false" controller="UploadOpportunityScheduleLineItem123"> <apex:form > <apex:sectionHeader title="Upload data from CSV file"/> <apex:pagemessages /> <center> <apex:inputFile value="{!contentFile}" filename="{!nameFile}" /> <apex:commandButton action="{!ReadFile}" value="Upload File" id="theButton" style="width:70px;"/> <br/> <br/> </center> </apex:form> </apex:page>apex:
public with sharing class UploadOpportunityScheduleLineItem123{ // Global variables public string nameFile{get;set;} Public Id parentId{get;set;} public Blob contentFile{get;set;} List<account> lstScheduleToUpdate = new List<account>(); public account objSchedule{get;set;} //String array for taking csv data by line. String[] filelines = new String[]{}; //set for storing all id's from csv. set<String> opptoupload{get;set;} //Main constructor public UploadOpportunityScheduleLineItem123() { //Initalizing required objects. objSchedule = new account(); opptoupload = new set<String>(); } //Method to read file content and check extension and file format. public Pagereference ReadFile() { parentId=Apexpages.currentPage().getParameters().get('ParentId'); //If without selecting csv file you clicked on upload it will give error message. if(nameFile == null) { ApexPages.Message errormsg = new ApexPages.Message(ApexPages.severity.ERROR,'You should select csv file to upload'); ApexPages.addMessage(errormsg); return null; } //Taking file extension. String extension = nameFile.substring(nameFile.lastIndexOf('.')+1); //Checking if file extension is .csv. if(extension == 'csv' ||extension == 'CSV') { nameFile =blobToString( contentFile,'ISO-8859-1'); //Spliting by new line filelines = nameFile.split('\n'); //Spliting values by (,) for checking coloumn size for (Integer i=1;i<filelines.size();i++){ String[] inputconvalues = new String[]{}; inputconvalues = filelines[i].split(','); account b = new account(); b.name= inputconvalues[0]; b.billingcountry = inputconvalues[1]; b.billingcity = inputconvalues[2]; lstScheduleToUpdate.add(b); } //Checking if list is not empty then updating. if(lstScheduleToUpdate.Size()>0) { insert lstScheduleToUpdate; } ApexPages.Message errormsg = new ApexPages.Message(ApexPages.severity.info,'Batches File uploaded successfully'); ApexPages.addMessage(errormsg); return null; } //If file is not csv type then it will give error message. else { ApexPages.Message errormsg = new ApexPages.Message(ApexPages.severity.ERROR,'File type should be csv type'); ApexPages.addMessage(errormsg); return null; } } public static String blobToString(Blob input, String inCharset){ String hex = EncodingUtil.convertToHex(input); System.assertEquals(0, hex.length() & 1); final Integer bytesCount = hex.length() >> 1; String[] bytes = new String[bytesCount]; for(Integer i = 0; i < bytesCount; ++i) bytes[i] = hex.mid(i << 1, 2); return EncodingUtil.urlDecode('%' + String.join(bytes, '%'), inCharset); } }
test class :
@IsTest(SeeAllData=true) private class testexceltoaccount { static testmethod void testLoadData() { StaticResource testdoc = [Select Id,Body from StaticResource where name ='testMethodCSVUpload1']; UploadOpportunityScheduleLineItem123 testUpload = new UploadOpportunityScheduleLineItem123(); testUpload.contentFile= testdoc.Body; testUpload.ReadFile(); } }
Cant able to cross this section of code in code coverage :
String extension = nameFile.substring(nameFile.lastIndexOf('.')+1); //Checking if file extension is .csv. if(extension == 'csv' ||extension == 'CSV') {
I tried many possible to cross code coverage but still it is at that point .Please help me in this regard.
Thanks in advance
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.
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
Thanks
Amit Chaudhary
All Answers
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.
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
Thanks
Amit Chaudhary