Service Virtualization

 View Only
Expand all | Collapse all

How to handle frequently changing request signatures?

Jump to Best Answer
  • 1.  How to handle frequently changing request signatures?

    Posted May 08, 2018 10:11 AM

    We have a virtual service in which we have 5 different responses based on an exact match.   For FirstName, LastName, and SSN we are looking for specific values to identify the response to serve and all other attribute values are set to Anything.  If there is no match we have the Meta response set with text that says No Match and an assertion to have it invoke the live service in this case.


    The problem is that the vendor of the service we are virtualizing frequently changes the request signature so when the development team runs a test, there are extra and/or changed attributes that are not part of the signature that was originally recorded.   This can change as frequently as weekly.  


    We'd prefer to not have to constantly be updating the VSI every time the signature changes.    All they care about is matching against FirstName, LastName, and SSN and don't care what the values of any other attributes are.


    We can't really change it to an Operation match because the response needs to be different based on what FirstName, LastName, and SSN are passed in.  


    Has anyone else encountered a situation like this and how did you handle it?

  • 2.  Re: How to handle frequently changing request signatures?
    Best Answer

    Posted May 08, 2018 10:36 AM

    You can use operation match and in match script editor add match script for the parameters you wanted to match like FirstName, LastName, and SSN and accordingly return true or false for the operation.


    This will first match the request with operation name and then verify match script and if true then only it will return the response.