+ Start a Discussion

How to write test class for this controller

public class AccContExt {

    private final Account account{get; set;}
    public AccContExt(ApexPages.StandardController controller) {
           this.account= (Account)controller.getRecord();


James LoghryJames Loghry
Hi Sumit,

First off, it sounds like you should head over to the Unit Testing module on Trailhead, and hopefully you'll get an idea of how unit tests work with Apex.

Your controller is really simple, and there's not much to it, so there's not a whole lot to test per se, but in general this is how you would set up your unit test class:
private class AccContExtTest{

    static testmethod void testConstructor(){
        //Set up a new account record. You  may need to populate additional required fields,
        //based on your security settings or validation rules, etc.
        Account a = new Account(Name='Test');
        insert a;
        AccContExt extension = new AccContExt(new ApexPages.StandardController(a));

        //Assertions go here
James LoghryJames Loghry
I forgot to include a link to the trailhead module.  Here you go: https://trailhead.salesforce.com/module/apex_testing
Thanks,  But I am getting this error :

Error: Compile Error: Invalid constructor syntax, name=value pairs can only be used for SObjects at line 7 column 21
James LoghryJames Loghry
Please check to see if you have any Apex classes named "Account" that could be overriding the standard object / constructor.
thanks james Now getting this error :Constructor not defined: [AccContExt].<Constructor>(ApexPages.StandardController) at line 11 column 32
Amit Chaudhary 8Amit Chaudhary 8
If you have any class with Account Name then please rename the same class or delete the same class.

You write a test class for this the same way that you would any other:
- Set up some data for the controller to access (in this case it looks like Account records)
- Instantiate the StandardController -
- Execute a method/methods if any
- Verify the behaviour with asserts.

Please check below post to learn about test classes
1) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html
2) https://trailhead.salesforce.com/module/apex_testing

I tired below code in my org which is working fine and giving 100% code coverage
private class AccContExtTest
    static testmethod void testConstructor()
        Account a = new Account(Name='Test');
        insert a;
            AccContExt extension = new AccContExt(new ApexPages.StandardController(a));
            //you cnt access extension.account.Id here as account is private variable here

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