You need to sign in to do that
Don't have an account?
Ola Bamidele
How to a start a test class for my code
Hi All,
I completed my extension page so now I need to write a test class.
I have been researching into how to write a test class but all the example i have seen are very different to mine therefore I dont still undertand how to apply the content to my test class.
This is my extension page code:
public with sharing class extencntrl{
private ApexPages.StandardController sc;
public extencntrl(ApexPages.StandardController sc) {
this.sc = sc;
}
public boolean displayPopup {get; set;}
public void closePopup() {
displayPopup = false;
}
public void showPopup() {
displayPopup = true;
}
public PageReference Save() {
PageReference detailPage = sc.Save();
if (detailPage != null) {
PageReference editPage = new PageReference(Label.websiteurl);
return editPage ;
} else {
return detailPage;
}
}
}
Please if someone knows how I could possible start developing the test class, please let me know!
Thanks,
Ola
I completed my extension page so now I need to write a test class.
I have been researching into how to write a test class but all the example i have seen are very different to mine therefore I dont still undertand how to apply the content to my test class.
This is my extension page code:
public with sharing class extencntrl{
private ApexPages.StandardController sc;
public extencntrl(ApexPages.StandardController sc) {
this.sc = sc;
}
public boolean displayPopup {get; set;}
public void closePopup() {
displayPopup = false;
}
public void showPopup() {
displayPopup = true;
}
public PageReference Save() {
PageReference detailPage = sc.Save();
if (detailPage != null) {
PageReference editPage = new PageReference(Label.websiteurl);
return editPage ;
} else {
return detailPage;
}
}
}
Please if someone knows how I could possible start developing the test class, please let me know!
Thanks,
Ola
Please check once below code :
I hope it helps you.
Thanks
Varaprasad
Thanks for your response. I tried the code but i am getting this error on line 5:
Constructor not defined: [ApexPages.StandardController].<Constructor>()
Thanks very much!
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
sample Test classes
1) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html
Sample test class to start
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 .
Let us know if this will help you
Thanks for your reply. I tried the code that you suggested and it worked with a 92% code coverage. The only line that was'nt covered on my extension page was "return detailpage;" (LIne 25).
I have been doing some research into why this line wasnt covered and I reed something like "test class didn’t contain a test to pass an invalid state parameter"
I am currently looking more into it but if you already know how to resolve this then please let me know, thanks!
Let us know if this will help you
Thanks again for your reply. I tried the code and its still 92% coverage. It also shows 1 failure in the tests tab this time.
Do you know why did could be? I assume it to do with the "static testmethod void validateStandardController1()" that was added in the second code.
Thanks very much again!
I hope 92% good code coverage for you for now
Okay I understand. however, I need the code to have 100% coverage. Is their a way around this as for when I change null the whole code doesnt work no more
Thanks very much
I just tried it and it worked perfectly, thanks very much!
Sorry to ask you another question :D
But ive changed my apex as code so the apex test therefore doesnt work anymore.
Could you perphaps point me in the right direction on how I could rewrite the test class for my new apex code?
This is my updated apex code:
Thanks very much!
Let us know if this will help you