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
Esteban Rocha 3Esteban Rocha 3 

testing a trigger that calls a class

Hello,
I'm very new to APEX and I'm trying to test a trigger that calls a Class. 
Apex Class:
public class NewAccount {

@Future(callout=true)
public static void PassNewAccoundIDToQuest(string AccID) {

    try {
    String url = 'https://integration.csmlive.com/service.asmx/AddAccount';
    
    String DataToSend = '{';
    DataToSend = DataToSend + '"SFKey": "' + AccID + '"';
    DataToSend = DataToSend + '}';

    Http h = new Http();
    HttpRequest req = new HttpRequest();
        req.setTimeout(2000);
        
    req.setEndpoint(url);
    req.setMethod('POST');
    req.setHeader('Content-Type', 'application/json');
   
    req.setBody(DataToSend);
    
    h.send(req);
    
        } catch(System.CalloutException e) {
    //Exception handling goes here.... retry the call, whatever
}
    
    //HttpResponse res = 
}
    
}
Apex Trigger:
trigger TriggerAccount on Account (after insert) {
        for(Account a: Trigger.new){
        NewAccount.PassNewAccoundIDToQuest(a.Id);
         }

The test on Class is covered but I'm struggling to get the trigger covered. Any help, please? Thanks
 
SalesFORCE_enFORCErSalesFORCE_enFORCEr
Just insert an Account record in your test class.
Amit Chaudhary 8Amit Chaudhary 8
I will recommend you to start using trailhead to learn about test classes
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
3) http://amitsalesforce.blogspot.com/2015/06/best-practice-for-test-classes-sample.html

You write a test class for this the same way that you would any other:

- Set up some data for the Trigger to access (in this case it looks like Account object )
- Instantiate the Trigger- Insert Account record
- Verify the behaviour with asserts.

Please try below code
@isTest 
public class TriggerTestClass 
{
    static testMethod void testMethod1() 
	{
		Account testAccount = new Account();
		testAccount.Name='Test Account' ;
		insert testAccount;

    }
}



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
 
Esteban Rocha 3Esteban Rocha 3
Hello,
I have created this class and I have check that it is covered. after that I have addedd to outbound change set and I attemped to deploy it in our live org. But for some reason I have this error: Your organization's code coverage is 50%. You need at least 75% coverage to complete this deployment. Also, the following triggers have 0% code coverage. Each trigger must have at least 1% code coverage.
TriggerAccount


Apex Test Failures 
Class NameMethod NameError Messagetest_updatecontactrolecounttestcreateopptywithconditionandroleSystem.Exception: Assertion Failed 
Stack Trace: Class.test_updatecontactrolecount.testcreateopptywithconditionandrole: line 38, column 1

What I don´t understand is why it says I haven´t done the TriggerAccount coverage? And, Why in Apex Test Failures it shows that trigger if I haven´t included in the upload change set?

Any information I'll be appreciated.
Thanks!
SalesFORCE_enFORCErSalesFORCE_enFORCEr
It will check the coverage of the complete org which includes every class and trigger present in the change set or production. So, may be because of this failure, TriggerAccount was not covered. You need to fix this error and then try to deploy again.
Esteban Rocha 3Esteban Rocha 3
I did the test and I can see that the code coverage is 90% but when I still trying to do the deploy gives me the error. I really don't understand why