Service Virtualization

I'm trying to create a VS with Rest data protocol wherein by using different http methods, the response is directed to respective transactions. The issue is I'm unable to extract the query Parmeter (1234 viz the EmployeeId). I tried extracting via {{=request_EmployeeId}}, but it's not working, Can someone please help. 

POST http://localhost:9789/employee 

GET http://localhost:9789/employee/1234 

UPDATE http://localhost:9789/employee/1234 

DELETE http://localhost:9789/employee/1234 

you can use REST data protocol to extract URI parameter. In your scenario, add an operation in REST as 

GET /employee/{empId} and add empId as an argument in your vsi.

which version of DevTest are you using ?

Thanks Syed. I'm using 10.1

Let me try this.

I tried making empId as an argument. Seems am doing something wrong. No arguements are being captured here

{"id":0,"operation":"GET /employee/1003","arguments":{}}

Hope you are using REST DPH. I have attached the snapshot of VSM and VSI.

Exactly this is how I'm using it, but unable to capture the value of EmpId, please see the screenshots

Query Parameters will start after ? and are name value pairs.

While creating a VSI with rr pairs use

GET /employee?employeid=1234 

Thanks,

Venkatesh

True Venkatesh. However I'm trying the query parameters directly.

Validate that the request arguments that you want to use are marked as magic string in the request tab.

Everything marked as magic string can then be used in the response tab as {{request_<argumentName>}}

So in your case based on the last screenshot you provided the following should work {{request_URLPARAM0}}

Hey Danny. I'm not using any additional parameter as a part of payload, passing only one parameter as a part of URL. The strange part is it is giving the value in response when I use {{request_URLPARAM0}} in VSI, however trying out the same in VSM, isn't capturing the value

It is not straightfoward to see from the printscreens what you are doing where exactly. I’ll give some thoughts based on what I think is happening.

If {{request_URLPARAM0}} has a value within the .vsi, i.e. within the “Response Selection” step and this is due to magic stringing then that property request_URLPARAM0 will NOT exist in any step prior to the “Response Selection” step.

If you need to work with request_URLPARAM0 before the Response Selection step then you need to add a Request Data Copier DPH after your REST DPH and copy the arguments to “request_” properties.

Then in the scripted assertion: to my knowledge the script is not parsed before it is executed, so I don’t think that using {{request_URLPARAM0}} will work.

Within the script the property request_URLPARAM0 will exist and have a value if it exists in testExec. Wherever it is encountered as a variable the BeanShell will treat it as an existing variable. However, you are using it inside a fixed string and the characters {{request_URLPARAM0}} are just considered as part of a string.

It would do it as:

String query = “Select * from EmplyeeTest where EmployeeId = ‘” + request_URLPARAM0 + “’”;

testExec.setStateValue(“query”, query);

Cheers,

Danny