function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
sf ostsf ost 

Error. Method not Visible

Hi Guys,

As a part of learning salesforce i got some errors in testClass. Need help on those errors. why they got ?

Error: Compile Error: Method is not visible: VerifyDate.DateWithin30Days(Date, Date) at line 31 column 21, and
Error: Compile Error: Method does not exist or incorrect signature: VerifyDate.SetEndOfonMonthDate(Date) at line 40 column 21

Apex Class:
public class VerifyDate {
    
    //method to handle potential checks against two dates
    public static Date CheckDates(Date date1, Date date2) {
        //if date2 is within the next 30 days of date1, use date2.  Otherwise use the end of the month
        if(DateWithin30Days(date1,date2)) {
            return date2;
        } else {
            return SetEndOfMonthDate(date1);
        }
    }
    
    //method to check if date2 is within the next 30 days of date1
    private static Boolean DateWithin30Days(Date date1, Date date2) {
        //check for date2 being in the past
            if( date2 < date1) { return false; }
        
            //check that date2 is within (>=) 30 days of date1
            Date date30Days = date1.addDays(30); //create a date 30 days away from date1
        if( date2 >= date30Days ) { return false; }
        else { return true; }
    }

    //method to return the end of the month of a given date
    private static Date SetEndOfMonthDate(Date date1) {
        Integer totalDays = Date.daysInMonth(date1.year(), date1.month());
        Date lastDay = Date.newInstance(date1.year(), date1.month(), totalDays);
        return lastDay;
    }

}

and below is my testClass:
@isTest

private class TestVerifyDate{

    @isTest static void TVD1(){
    
        Date Date1 = Date.parse('1/03/16');
        Date Date2 = Date.parse('12/03/16');

        Date TVD1 = VerifyDate.CheckDates(Date1, Date2);
        System.assertEquals(Date2, TVD1);

    }
    
    @isTest static void TVD2(){
    
        Date Date1 = Date.parse('1/03/16');
        Date Date2 = Date.parse('12/03/16');
        Date firstDayOfMonth = System.today().toStartOfMonth();

        Date TVD2 = VerifyDate.CheckDates(Date1,Date2);
        System.assertEquals(Date1.addDays(Date.daysInMonth(firstDayOfMonth.year(), firstDayOfMonth.month()) - 1), TVD2);

    }
    
    @isTest static void TVD3(){
    
      	Date Date1 = Date.parse('1/03/16');
       	Date Date2 = Date.parse('12/03/16');
        
       	Date TVD3 = VerifyDate.DateWithin30Days(Date1, Date2);
       	System.assertEquals(false, TVD3);

   }
    
   @isTest static void TVDL(){
    
       	Date Date1 = Date.parse('1/03/16');
       
        Date TVDL = VerifyDate.SetEndOfonMonthDate(Date1);
        System.assertEquals(Date1, TVDL);

   }


}

any modifications to the testClass ? Help me regarding this.
 
Best Answer chosen by sf ost
Amit Chaudhary 8Amit Chaudhary 8
Hi sf ost,

Problem in your test class is that you are try to access the private method in your test class. Which is wrong.
As per your code you need to call only VerifyDate.CheckDates(System.today(),System.today()+1); method which will call your private method in class.

So simply copy paste below test class and try

@isTest  public class TestVerifyDate {     
   static testMethod void testMethod1()      
   {         
         Date d = VerifyDate.CheckDates(System.today(),System.today()+1);         Date d1 = VerifyDate.CheckDates(System.today(),System.today()+60);     
  }

}

All Answers

Mahesh DMahesh D
Hi,

You can't call the Private methods outside the class.

Need to change Test Class to cover the Public Methods, so that private methods will automatically covers.

Please use the below Test Class:

 
@isTest
private class TestVerifyDate{

    @isTest 
	static void TVD1(){    
        Date Date1 = Date.parse('1/03/16');
        Date Date2 = Date.parse('12/03/16');

        Date TVD1 = VerifyDate.CheckDates(Date1, Date2);
        System.assertEquals(Date2, TVD1);

    }
    
