You need to sign in to do that
Don't have an account?
Manid
test class for the standard controller
public class ExtentionExample1 { public account acc {get;set;} public ExtentionExample1(apexpages.standardcontroller cont){ string[] names=new string[]{'name','phone','industry','rating'}; cont.addfields(names); acc=(account)cont.getrecord(); } public pagereference save(){ string str=acc.name; integer count=[select count() from account where name =: str]; if(count>0){ acc=[select name,phone,industry,rating from account where name =: str]; return null; } else{ insert acc; pagereference pag=new pagereference('/'+acc.Id); return pag; } } }plz write the test class for the above code
1) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html
I tested your code in my org and found you are getting "You cannot call addFields when the data is being passed into the controller by the caller" in test class due to below code in apex class
Even same code is not in use. So you can delete same code or use
if (!Test.isRunningTest()) cont.addFields(fields);
Please try below code
Test class
Let us know if this will help you
All Answers
public class MassDeleteTest {
testmethod static void testme(){
list<account> accs=new list<account>();
account a=new account(name='Test name');
insert a;
account a2=new account(name='Acme pro');
insert a2;
accs.add(a);
accs.add(a2);
test.startTest();
pagereference pref=page.massDeleteAcc;
test.setCurrentPage(pref);
apexpages.standardsetcontroller std=new apexpages.StandardSetController(accs);
std.setselected(accs);
MassDelete obj=new Massdelete(std);
obj.deletes();
test.stopTest();
}
}
You need to complete the Trailhead module to learn Apex Testing. It is one of the important steps of your development process.
https://trailhead.salesforce.com/en/modules/apex_testing
Once you are done with the above module, you will understand the importance of test classes, test coverage and how to write test classes in Apex.
You can go through the below Salesforce Developer Documentation as well.
https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_qs_test.htm
Please accept this as best answer if my reply is helpful.
so write like this everything is covered except this.
1) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html
I tested your code in my org and found you are getting "You cannot call addFields when the data is being passed into the controller by the caller" in test class due to below code in apex class
Even same code is not in use. So you can delete same code or use
if (!Test.isRunningTest()) cont.addFields(fields);
Please try below code
Test class
Let us know if this will help you
I will recommend you to start using trailhead to learn about test classes
1) https://trailhead.salesforce.com/modules/apex_testing
Also please check below post
1) https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_qs_test.htm
2) https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_testing_example.htm
3) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.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 post will help you