{"id":869,"date":"2015-02-02T05:10:10","date_gmt":"2015-02-02T05:10:10","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/salesforce\/?p=869"},"modified":"2018-10-08T05:47:28","modified_gmt":"2018-10-08T05:47:28","slug":"testing-web-service-callouts","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/salesforce\/2015\/02\/02\/testing-web-service-callouts\/","title":{"rendered":"Testing Web Service Callouts"},"content":{"rendered":"

Earlier we had generated code from WSDL as an Apex class containing the methods that can be invoked for calling the Web service. As we are aware that to deploy or package this Apex class, 75% of the code must have test coverage, including the methods in the generated class.<\/p>\n

Real-time, bi-directional, multi-company – Sage ERP Integration with Salesforce<\/strong><\/a>
\n<\/strong><\/strong><\/p>\n

While writing the test coverage we came to know that by default, test methods don\u2019t support Web service callouts and tests that perform Web service callouts are skipped. To avoid tests from being skipped Apex provides the built-in WebServiceMock interface and the Test.setMock method that one can use to receive fake responses in a test method.<\/p>\n

When we generate an Apex class from a WSDL, the methods call WebServiceCallout.invoke to perform the callout to the external web service. Now while testing we need to instruct the Apex runtime to generate a fake response whenever WebServiceCallout.invoke is called.<\/p>\n

For this, we implement the WebServiceMock interface and specify a fake response that the Apex runtime should send. Following is a simple example that will give an idea on how we can test the web service callouts-<\/p>\n

    \n
  1. Create the class which implements WebServiceMock interface. This implements the doInvoke method, which returns the response we want. In this case, the response element of the auto-generated class is created and assigned a value.\u00a0\"callout1\"<\/a><\/li>\n
  2. Following is the method that callouts the Web service.\"callout2\"<\/a><\/li>\n
  3. Below is the test class which tests web service callout in the mock callout mode. It calls the callEchoString method of above class and verifies that a mock response is received.
    \n    \"callout3\"<\/a><\/li>\n<\/ol>\n

    About Us<\/strong><\/span>
    \n    Greytrix<\/a>\u00a0as a Salesforce Product development partner offers a wide variety of integration products and services to the end users as well as to the Partners across the globe. We offers Consultation, Configuration, Training and support services in out-of-the-box functionality as well as customizations to incorporate custom business rules and functionalities that requires apex code incorporation into the Salesforce platform.<\/p>\n

    Greytrix<\/a>\u00a0has some unique solutions for Cloud CRM such as Salesforce integration with\u00a0Sage Enterprise Management (Sage X3<\/a>),\u00a0Sage Intacct, Sage 100\u00a0<\/a>and\u00a0Sage 300 (Sage Accpac)<\/a>. We also offer best-in-class Cloud CRM\u00a0Salesforce customization and development services<\/a> along with services such as Salesforce Data Migration<\/a>, Integrated App development<\/a>, Custom App development<\/a> and Technical Support<\/a> to business partners and end users.<\/p>\n

    Greytrix GUMU™ integration for Sage ERP \u2013 Salesforce is a 5-star app listed on Salesforce AppExchange<\/a>.<\/p>\n

    For more information, please contact us at\u00a0salesforce@greytrix.com<\/a>. We will be glad to assist you.<\/p>\n

    Related Posts<\/span><\/strong><\/p>\n