Forum Discussion

Ashley's avatar
Ashley
Occasional Contributor
15 years ago

Working soapUI testcase has many assertion errors in loadUI

I have quite a large functional testcase that works correctly in soapUI without error. I can run clones of the testcase in parallel without issue within soapui and furthermore I can use the loadtest feature within soapUI and everything works correctly.

However when i transfer my testcase to loadUI and run it I get many assertion errors, below is the output from the log:

"0","[[Check for existance of [smf:xxx]] XPathContains comparison failed, expecting [true], actual was [false]]","1291303351462","Cancelling due to failed test step"
"1","[[Check for existance of [smf:xxx]] XPathContains comparison failed, expecting [true], actual was [false]]","1291303353028","Cancelling due to failed test step"
"2","[[Match content of [xxx]] XPathContains comparison failed, expecting [true], actual was [false]]","1291303353469","Cancelling due to failed test step"
"4","[[Check for existance of [smfwsdl:xxx]] XPathContains comparison failed, expecting [false], actual was [true]]","1291303355476","Cancelling due to failed test step"
"5","[[Check for existance of [smf:xxx]] XPathContains comparison failed, expecting [true], actual was [false]]","1291303356647","Cancelling due to failed test step"
"6","[[Match content of [@int]] XPathContains comparison failed, expecting [1], actual was [2]]","1291303357480","Cancelling due to failed test step"
"7","[[Match content of [@int]] XPathContains comparison failed, expecting [1], actual was [0]]","1291303358499","Cancelling due to failed test step"
"8","[[Check for existance of [xxx]] XPathContains comparison failed, expecting [true], actual was [false]]","1291303359468","Cancelling due to failed test step"
"9","[[Check for existance of [smf:xxx]] XPathContains comparison failed, expecting [true], actual was [false]]","1291303360488","Cancelling due to failed test step"
"10","[[Match content of [@int]] XPathContains comparison failed, expecting [1], actual was [2]]","1291303361449","Cancelling due to failed test step"
"11","[[Match content of [@int]] XPathContains comparison failed, expecting [1], actual was [0]]","1291303362494","Cancelling due to failed test step"
"12","[[Match content of [@int]] XPathContains comparison failed, expecting [1], actual was [0]]","1291303363450","Cancelling due to failed test step"
"14","[[Match content of [xxx]] XPathContains comparison failed, expecting [true], actual was [false]]","1291303365450","Cancelling due to failed test step"
"15","[[Match content of [@int]] XPathContains comparison failed, expecting [1], actual was [2]]","1291303366511","Cancelling due to failed test step"
"17","[[Check for existance of [smf:xxx]] XPathContains comparison failed, expecting [true], actual was [false]]","1291303368471","Cancelling due to failed test step"
"16","[[Check for existance of [smfwsdl:xxx]] XPathContains comparison failed, expecting [false], actual was [true]]","1291303367458","Cancelling due to failed test step"
"18","[[Match content of [@int]] XPathContains comparison failed, expecting [1], actual was [2]]","1291303369432","Cancelling due to failed test step"
"20","[[Check for existance of [smf:id]] XPathContains comparison failed, expecting [true], actual was [false]]","1291303371506","Cancelling due to failed test step"


As well as these 'content' assertions I have one that just checks that a soap request receives a response, this is the first assertion for each request and they all pass (no response assertion errors in log).

The assumption that I currently have is that the soap requests are being sent and a response is being received but the response received in loadUI is different to that of soapUI obviously this could be because the request is different too. By different I mean maybe some of the content used in property transfers hasn't been generated/transferred correctly.

Is there anyway of getting a decent debug output from loadUI? I want to know what requests have been sent and what responses I've gotten so I can work out where its failing and fix it!

Or is this a common error and does anyone have a solution?

Any help would be greatly appreciated, cheers!

2 Replies

  • Ashley's avatar
    Ashley
    Occasional Contributor
    I am quite keen to resolve this issue, it is my understanding that teatcases from soapui should be directly portable to loadui and my working one in soapui fails as above in loadui. If I have posted In the wrong section please move it. Thanks in advance for any help you can give me.
  • Hi,

    You are definitely right, soapUI TestCases should be portable to loadUI; we are trying to reproduce this internally.. I'll let you know of our progress!

    regards,

    /Ole
    eviware.com