Service Testing
Service Testing is a light-weight module. You can use it to test vConnect services. By testing a vConnect service, you make sure that the service is up and working as expected. The vConnect service means that the service is configured and published in the vConnect module.
For a complete service configuration process on the vConnect portal, you configure an API and then create a service. A newly created service works as a container. Thus, you add the configured API to the service.
If you want to use the service as a wrapper service, you can add more than one API to the service. For instance, you can add multiple APIs to the service. Under the service container, these orchestrated APIs perform the intended functions sequentially or in a parallel manner.
After you add an API to the service, you publish the service in the vConnect module. That is how this module allows you to test services that are published in the vConnect module.
To test a vConnect service:
- In the App Ops module, see the Service Testing page in the middle panel.
- On the Service Testing page, click in the Search Service box, and a list of services opens.
- This list displays all services that are published and deployed in the vConnect module.
- In the list, select a service (for example, AUTH) that you want to test.
- After you select the service, the Service Testing page loads the API request’s body in JSON format.
- The Request Body box displays the API request in JSON format with the parameters’ default value.
- In the API request’s body, you can change the default values of parameters.
- After you apply the required changes to the API’s request body, click Test, and the Service Testing page executes the selected API and then displays results.
When you test an API, the Service Testing page may show unexpected results or throw an error as a result of one of the following reasons:
- The service is not synced
- Issue occurs at the backend layer
- If a required body parameter is missing or parameter’s mandatory value is missing