Following code will be helpfull to cover wrapper class: Account acc=new Account (); acc.Name=’test’; insert acc; Checkbox_Class.accountwrapper wrap=new Checkbox_Class.accountwrapper (acc); I hope you find the above solution helpful. Full Answer What is a wrapper class in Salesforce? A Wrapper class is a class whose instances are collection of other objects. It is used to display … Read more
To create vf pages in Salesforce navigate to Setup | Build | Develop | Visualforce pages. Click on New button to create vf page. Enter label and Name. Follow these steps to create a Visualforce page in the Developer Console. Open the Developer Console under Your Name or the quick access menu ( … Click … Read more
You can write test class two ways- 1)By using static resources-In this you need to go Developer Console-> select File -> New -> Static Resource. 2)By implementing Interface. Create class->then implement interface. Full Answer How to write a test class in Salesforce? The key points while writing a test class are: You have to start … Read more
Add the name of the trigger as a comment above your test class and vice versa to make it easier to maintain code. For those wondering how to write test cases for triggers, remember that your trigger is activated by the operation on the object that its written against (i.e Insertion, update, delete, upsert). Full … Read more
The general format of a test class is: @isTest private class listViewTest { static testmethod void test1 () { } static testmethod void test2 () { } } From there, it’s a matter of constructing your class if you’re calling an instance method, or calling the method directly if it’s a static method. Full Answer … Read more
The key points while writing a test class are: You have to start your class with @isTest annotation, then only Salesforce will consider this class as test class. Keep your class as Private, and the best practice is to name your test class as your original Class or trigger Name + ‘Test’. Full Answer How … Read more
The key points while writing a test class are: You have to start your class with @isTest annotation, then only Salesforce will consider this class as test class. Keep your class as Private, and the best practice is to name your test class as your original Class or trigger Name + ‘Test’. Full Answer How … Read more
You have to start your class with @isTest annotation, then only Salesforce will consider this class as test class. Keep your class as Private, and the best practice is to name your test class as your original Class or trigger Name + ‘Test’. Methods of your test class have to be static, void and testMethod … Read more
You have to start your class with @isTest annotation, then only Salesforce will consider this class as test class. Keep your class as Private, and the best practice is to name your test class as your original Class or trigger Name + ‘Test’. Methods of your test class have to be static, void and testMethod … Read more
The key points while writing a test class are: You have to start your class with @isTest annotation, then only Salesforce will consider this class as test class. Keep your class as Private, and the best practice is to name your test class as your original Class or trigger Name + ‘Test’. Full Answer How … Read more