Contributions
SOAPUI 5.2.1 Access to MockService properties via maven/pom.xml
Hello, I have been trying to find whether it is possible to access the MockService Custom Properties from maven/pom.xml when running a Mock Service. I currently access the <projectProperties> as follows in the pom.xml; <projectProperties> <projectProperty>testScriptPath=configuration/</projectProperty> <projectProperty>XLSConfigFile=TestSuite.xlsx</projectProperty> </projectProperties> Is there anyway to access the mockService properties in a similar way? If so, I cannot find anything online which helps with the naming convention. If it followed a logical route it would be; <mockServiceProperties> <mockServiceProperty>testScriptPath=configuration/</mockServiceProperty> <mockServiceProperty>XLSConfigFile=TestSuite260to265.xlsx</mockServiceProperty> </mockServiceProperties> Or are these accessed via <projectProperties> ? Can you please let me know if this is possible or not ... or a simple workaround would be to convert to projectProperties? Is there another method? Many Thanks Ed Crane716Views0likes0CommentsRe: SoapUI Mock responds slowly to initial message
Rupert, Looks like you might have the solution for a WAR file. As I mentioned in the first post, I'm running from Maven using the SOAPUI plugin. There maybe a similar issue with the plugin vs the WAR. But how to configure the SOAPUI maven plugin to do the same as you have suggested in your last post? I am going to try to start the mock service via a "load script" in the project file to see if that gets the mock started when the project is loaded, rather than when the first message is received. I'm not sure, but potentially the SOAPUI maven plugin starts the mock service anyway? I'll let you know how I get on and if you can help with the setup of the maven plugin to get the same behaviour as the WAR that would be much appreciated. Many thanks Ed1.7KViews0likes0CommentsRe: SoapUI Mock responds slowly to initial message
Rupert, Many thanks for your response. I had already experimented with adding a pre-test to "warm up" SOAPUI. This of course works. But I was searching for a solution which didn't require adding this to all of the tests. I think I have no real issue with SOAPUI taking some extra time on receiving the first message. I think its the amount of time taken that seems excessive. In some cases approx 5 seconds. Which to me suggests SOAPUI is waiting for something? Rather than actually processing for 3-5 seconds? I had started to investigate Proxies as I read somewhere that if the SOAPUI proxy was set to automatic then potentially SOAPUI might do some exploration before deciding there was no proxy. So I was trying to disable proxy in the pom.xml, just to see if this has any effect with the following lines; <soapuiProperties> <property> <name>ProxySettings.ENABLE_PROXY</name> <value>false</value> </property> </soapuiProperties> This seems to have no effect, but this could be due to, proxies not being the issue or the addition above not being correct. I struggled to find an example of this. But as SOAPUI allows you to put any name into the above XML there is no real way for me to know whether I am changing the right existing SOAPUI setting or creating a new one. Do you know what the correct name would be in this case? I'd just like to eliminate this from my investigation. If this doesn't work, potentially we will just have to elongate the timers for testing, as we can still test functionality this way as I have control of both ends (JMETER>>DUT>>>SOAPUImock). For performance we will have to "warm up" SOAPUI. Many thanks for your help so far.1.7KViews0likes2CommentsSoapUI Mock responds slowly to initial message
Dear SmartBear, I have trawled the internet looking for anyone who might have the same issue as me , but I can find nothing. So I'm hoping that you can help me. I'm running a SOAPUI Mock service via jenkins using the maven plugin ( <artifactId>maven-soapui-extension-plugin</artifactId> <version>4.6.4.2</version>) on Linux. The issue I see is that the first message processed by SOAPUI Mock seems to take much longer than the subsequent messages. All messages are processed via the same Groovy script. The groovy script contains proprietary info so I cannot send it to you. But each message is roughly the same and I cannot see why the first would be delayed. The groovy script takes the following steps; open a XLS to retrieve the request/response message data for this test case Validate the XLSrequest message data against the message received Build the response based upon theXLSresponsemessage data Send the response This see what I see in the log; Handled request 1; [request] with [response] in [5304ms] at [2017-03-02 16:10:01.029] Handled request 2; [request] with [response] in [482ms] at [2017-03-02 16:10:06.777] Handled request 3; [request] with [response] in [520ms] at [2017-03-02 16:10:07.711] As you can see the first message takes much longer and I'm searching for the reason behind this. Could it be some kind of initialisation step i.e. thread allocation/memory allocation? I've not been using SOAPUI for a long period of time, so I apologise if there is already a published answer to this question Many Thanks Ed1.8KViews0likes4Comments