    @isTest 
	static void TVD2(){    
        Date Date1 = Date.parse('1/03/16');
        Date Date2 = Date.parse('12/03/16');
        Date firstDayOfMonth = System.today().toStartOfMonth();

        Date TVD2 = VerifyDate.CheckDates(Date1,Date2);
        System.assertEquals(Date1.addDays(Date.daysInMonth(firstDayOfMonth.year(), firstDayOfMonth.month()) - 1), TVD2);
    }
	
	@isTest 
	static void TVD2(){    
        
        Date Date1 = Date.parse('12/03/16');
		Date Date2 = Date.parse('1/03/16');
        Date firstDayOfMonth = System.today().toStartOfMonth();

        Date TVD2 = VerifyDate.CheckDates(Date1,Date2);
		// Please add the assertion according to your requirement.
        //System.assertEquals(Date1.addDays(Date.daysInMonth(firstDayOfMonth.year(), firstDayOfMonth.month()) - 1), TVD2);
	}
}

Please check below post for test classes.

1) http://amitsalesforce.blogspot.com/search/label/Test%20Class (http://amitsalesforce.blogspot.com/search/label/Test%20Class" target="_blank)
2) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html (http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html" target="_blank)

3) https://developer.salesforce.com/page/An_Introduction_to_Apex_Code_Test_Methods


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 do let me know if it helps you.

Regards,
Mahesh
Tavva Sai KrishnaTavva Sai Krishna
Hi Sf ,

For 1st error:
Change the access type of the two methods from Private to Public to get out of the 1st error.

Please find below link  understand what Access Modifiers is
https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_access_modifiers.htm (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_access_modifiers.htm" target="_blank

For 2nd error: 
The method name is "SetEndOfMonthDate" which is defined in the class but whereas in test class you have defined the method name as "SetEndOfonMonthDate".  Please find the underlined text what is error in the word.

Let me know if you have face any errors,

Regards,
Sai Krishna Tavva.
Amit Chaudhary 8Amit Chaudhary 8
Please check below post..
1) https://developer.salesforce.com/forums/?id=906F0000000BQzJIAW
Pleae try below test class.
@isTest 
public class TestVerifyDate
{
    static testMethod void testMethod1() 
    {
        Date d = VerifyDate.CheckDates(System.today(),System.today()+1);
        Date d1 = VerifyDate.CheckDates(System.today(),System.today()+60);
    }
}

Please check below blog for more information in test classess:-
1) http://amitsalesforce.blogspot.in/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

Thanks,
Amit Chaudhary

 
sf ostsf ost
After changing the class from private to public still the same error..

Error: Compile Error: Method is not visible: VerifyDate.DateWithin30Days(Date, Date) at line 31 column 20

help me..
Mahesh DMahesh D
You can try this:
 
@isTest 
public class TestVerifyDate
{
    static testMethod void testMethodOne() 
    {
        Date d = VerifyDate.CheckDates(System.today(),System.today()+1);
        Date dOne = VerifyDate.CheckDates(System.today(),System.today()+60);
        Date dTwo = VerifyDate.CheckDates(System.today(),System.today()-60);
    }
}

Regards,
Mahesh
sf ostsf ost
Experiencing same error @Amit

Error: Compile Error: Method is not visible: VerifyDate.DateWithin30Days(Date, Date) at line 31 column 20

User-added image
Amit Chaudhary 8Amit Chaudhary 8
Hi sf ost,

Just simply replace you test class with below class, Same code is working fine in my developer org.
Class :- VerifyDate
public class VerifyDate {
  
  //method to handle potential checks against two dates
  public static Date CheckDates(Date date1, Date date2) {
    //if date2 is within the next 30 days of date1, use date2.  Otherwise use the end of the month
    if(DateWithin30Days(date1,date2)) {
      return date2;
    } else {
      return SetEndOfMonthDate(date1);
    }
  }
  
  //method to check if date2 is within the next 30 days of date1
  private static Boolean DateWithin30Days(Date date1, Date date2) {
    //check for date2 being in the past
          if( date2 < date1) { return false; }
        
          //check that date2 is within (>=) 30 days of date1
          Date date30Days = date1.addDays(30); //create a date 30 days away from date1
    if( date2 >= date30Days ) { return false; }
    else { return true; }
  }

