JimL
15 years agoContributor
SOAPUI 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.:
I then ran the testcase in a way that I knew would fail (host was down), and got:
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,
Jim
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,
Jim