Forum Discussion

Contributor

10 years ago

simple scripting in a Mock Service - no longer works

I have a problem with Mock Service scripting. It used to work. Now it doesn't. In a previous project (about a year ago) I used simple scripting in a soapUI Mock Service. I had several responses ...

custom sequence

Mock Response

jamescollett
10 years ago
I have found a solution. I have moved on to a new SoapUI project (a SOAP project, this time, not REST) and just for the sake of punishing myself I tried again to construct a custom sequence. I have taken bits of a coupe of the kind responses and amended them based on my observations and have come up with the following.

I realised that the script log was showing the values of my list items with the square brackets around them. It occurred to me that a statement like this:-

myRespList = ["Response_2","Response_1"]
- must do a bit more than just insert the two strings "Response_2" and "Response_1" to a list; it must be adding the square brackets around the words first. No idea why.

I re-named my methods to include the square brackets and suddenly the thing is working.

Here are the details:-

My Responses in the method are as follows:-

[Response_Template]
[Response_1]
[Response_2]

My code (heaviliy influenced by previous contributors) is as follows.

// get the list from the context def myRespList = context.myRespList // if list is null or empty reinitalize it if (!myRespList || !myRespList?.size) { log.info "--> Refreshing the list" // list in the desired output order myRespList = ["Response_2","Response_1"] } // take the first element from the list def myResp = myRespList.take(1) // update the context with the list without this element context.myRespList = myRespList.drop(1) // return the response log.info "--> Response is: " + myResp return myResp;
The output in the script is like this:-

Fri Oct 09 18:34:47 BST 2015:INFO:--> Refreshing the list
Fri Oct 09 18:34:47 BST 2015:INFO:--> Response is: [Response_2]
Fri Oct 09 18:34:50 BST 2015:INFO:--> Response is: [Response_1]
Fri Oct 09 18:34:51 BST 2015:INFO:--> Refreshing the list
Fri Oct 09 18:34:51 BST 2015:INFO:--> Response is: [Response_2]
Fri Oct 09 18:34:51 BST 2015:INFO:--> Response is: [Response_1]
Fri Oct 09 18:34:52 BST 2015:INFO:--> Refreshing the list
Fri Oct 09 18:34:52 BST 2015:INFO:--> Response is: [Response_2]
The SOAP XML Responses from the mock service are swicthing betwen Response_2 and Response_1 as desired.

jamescollett

Contributor

Really, does no-one have any wisdom to offer on this one? This sort of mock service setup has to be in the category of Mock Service Scripting 101 and yet no advice on how to make it work?

Sigh.

jamescollett

Contributor

10 years ago

I am re-visiting this problem once again. This time I have moved up to SoapUI 5.2.0. And this time I am modelling a RESTful web service instead of a SOAP web service.

Again I should like to define a specific order of responses from the set of responses that I have created for a method. If I use the SEQUENCE option, the responses will come out in the order in which they were added. But I do not want this. Suppose I want to just return the 4th and the 5th response and for now ignore the 1st, 2nd and 3rd?

The tool does not allow me to arbitrarily move the responses as they are listed. I do not wish to delete any of them. I should like to write a script that says, "Send back the 4th response, then the 5th, regardless of the contents of the incoming request."

Please, anyone?

rupert_anderson
Valued Contributor
10 years ago
Hi,

To do what you need and many other dynamic responses, I would use a Dispatch type of SCRIPT. Please see example in the screen shot:

Basically, the script allows you to conditionally return different responses e.g. you could do return "response 4" or whatever you need.

Assuming you're happy to do some simple Groovy script, does this make sense? If you're not happy to, then your options are limited to the sequence option.

Hope this helps,

Cheers,

Rupert
- jamescollett
  Contributor
  10 years ago
  Thanks, Rupert, for your response.
  
  Unfortunately, that is not what I am attempting to do. Your example addresses the very reasoble desire to base the response on the contents of the request. So for example, if the <userID> is "tomthumb", generate "Response 2", else generate "Response 1".
  
  My needs are so much simpler!
  
  The request in this case is going to be the same each time, but the response will change over time, and that is what I wish to simulate - by choosing a subset of my already defined responses and sending them back in a custom order of my choosing. I tried to highlight this in my second post in the thread.
  
  It seems that all sorts of wonderfully complex things are possible in SoapUI but not this trivial task. Ironically, it used to work. On a previous project I was able to specify in a script section somethuing like the following:-
  
  return "Response 5" return "Response 4" return "Response 7"
  Only these three reponses were returned, and in the obvious order specified, not in the order in which they were created. Other responses that I had defined (but did not wish to use on this occasion) were ignored and I did not have to delete them.
  
  When I came back to re-use my SoapUI project after making some code changes, this feature no longer worked and I could not track down the cause, except maybe a change in version of SoapUI that I was using.
  
  This problem applies to scripting responses to both SOAP web services and RESTful web services.
  
  The only solution I have to the problem is to delete the responses, create exactly the ones I want to use in this case, and select the SEQUENCE option. But that sucks. It sucks golf balls up a garden hose.
  - nmrao
    Champion Level 3
    10 years ago
    "I have a problem with Mock Service scripting. It used to work. Now it doesn't."
    
    -- quoting from the original query.
    
    Would you please post the script that used to work? and also post the error that you see in the log, may be that will help to narrow down the core of the issue? Also list the details of your environment changes between working, not working which I think will help you also to pin point the issue