Test Execution

The Test Execution option lets you test your Decision Service by making a REST or SOAP request to it. When you select the Test Execution, you choose a server where the Decision Service is deployed, whether to make a REST or SOAP request, and then locate a JSON or XML file for the payload of the request.

To execute a test against a selected deployment of the current Decision Service :

1. Click Server to select a server that has the Decision Service deployed.
2. In the Choose Request File area, click Choose File, then locate and open an XML or JSON request appropriate for the Decision Service. The Request area shows the request text.
   Note: You could choose to paste or type in the request.
   Note: The entry will be evaluated as to whether it is valid, and, if invalid, highlights the Request area, as illustrated:

   
   
   

3. Choose its Request Type to set the type for the selected file, where:
   • REST/JSON expects well-formed JSON as you may have exported from a testsheet, as illustrated in Export a Testsheet to JSON .
   • REST/NativeJSON expects the request to adhere to simplified format of Native JSON.
   • REST/XML expects well-formed XML.
   • SOAP/XML expects well-formed XML in a SOAP wrapper.
   Note: XML and SOAP requests require the decision service name to be the name of the Decision Service in the Web Console. If you exported a request from a Ruletest, you can edit the request or set it as you work by selecting the Decision Service name, and then revising the request header by replacing "InsertDecisionServiceName" with, in this case, "Grocery":

   
   
   

   • REST/JSON expects well-formed JSON.
   • REST/NativeJSON expects the request to adhere to simplified format of Native JSON.
4. Click Execute.

The request executes, and then adds the Response text, as shown for native JSON in its simplest form:

As you can see, the output for a nativeJSON request is formatted as nativeJSON.