[SalesForce] How to test access token for HTTP callouts

I have an access token for my HTTP callouts. How can I test it if I wanna use Static Resource? But I can also use the HttpCalloutMock Interface. it doesn't matter

My access token is in custom object. I just call fields in the method.

public static String accessToken(){
//Error is here:
    Token__c tok = [SELECT ConsumerKey__c, ClientSecret__c, Username__c, Password__c, SecurityToken__c
                            FROM Token__c 
                            WHERE Name = 'OurToken'];  
    String consumerKey = tok.ConsumerKey__c;
    String consumerSecret = tok.ClientSecret__c;
    String username = tok.Username__c;
    String password = tok.Password__c + tok.SecurityToken__c;
    String request = 'grant_type=password&client_id=' + consumerKey +'&client_secret=' + consumerSecret +
                     '&username=' + username + '&password='+password;
    return request;
}

I have my test, but it's write me an Error:

System.QueryException: List has no rows for assignment to SObject

@isTest
static void testCallout() {
    Test.setMock(HttpCalloutMock.class, new MockHttpResponseGenerator());

    Http ourHttp = new Http();
    String requestBody = Callout.accessToken();  //error is here
    HttpRequest ourRequest = new HttpRequest();
    ourRequest.setBody(requestBody);
    ourRequest.setMethod('POST');
    ourRequest.setEndpoint(System.Label.URL + '/services/oauth2/token');
    HttpResponse response2 = ourHttp.send(ourRequest);
}

Best Answer

in tests methods without seeAllData = true property of annotation @isTest only data created in test method and in methods annotated with @testSetup is visible. this is a copcept of test data isolation

you have to create tour Token__c record before invoking Callout.accessTokenBody(); in test.

@isTest
static void testCallout() {
    Test.setMock(HttpCalloutMock.class, new MockHttpResponseGenerator());
    insert new Token__c(
        Name = 'OurToken',
        .....
        );
    Http ourHttp = new Http();
    String requestBody = Callout.accessToken();  //error is here
    HttpRequest ourRequest = new HttpRequest();
    ourRequest.setBody(requestBody);
    ourRequest.setMethod('POST');
    ourRequest.setEndpoint(System.Label.URL + '/services/oauth2/token');
    HttpResponse response2 = ourHttp.send(ourRequest);
}

Related Solutions

[SalesForce] Need help with Test Class for HTTP Callout

The MOCKHTTP class ss returning EXACTLY what the regular Endpoint would return.

Since your class ClinicalStudySetupExtension.callRestEndPoint() is PRIVATE Method of ClinicalStudySetupExtension you simply need to instantiate your controller as it will call the method which in turn will make the callout thus getting a response based on the HTTPMOCK class and process based on the controller

ClinicalStudySetupExtension con = New ClinicalStudySetupExtension(New ApexPages.StandardController(YOUROBJECT));

The point of the HTTPMOCK is to return an HTTPResponse just like an endpoint would.

Also, no need for a system assert in your HTTP Mock Class. You are going to construct and return different responses based on the request parameters sent to endpoint by whatever class / method calls it. You can use the same HTTPMOCK class for several methods from a related class that may use PUT, GET, POST, etc or different endpoints and wrap them all up in one HTPMOCK class to generate the appropriate response.

Once you instantiate the controller assert the value of 'this.studyJson' for the value of {"study":{"moleculeDescription":"RONTALIZUMAB","protocolTitle":"IMM","protocolNumber":"GA00806","studyName":"Interferon alpha in SLE Phase II LCM Option","therapeuticArea":"INFLAMMATORY,AUTOIMMUNE&BONE","startDate":"2009-03-25","endDate":"2013-08-22"}} since this is what your controller sets based on the response.

Clear as mud?

[SalesForce] Test class for http callouts

You're really close with the code you have. The mistake is that you're testing against the mock class after the Test.setMock instead of testing against your non-test class's wrapper method and callout method. The Test.setMock method tells the test framework to swap out the response data from your non-test class's callout.

You'll also need to remove the logic check you have in place in your callout method so it can properly populate the HttpResponse object.

public static void callWSGetIdObject(Object__c Obj ){
    // ...
              // remove this check, the test framework will swap the response data
                    if(!system.Test.isRunningTest()){
                    res = http.send(req);
                    }
    // ...
}

I can see you modeled this off of the documentation for the Test.setMock. The problem with their example is that their non-test method responds back with the HttpResponse object. That example is very basic since the method only returns the HttpResponse directly, but given the context of the feature, it is slightly tricky and confuses the issue.

https://www.salesforce.com/us/developer/docs/apexcode/Content/apex_classes_restful_http_testing_httpcalloutmock.htm

An easier example to think of is a REST service taking in 1 integer, and returning two integers, and your non-test method that performs the callout also processes it like most test accessible(public/global) callout methods tend to do. Like all other tests your job is to make sure the method itself (and its wrapper @future) function as expected when given the right inputs, and that their output is valid. Test.setMock is only used so you can populate the response data in the non-test method with expected data (also because test can't run callout). Ideally you'd write a few versions of this test with varying values and callout responses including a test that returned invalid responses or exception catching states (e.g. blank response, XML with no nodes except parent, missing an XML node that is critical).

[[example coming later, it's super late here]]

Best Answer

Related Solutions

[SalesForce] Need help with Test Class for HTTP Callout

[SalesForce] Test class for http callouts

Related Topic