I'm trying to use Property Transfers in order to export a parameter from a service response and have it display in maybe a table log in LoadUI. I have the property transfer working in the sense that I have got it to store the response in a property I have created. What I can't do is get that property to display anywhere in LoadUI with the contents of the response. If I can do this then I can prove that each request has been successful (or not). I then wouldn't necessarily need an assertion as I could see the whole response each time. Or better still a specific part of it.I've already tried clicking "Add test case properties to results message' it doesn't do anything. I have a table log off each node of the soapui runner and there is no output in any of them that relates to the response message. Also in the settings dialogue of the soap ui runner the properties tab doesn't contain the property I am trying to save despite having "Add test case properties to results message" ticked.Also, each request is failing in loadui due to an assertion in soapui pro which checks for the word 'fault' in the response. However when I run the same test in SOAPUI Pro, it passes fine every time?Really need help with this. I'm soooo close.

I assuming I must be doing something wrong here as I've now tried an XPath assertion which also passes in SOAPUI Pro, but fails every time in LOADUI.

I think I'm closing in on the answer now. I've found that after I created a new project in the latest version of SOAPUI Pro (Don't know if this is significant) that the test runs via loadui successfully, once. It then starts failing again. I though this may be due to the fact that although I think I'm using different data in each request from an excel file, it's actually failing to read the next row in. So I tested the theory using a Grid of 4-5 values. This worked fine via LoadUI. So for some reason the same value is being accessed each time when I use the excel data source, even though I have the following settings for the data sourceAny help would be appreciated.Also I still can't get the actual response output from any of the table logs. If I can nail these issues then I'm well away!

Just wanted to say that I'm looking into this right now. This topic hasn't been forgotten! Henrik @ SmartBear

At the moment I'm getting round this issue by using the grid option for the data source. (Im not sure how many rows I can paste into a grid.)But I could still do with the excel option working. And when a test fails it would be useful to know specifically which request went wrong so to be able to get the actual request out in the table log and the responses would be useful rather than the fact that there was a failure.I can use an assertion to check for a specific string in the response which is unique to a successful request in order to convince myself that it worked ok, it's just when it doesn't that the information on what went wrong and which one, would be useful.

Assertion fails in loadui but not in soapui

13 Replies

AndyHughes
Regular Contributor
14 years ago
I assuming I must be doing something wrong here as I've now tried an XPath assertion which also passes in SOAPUI Pro, but fails every time in LOADUI.
AndyHughes
Regular Contributor
14 years ago
I think I'm closing in on the answer now. I've found that after I created a new project in the latest version of SOAPUI Pro (Don't know if this is significant) that the test runs via loadui successfully, once. It then starts failing again. I though this may be due to the fact that although I think I'm using different data in each request from an excel file, it's actually failing to read the next row in. So I tested the theory using a Grid of 4-5 values. This worked fine via LoadUI. So for some reason the same value is being accessed each time when I use the excel data source, even though I have the following settings for the data source

Any help would be appreciated.

Also I still can't get the actual response output from any of the table logs. If I can nail these issues then I'm well away!
SmartBear_Suppo
Alumni
14 years ago
Just wanted to say that I'm looking into this right now. This topic hasn't been forgotten!

Henrik @ SmartBear
AndyHughes
Regular Contributor
14 years ago
Thanks Henrik. Appreciated.
AndyHughes
Regular Contributor
14 years ago
At the moment I'm getting round this issue by using the grid option for the data source. (Im not sure how many rows I can paste into a grid.)
But I could still do with the excel option working. And when a test fails it would be useful to know specifically which request went wrong so to be able to get the actual request out in the table log and the responses would be useful rather than the fact that there was a failure.

I can use an assertion to check for a specific string in the response which is unique to a successful request in order to convince myself that it worked ok, it's just when it doesn't that the information on what went wrong and which one, would be useful.
SmartBear_Suppo
Alumni
14 years ago
Hi,

I am looking into this issue now. I was wondering if you are able
to share your loadui and soapui project as well as excel data source
so I can check them? If you are not able to share your projects
it would be great if you could create sample projects that do
the very same thing as your original projects.

Thanks.

/Predrag
SmartBear Software
AndyHughes
Regular Contributor
14 years ago
Hi,

Afraid I can't share the projects but I can share these screen shots. The tests aren't that complex to be honest. And the excel data source really is just a list of hexadecimal values in one column like this:

Despite having test case properties in result message ticked, there is nothing in the properties tab of this same box and I can't find any responses output anywhere.

Thanks
SmartBear_Suppo
Alumni
14 years ago
Hi,

Do you have a property on a TestCase level (not the properties teststep) defined to which
you are transferring responses? The option 'Add TestCase Properties to Result Message' is related
to properties defined in a testcase itself and not Properties teststep. So, what you have to do
is to define property on the testcase level and change you property transfer to point to it.
After this your response should appear in the TableLog connected to the first node from the left.

Does this make sense?

(I'm continuing with DataSource issue)

/Predrag
AndyHughes
Regular Contributor
14 years ago
Yeah that makes sense thanks. I was doing it at test step level.

Would be good if the excel thing was fixed - thanks for your work on this.
SmartBear_Suppo
Alumni
14 years ago
We have looked at this now together with soapUI devs. We will probably start fixing it on Monday.

Have a nice weekend!

/Henrik