Apex Code Development You need to sign in to do that
Don't have an account?
Test class method does not exist or incorrect signature: void
// Trigger
trigger Opportunity_Misc on Opportunity (before insert, before Update)
if(Trigger.isBefore && Trigger.isInsert){
MyHelperClass.NewStep(Trigger.new);
}
// class
public with sharing class MyHelperClass {
public static void NewStep(List<Opportunity> newstepopps){
}
// test clas
@isTest
public static void testNewStep(){
// create test opportunity
Opportunity opp = Test_Helper.CreateOpp(contact,user);
insert(opp);
Test.startTest();
Opportunity opp1 = opp.clone(true);
List<Opportunity> newloanopps = AutoAssignCampaignHelper.NewLoan(opp1);
Test.stopTest();
}
trigger Opportunity_Misc on Opportunity (before insert, before Update)
if(Trigger.isBefore && Trigger.isInsert){
MyHelperClass.NewStep(Trigger.new);
}
// class
public with sharing class MyHelperClass {
public static void NewStep(List<Opportunity> newstepopps){
}
// test clas
@isTest
public static void testNewStep(){
// create test opportunity
Opportunity opp = Test_Helper.CreateOpp(contact,user);
insert(opp);
Test.startTest();
Opportunity opp1 = opp.clone(true);
List<Opportunity> newloanopps = AutoAssignCampaignHelper.NewLoan(opp1);
Test.stopTest();
}
Try this :
@isTest public class Opportunity_Misc_Test{ public static testmethod void testNewStep(){ // create test opportunity Opportunity opp = Test_Helper.CreateOpp(contact,user); insert(opp); Test.startTest(); Opportunity opp1 = opp.clone(true); List<Opportunity> newloanopps = AutoAssignCampaignHelper.NewLoan(opp1); Test.stopTest(); } }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 .
Hope this helps you!
If my answer helps resolve your query, please mark it as the 'Best Answer' & upvote it to benefit others.
Thanks
Varaprasad
@For SFDC Support: varaprasad4sfdc@gmail.com
Blog: http://salesforceprasad.blogspot.com/
Salesforce latest interview questions :
https://www.youtube.com/channel/UCOcam_Hb4KjeBdYJlJWV_ZA?sub_confirmation=1
@isTest public class Opportunity_MiscTest { static testMethod void Opportunity_MiscTestMetod() { //Created record from scratch // Create a test account System.Test.startTest(); Account testAcct = new Account (Name = 'My Test Account'); insert testAcct; // Creates first opportunity Opportunity oppt = new Opportunity(Name ='New mAWS Deal', AccountID = testAcct.ID, StageName = 'Customer Won', Amount = 3000, CloseDate = System.today()); insert oppt; System.Test.stopTest(); } }I shoul have posted my code snippet in the correct context as to enable you to get a better idea.
I try to follow best practice. In this case, all i am trying to do is passing a list of newly created opportunities to a method in my helper class.
I fail to figure out why I am getting the error 'Method does not exist or incorrect signature: void NewLoan(Opportunity) from the type MyHelper'
// Trigger trigger Opportunity_Misc on Opportunity (before insert, before Update) { if(Trigger.isBefore && Trigger.isInsert){ MyHelperClass.NewLoan(Trigger.new); } } //MyHelperClass public with sharing class MyHelperClass{ public static void NewLoan(List<Opportunity> newloanopps){ // all the logic } } // Test Class @isTest public class MyTest { public static testmethod void testNewLoan(){ // create test opportunity Opportunity opp = Test_Helper.CreateOpp(contact,user); insert(opp); Test.startTest(); Opportunity opp1 = opp.clone(true); List<Opportunity> newloanopps = MyHelperClass.NewLoan(opp1); Test.stopTest();@isTest
public class MyTest {
public static testmethod void testNewLoan(){
Opportunity opp = Test_Helper.CreateOpp(contact,user);
insert(opp);
List<Opportunity > lstOpp = new List<Opportunity >();
Test.startTest();
Opportunity opp1 = opp.clone(true);
lstOpp.add(opp1 );
List<Opportunity> newloanopps = MyHelperClass.NewLoan(lstOpp);
Test.stopTest();
NOTE:- You dnt need to call helper method mannualy as it will call from Trigger so you need to just create Opp record.
I am aware of passing the list of opps, since my helperclass method accepts a list of opportunities.
However, even when i pass a list, I get the illegal assignment from void to list < Opportunity > error
The only way around to successfully compile is to instantiate the helper class.
MyHelperClass mhc = new MyHelperClass ();
MyHelperClass .NewLoan(lstOpp); // Compiles without error
mhc .NewLoan(lstOpp); // throws compilation error
I fail to understand why?
As of now, i am ok with my test class.
I am good for now. I rewrote my Helper class to adhere to best practices.
You can try below code
@isTest public class MyTest { public static testmethod void testNewLoan(){ Opportunity opp = Test_Helper.CreateOpp(contact,user); insert(opp); List<Opportunity > lstOpp = new List<Opportunity >(); Test.startTest(); Opportunity opp1 = opp.clone(true); lstOpp.add(opp1 ); List<Opportunity> newloanopps = MyHelperClass.NewLoan(lstOpp); Test.stopTest(); } }In case you find any other issue please mention.
If you find your Solution than mark as this as a best answer.
Thanks and Regards
Suraj Tripathi.