maxfactor
Occasional Contributor
Joined 12 years ago
User Profile
User Widgets
Contributions
Failed to find MockResponse
I created my first ever very simple single mock response but when I ran it against my service I received the "Failed to find MockResponse" error. I found that I had to edit the project file to fix the incorrectly named default response ("Response 1"). See more details I posted at the end here:http://www.soapui.org/forum/viewtopic.php?f=5&t=6470&p=46641#p46641 No where on the SoapUI Mock Response GUI is there an option to reference the default mock name ("Response 1") that was defined in the project file. Is this a bug?4.2KViews0likes2CommentsRe: Failed to find Mock Response from SoapUI 3.6.1 w/QUERY_MATCH
I had a very very similar problem and this posted solution fixed it. I had just one simple mock response with no query match at all. I started the Mock response engine and then generated the request and received "Failed to find MockResponse" error from SoapUI. So I looked in my project file and I found: <con:defaultResponse>Response 1</con:defaultResponse><con:response name="MockResponse 2" MY Mock response is really named "MockResponse 2" and I have no idea where the default name "Response 1" came from but I changed the default to also be "MockResponse 2", re-ran the test and then the Mock response was generated. Thanks Bhlem! I am using SoapUI 2.5.2 Pro on a Windows 7 machine. This seems like a bug that has been around since the original post in 2011.3.3KViews0likes0CommentsSchedule component not dependable
I am trying to set up a simple LoadUI schedule to trigger my SoapUI runner (via a fixed rate generator) to generate triggers during all "typical" week day work hours, i.e. Monday - Friday, 8am to 5pm. But I find that when I rearrange the schedules, such as added the next day of the week, or changing the start time, or whatever, that seemingly randomly triggers are no longer generated after I press go. Further details: 1) All components are "enabled" (i.e. "on") 2) The duration is set to 9 hours for each schedule component (Indicated as seconds): "32400" 3) Start time is set to 8am on each component: "0 0 8" 4) Current TOD when this issue occurs is anywhere between 8am and 5pm - i.e. Within the schedule period. To fix this and get triggers again sometimes I have to do any one of the following things: 1) Close the project and reopen it (and not changing the test in any way) - now triggers will be generated again 2) -or- Pause 5 or 10 seconds before I press "go" again (and not changing the test in any way) 3) -or- Delete all other schedule components (or connectors) that are not "today", and then re-add them later Does anyone have any suggestion why this is so flaky? I have searched this forum and did not find anyone else with this issue. Thanks2.2KViews0likes1CommentRe: How to share Excel DataSource amoung Agents
As I discovered, and to be more specific about Renato's answer: If you use an Excel file as a data source and you want to run in LoadUI distributed mode then you must copy the Excel file to the same folder as the Agent executable (installation folder) on every machine where you want to run an agent. i.e. you do NOT copy the Excel to the ".../.loadui" folder and you do NOT copy it to a replicated SoapUI project folder tree (where the Excel had originally come from)936Views0likes0CommentsRe: How to share Excel DataSource amoung Agents
I should have also asked, where is "the expected location"? I think that means that I have to recreate an identical custom folder structure (note that it is NOT in /.soapui folder) on each agent machine and put the Excel file in that folder. Is that correct? Or does it belong in the ...../Agent/.bin folder?937Views0likes0CommentsRe: How to share Excel DataSource amoung Agents
Hi Renato. Yes, I do think that feature would be very useful to us. We want to run on dozens of machines and the Excel drives the entire process so it would be very inconvenient to have to constantly copy new versions of the Excel to these other machines. I would think that this feature would be very important in general to many users especially considering that distributed testing is such a huge selling feature of LoadUI. I would be pretty amazed if I am the first person to want such a feature. Perhaps in this scenario I should not be using an Excel? Is there some other text based data source mechanism (i.e. not a real 'database') that I should be using that would have an automatic distribution feature? Thanks.938Views0likes0CommentsRe: LoadUI 2.5.2
To solve the previous problem I first uninstalled LoadUI PRO v2.5.2. Then I started LoadUI PRO v2.5.1 (it was still installed) and tried to open the previous (v2.5.1) project files. The result was that the 2.5.1 GUI would only display a blank white screen. When I exited the program I got the error dialog box that says: “A problem occurred during startup and LoadUI needs to restart – Restart/Quit”. I tried restart and that did not help so next time I tried Quit and that did not help. i.e. still blank white screen on next attempt to run it. So I have tried uninstalling everything (i.e. free version, version 2.5.1, version 2.5.2 and LoadUI Agent) and rebooting and then only reinstalling 2.5.1 and still just a blank white GUI appears with that same error dialog box. To finally fix this I found that I had to also delete the folder C:\users\"name"\.loadui and then restart LoadUI 2.5.1 again and then v2.5.1 recreated the .loadui folder and it works again (i.e. no white screen) Make a copy of your .loadUI directory before you do this so you can reload your previous project files and other work.1.8KViews0likes0CommentsRe: LoadUI 2.5.2
I just installed LoadUI 2.5.2 and it can't seem to open my project files that were created in LoadUI 2.5.1. I can see my previous project file names in Version 2.5.2 but when I say "open" nothing happens and it just stays on the main LoadUI screen. Then when I exit LoadUI 2.5.2 it seems to become some sort of background task that can no longer be bought to the foreground as a GUI so I have to use task manager to kill that process and try again. I am working on Windows 7 professional SP1.1.8KViews0likes0Comments