mocking best practices -SOAP or REST Proxies

abiram8
Participant IV

Hi,

We are developing the Mocking proxy for Majorly SOAP and few REST backend without Target.

What are the best practices from Mocking perspective with No Target. like few

for either SOAP or REST

1. Having Spike and Threat protection in Mock ?

2. Validating the Header parameters for every request (applicable to POST not for GET)

3. Say for SOAP verify the SOAP Method to route to the required Mock target...

4. Do I require 1 proxy for each API (hence say if I had 10 Proxy then I need 10 Target Mock Proxy ?).

5. For Extract Policy validate the XPath (for SOAP request) plus validate with the SOAP Message Validation for namespace etc. What I hate about SOAP Message Validation is the WSDL need to be imported to Apigee, hence any change to WSDL will trigger again code or configuration changes (Do you agree ?)

6. "No-Target" mock returning the Javascipt object with required XML or JSON response.

7. Mock to handle error response if say Body or JSON is empty ?

Any other thoughts in terms of automation or design or implementation or maintenance for both SOAP and REST ("No-Target")mock.

Please advice want to see if I am missing ...

0 0 296
0 REPLIES 0