Apex Code Development You need to sign in to do that
Don't have an account?
Gil Hecht How and where should I write a testmethod for this class?
I'm working in sandbox and I want to deploy this to my production but I currently have 0% coverage. Any help is appreciated!
public class tenPageSizeExt { public tenPageSizeExt(ApexPages.StandardSetController controller) { controller.setPageSize(10); } }
public class tenPageSizeExt { public tenPageSizeExt(ApexPages.StandardSetController controller) { controller.setPageSize(10); } }
My apologies - you need to requery for those records before you can pass them through to the SSC. Should have caught that the first time through. Corrected code follows:
@isTest private class BoardsDemoUT { @isTest static void testController() { List<Account> lstAcctsInsert = new List<Account>(); for(Integer iCount = 0; iCount < 100; iCount++ ) { lstAcctsInsert.add(new Account(Name='Test Account ' + string.valueOf(iCount))); } // Insert List of Accounts insert lstAcctsInsert; // Requery for Accounts List<Account> lstAccts = [SELECT Id, Name FROM Account LIMIT 100]; // Start Test test.startTest(); // Instanciate Class and pass SSC ApexPages.StandardSetController sscTest = new ApexPages.StandardSetController(lstAccts); tenPageSizeExt clsTest = new tenPageSizeExt(sscTest) // End Test test.stopTest(); } }All Answers
@isTest private class BoardsDemoUT { @isTest static void testController() { List<Account> lstAccts = new List<Account>(); for(Integer iCount = 0; iCount < 100; iCount++ ) { lstAccts.add(new Account(Name='Test Account ' + string.valueOf(iCount))); } // Insert List of Accounts insert lstAccts; // Start Test test.startTest(); // Instanciate Class and pass SSC ApexPages.StandardSetController sscTest = new ApexPages.StandardSetController(lstAccts); tenPageSizeExt clsTest = new tenPageSizeExt(sscTest) // End Test test.stopTest(); } }You SHOULD read up on Unit Tests and assertions (there are none in this code), but this should get you able to push to Production.
Please try below code
@isTest public class tenPageSizeExtTest { static testMethod void testMethod1() { List <Account> lstAccount = new List<Account>(); Account testAccount = new Account(); testAccount.Name='Test Account' ; lstAccount.add(testAccount); Account testAccount1 = new Account(); testAccount1.Name='Test Account1' ; lstAccount.add(testAccount1); insert lstAccount; Test.startTest(); Test.setCurrentPage(Page.YOUR_PAGE); // Please add your page name here ApexPages.StandardSetController stdSetController = new ApexPages.StandardSetController(lstAccount); stdSetController.setSelected(lstAccount); tenPageSizeExt ext = new tenPageSizeExt (stdSetController); Test.stopTest(); } }For more information on test class please check below blog :-
http://amitsalesforce.blogspot.in/2015/06/best-practice-for-test-classes-sample.html
http://amitsalesforce.blogspot.in/2015/06/salesforce-testing-best-practice.html
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 will help you
Thanks
Amit Chaudhary
amit.salesforce21@gmail.com
We need to write Test Class for each and every class which is available in our org,for deploy from sandbox to production.Test Class is similar to Class but its just business logic of whole Apex Class.With @Test we should write Test Class.All the best.If you get any problem let me know.
System.VisualforceException: Modified rows exist in the records collection-This error means that the records collection in your VF controller's memory have been modified, not that the underlying records in the database have been modified between paging requests.
My apologies - you need to requery for those records before you can pass them through to the SSC. Should have caught that the first time through. Corrected code follows:
@isTest private class BoardsDemoUT { @isTest static void testController() { List<Account> lstAcctsInsert = new List<Account>(); for(Integer iCount = 0; iCount < 100; iCount++ ) { lstAcctsInsert.add(new Account(Name='Test Account ' + string.valueOf(iCount))); } // Insert List of Accounts insert lstAcctsInsert; // Requery for Accounts List<Account> lstAccts = [SELECT Id, Name FROM Account LIMIT 100]; // Start Test test.startTest(); // Instanciate Class and pass SSC ApexPages.StandardSetController sscTest = new ApexPages.StandardSetController(lstAccts); tenPageSizeExt clsTest = new tenPageSizeExt(sscTest) // End Test test.stopTest(); } }How to write the positive test classes in salesforce?