Contributions
Re: SOAPUI 4.0.0 BUG? Assertions appear as "UNKNOWN"
Dragica, What about the problem that I described in the earlier post: viewtopic.php?f=5&t=7969&p=23108#p23108 That is a static situation, i.e., just displaying what assertions were configured. I've been "assuming" that the two (the 1st/static/SOAPUI GUI one and the 2nd one where I get the "UNKNOWN" when running tests) were related, but they may not be. You may be correct about the 2nd one ("UNKNOWN" because there is no response), but shouldn't the 1st problem show something other than "UNKNOWN" in the SOAPUI GUI? As I posted in that post I linked above, the assertions look correct in the SOAPUI Project XML file. It's just that they appear in the GUI as "UNKNOWN" when you look after configuring the assertions. Jim13 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.7KViews0likes0CommentsRe: Cannot find 'Launch SOAP Monitor' option.
Hi, According to this: viewtopic.php?f=2&t=5059 it says in newer versons of soapUI Soap Monitor is renamed to Http Monitor. You can run this wizard by right click on Project name in navigator tree and select "Launch HTTP Monitor". Jim953Views0likes0CommentsRe: Property transfer in SOAPUI
Hi, If you launch testrunner and get the GUI, and then run it, and then scroll to the top of that, it will show you the testrunner.bat command line with the parameters that were used, including the endpoint URL. Also, according to this: http://learnsoapui.wordpress.com/2011/0 ... mand-line/ the "-e" parameter is for the endpoint. Jim547Views0likes0CommentsRe: Delay test step time (if parameterised) is not respected...
Hi, Sorry to jump into this thread, but I think that I've noticed that this problem is even happening when using property expansion in the Delay teststep per your documentation. In my case, I'm trying to us the Variance loadtest strategy, and want to limit the number of requests within each 60 second interval, so I have: Threads: 5 Variance: 0 (so constant 5 threads during interval) Interval: 60 seconds Limit: 120 seconds My test case has: - Groovy script step (sets up some properties) - SOAP request step (sends request) - Delay step (${=30000 + 30000*Math.random()}) It seems like even in this case, the Delay step is always taking only ~1000 msecs (= ~1 second), whereas I expected it to take 30-60 seconds, and I'm ending up with 200+ requests in the 120 second run, rather than something like 10-20 requests in 120 seconds. Any feedback on this, or way to make this work yet? Jim13 years agoPlace ReadyAPI QuestionsReadyAPI Questions1KViews0likes0CommentsSuggestion: Slightly improve/enhance "Variance" strategy
Hi, With the "Variance" strategy, you can specify an "Interval" (e.g., 60 secs) over which the number of threads used in the loadtest will varied. From my understanding (and testing), when the "Variance" strategy is used, SOAPUI will fire off requests in each of those threads as quickly as possible, so say we have: Interval: 60 secs Threads: 5 Variance: 1.0 The number of threads will, in a period of 60 secs, start a 5, go up to 10 (= 5 + 5), go down to 1, then begin ramping back up to 10, etc. However, since SOAPUI will fire off requests, one-after-the-other within each of those threads, there will be (variably) many requests during each "Interval". In SOAPUI 4.0.0, for "Limit", you can also specify "Total runs" or "Runs per thread", but this "Limit" setting only applies to the entire loadtest. The bottom line is that there is no way to specify or limit the number of requests per "Interval", either per thread or (total) per interval. The suggestion here is to add an additional setting to the "Variance" strategy, to limit the number of requests ("runs") during the specified "Interval". Ideally, if this could offer similar choices as with the "Limit", and give the choice of "Total runs per interval" or "Runs per thread within interval", with possibly empty setting ==> the current no-limit that would be great. Thanks, Jim13 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.4KViews0likes0CommentsRe: How to generate HTML report using SOAPUI free version?
Hi, When you're in the Launch window, under the Reports tab, there's a checkbox for "Junit" style report. I think that this is equivalent to a "-j" on the command line. When you have that checked, it outputs an XML file report. I guess that you can do some XSLT to convert that to HTML? Jim8.8KViews0likes0CommentsRe: How to generate HTML report using SOAPUI free version?
Hi, I don't know the answer to your question, but I just ran across this on the Pro area: viewtopic.php?f=2&t=6989 The thread has some command lines with "-FPDF", so maybe something like "-FHTML" would work for you? Pls post back! Jim8.8KViews0likes0CommentsRe: How to detect/handle testcase errors?
Hi, For the record, I think that I've found something that works, by putting some code in the testcase teardown script. The code I've used is based on the 6/28/2010 code that's posted on this thread: http://www.soapui.org/forum/viewtopic.php?f=2&t=3994 I think that I've also found a bug in the way that SOAPUI 4.0.0 is reporting assertions, which I've posted in the "Bugs" section, but the code I referenced seems to work ok if you check if all of the assertion.status is equal to the string "VALID". Jim550Views0likes0CommentsSOAPUI 4.0.0 BUG? Assertions appear as "UNKNOWN"
Hi, I posted this awhile ago in the general SOAPUI area, but haven't seen any responses. I don't know if anyone from Eviware support monitors this (Bugs) area, but see this post: viewtopic.php?f=5&t=7969&p=23108#p23108 As described in the above post, the first problem I encountered was just when SOAPUI displays the assertions that are configured (see attached PNG). However, since then, I've encountered an additional problem (bug?) that may also be related. This second problem/bug is because I was researching how to do what I was asking about in this other thread: viewtopic.php?f=5&t=8025 In researching how to solve the above, I found this other thread, that, at first, I thought would help solve the problem (trying to detect failed testcase): http://www.soapui.org/forum/viewtopic.php?f=2&t=3994 So, I tried to add the code in the 28 June 2010 post by Eviware support into my testcase teardown script, i.e.: def soapStep = testRunner.testCase.testSteps["soap step 1"] for( assertion in soapStep.assertionList ) { log.info "Assertion [" + assertion.label + "] has status [" + assertion.status + "]" for( e in assertion.errors ) log.info "-> Error [" + e.message + "]" } I then ran the testcase in a way that I knew would fail (host was down), and got: Thu Jul 21 18:59:24 EDT 2011:INFO:Assertion [SOAP Response] has status [UNKNOWN] Thu Jul 21 18:59:24 EDT 2011:INFO:-> Error [null/empty response] Thu Jul 21 18:59:24 EDT 2011:INFO:Assertion [Contains] has status [UNKNOWN] Thu Jul 21 18:59:24 EDT 2011:INFO:-> Error [null/empty response] As you can see from the above, it appears that the "UNKNOWN" is appearing not just when just displaying the assertions in the testcase, but also when trying to access the assertions in the assertionList for the testcase programmatically. So, it appears that both of these are possibly bugs in SOAPUI 4.0.0 (on Windows 32). Please advise. Thanks, Jim13 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.7KViews0likes2Comments