  //method to return the end of the month of a given date
  private static Date SetEndOfMonthDate(Date date1) {
    Integer totalDays = Date.daysInMonth(date1.year(), date1.month());
    Date lastDay = Date.newInstance(date1.year(), date1.month(), totalDays);
    return lastDay;
  }

}
User-added image

Test class:-TestVerifyDate --------------- Simply copy paste same class in you org and try
@isTest 
public class TestVerifyDate
{
    static testMethod void testMethod1() 
    {
        Date d = VerifyDate.CheckDates(System.today(),System.today()+1);
        Date d1 = VerifyDate.CheckDates(System.today(),System.today()+60);
    }
}

User-added image


Let us know if this will help you

Thanks
Amit Chaudhary
amit.salesforce21@gmail.com
sf ostsf ost
if possible can u update my testClass ?
Amit Chaudhary 8Amit Chaudhary 8
Hi sf ost,

Problem in your test class is that you are try to access the private method in your test class. Which is wrong.
As per your code you need to call only VerifyDate.CheckDates(System.today(),System.today()+1); method which will call your private method in class.

So simply copy paste below test class and try

@isTest  public class TestVerifyDate {     
   static testMethod void testMethod1()      
   {         
         Date d = VerifyDate.CheckDates(System.today(),System.today()+1);         Date d1 = VerifyDate.CheckDates(System.today(),System.today()+60);     
  }

}
This was selected as the best answer
sf ostsf ost
Thanks Amit.. Resolved.. :)
sf ostsf ost
i have a doubt.. 

methods which are public only have testClasses or private too?
Amit Chaudhary 8Amit Chaudhary 8
you can access the public method only in test class. But you need to access private method then you need to use @TestVisible

Please check below post for same i hope that will help you
1) https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_testvisible.htm

Use the TestVisible annotation to allow test methods to access private or protected members of another class outside the test class. These members include methods, member variables, and inner classes. This annotation enables a more permissive access level for running tests only. This annotation doesn’t change the visibility of members if accessed by non-test classes.
With this annotation, you don’t have to change the access modifiers of your methods and member variables to public if you want to access them in a test method. For example, if a private member variable isn’t supposed to be exposed to external classes but it should be accessible by a test method, you can add the TestVisible annotation to the variable definition
public class TestVisibleExample {
    // Private member variable
    @TestVisible private static Integer recordNumber = 1;

    // Private method
    @TestVisible private static void updateRecord(String name) {
        // Do something
    }
}
@isTest
private class TestVisibleExampleTest {
    @isTest static void test1() {
        // Access private variable annotated with TestVisible
        Integer i = TestVisibleExample.recordNumber;
        System.assertEquals(1, i);

        // Access private method annotated with TestVisible
        TestVisibleExample.updateRecord('RecordName');
        // Perform some verification
    }
}
Let us know if this will help you

Thanks
Amit Chaudhary
 
sf ostsf ost
Thanks Amit. Thats a very useful information got from you. Cheers man.. 
BOUGUEM SIHOUTE JoelleBOUGUEM SIHOUTE Joelle
Hi Guys ,
the DateWithin30Days and SetEndOfMonthDate methods are private methods so they cannot be called in another scoop. it should also be noted that the CheckDates method calls on these two other methods and in addition it is public. so we can cover 100% of the code just by calling CheckDates in the test class.


@isTest
public class TestVerifyDate 
{
    @isTest public static void verifyDateTest ()
    {
        Date date1 = date.newInstance(2022, 10, 20) ;
        Date date2 = date.newInstance(2022, 10, 21) ;
        Date date3 = date.newInstance(2022, 10, 01) ;
        Date date4 = date.newInstance(2022, 10, 31) ;
        Date date5 = date.newInstance(2022, 11, 31) ;
        Date DT2   = VerifyDate.CheckDates(date1,date2);
        Date DT3   = VerifyDate.CheckDates(date1,date3);
        Date DT4   = VerifyDate.CheckDates(date1,date5);
        system.assertEquals(date2, DT2);
        system.assertEquals(date4, DT3);
        system.assertEquals(date4, DT4);
        
        
    }

}