Forum Discussion
Elvorin
14 years agoContributor
AndyHughes wrote: Yeah I get your point, and you do have to just get the timings from the specific test step you want when drawing graphs, but to be honest the property transfer part is negligible in terms of time when compared to the request (most of the time it's nothing).
Not always true.
Some of my service operations responds in 4ms (best time scenario). Having a 2ms property transfer will skew it a lot. 
I really wish LoadUI had option to generate report just on soap call response time. Right now, I can configure graphs to show just that and get aggregated raw data from it. But summary still shows for the entire test case.
AndyHughes wrote:
Also, I keep it in there so I can see what actually happens if and when it fails in a load test.
Also another point to note which I didn't say before is that you will also have to have an assertion which looks for a 'failure' in order that should it happen, it's recorded as such. For example I use a 'Contains' assertion with the text 'fault'. Generally I find any SOAP request which goes wrong has the word 'fault' somewhere in the response.
I generally keep 2 assertions - SOAP response and Not a SOAP Fault.
