Mock a REST Service using SOAPUI with JSON response

Sometimes, backend service is not ready to receive requests and we may want to mock the service. In such cases we have sample request and response but integration cannot be tested unless we actually hit the service. Mocking the services is a good option to continue and progress.

In this tutorial, we will use SOAP UI to mock a REST service with POST method and JSON response(static in nature). This is the basic tutorial to configure static response with no request validation. We can use the SOAP UI to test the created mock service also before, we try to hit from any Integration service.

Sample URL(for actual service): http://localhost:8080/api/test
Sample JSON Response:
{
"name": "John",
"age": 30,
"car": null,
"regitered": true
}

Steps:

1. Open SOAP UI and click on REST to create a New REST Project. 
2. Provide the url for the api you want to create a mock service.
3. Once the project is created, right click on host name(http://locatlhost:8080) under REST Project 1 and then click on Generate REST Mock Service.
4. Specify the name for mock service and click on OK.
5. A window will open showing that mock service GET /api/test has been started at port 8089.
6. Click on stop button to stop the mock service. Click on /api/test under REST MockService 1. Change method from GET to POST.
7. Mock response is specified as Response1 which was automatically created. Double click Response 1 from this window or navigator window. 
8. Keep HTTP Status Code to be 200 - OK, if your back end application sends the status code 200 else change to the code which backend application sends. Update the sample response under content window editor. Specify media type to application/json.
9. Start the mock service. You will see the mock service POST /api/test is started at port 8089.
10. To test this service, open the request under REST Project 1. Update the hostname:port with the value for mock service. Here in this case will be http://localhost:8089. Click on run.
You will see the response is received. And also we can see in logs that request triggered and is successful.


Note: In SOAP UI, we can also configure dynamic response using groovy script.



-

Comments

Post a Comment

Popular posts from this blog

DateTime formatting using xp20:format-dateTime ()

xs:dateTime Format In XML, we generally use xs:dateTime(xs:xmlns="http://www.w3.org/2001/XMLSchema") data type to store date time data. The generic representation of date time, that is supported by xs:dateTime in xml: YYYY-MM-DDThh:mm:ss[.SSS][Z|(+|-)hh:mm] Example :  2019-09-11T10:16:31.943+05:30 Code Description Example YYYY represents a 4-digit year 2019 MM represents a 2-digit month 09 DD represents 2-digit date 11 hh represents 2-digit hours 10 mm represents minutes in 2-digits 16 ss represents seconds in 2-digits 31 SSS represents milliseconds 943 T represents time separator T Z represents UTC time zone or 0 time zone offset (+|-)hh:mm represents time zone offset +5:30 Few more valid examples : 2019-09-11T21:32:52, 2019-09-11T21:32:52+02:
Read more

Create Delimited String from XML Nodes and Vice Versa in SOA 12c

A delimited string is a string representation of data separated by a delimiter(e.g. ","). A simple representation of the delimited string will look like. Delimited String Examples Sample-1-- Delimiter as ","        Value1,Value2,Value3   Sample-2-- Delimiter as "|"        Value1|Value2|Value3 If we want to represent the above set of delimited values in the form of an XML document under some root and parent tag. The representation will look like this. XML Example <root xmlns="http://test.com/sample/xml">   <Values>     <value>Value1</value>     <value>Value2</value>     <value>Value3</value>   </Values> </root> Sometimes we may need to convert values coming in delimited string to an xml document or vice versa. Since delimited string is similar to csv format. We can create
Read more

Import and Export MDS artifacts in SOA 12c

Image
Oracle SOA-MDS (Metadata Store) repository can be used to access artifacts that can be shared among various SOA composites. For example, we have one common schema for a business fault that is consumed by various applications. Instead of having a localized copy of that schema file in each SOA composite, we can have it in a centralized repository (SOA-MDS). Another benefit of using SOA-MDS is that we can change the file at runtime and need not redeploy the complete code. While developing SOA composites, we use SOA design-time repository, later these changes can be synced to the SOA servers. In this article, we will discuss 2 ways to sync the artifacts available in the SOA design-time repository and the SOA servers. Establishing the connection to SOA-MDS in Jdeveloper. Using SOA em console or Fusion Middleware control console. Moving a file between SOA composite to SOA design-time MDS repository Let's assume, we created a businessFault.xsd which wi
Read more