Can someone explain the following differences to me please!
I have several tests setup for LoadUI that I am trying to figure out. I do not have a LoadUI license yet, but am dabbling around using the free version for now to determine whether to buy it or not. Currently I have a test setup for 50 Users with a Request Interval of 5 seconds. The Soap Project has assertions setup on it and I have 2 Assertions setup for the LoadUI test, one for Time Taken (Max) being between 1000 and 4500 (1 second and 4.5 seconds) and Through put Bps being between 0 and 500000.
After the test completes:
On the Design Tab at the top, it shows the Time (5 minutes), the number Sent (7936) and the Failures (934).
On the Design Tab on the Soap UI Runner, it shows number of Requests (7936), Running (0), Completed (7936), Queued (0), Discarded (3069) and Failed (321).
On the Report under Execution Data it shows Total number of requests (7936), Total number of failed requests (0), Total number of assertions (1237) and Total number of failed assertions (934). Under Execution Metrics for Runners it shows a count of (7936) and also Min, Max, Ave, Std-dev, Min/avg, Max/avg, err and ratio. Under Assertions it shows the Constraint column and the Failures. For my Through put - it is showing (261) errors and for Time Taken assertion it is showing (352).
I am trying to figure out the following (after test is complete):
On the Design Tab - top - what does the 934 Failures represent? What sort of Failures are they - Assertion failures? I don't think so, but am not sure what sort of failures they are?
On the Design Tab - on the Runner itself, if Discarded is 3069, I was expecting Completed to be (7936 - 3069) or (4867) not 7936. Also if 321 Failed - does that mean 321 Failed assertions? If so, why doesn't that value match the the Assertion values on the report? If it does not represent Assertion Failures but request failures - shouldn't it match the 934 value?
What exactly does Discarded mean? How are the Discarded requests being taken into account overall?
Why don't any of these numbers add up?
Are some of the Failures that are showing up, Failures of the Assertions that exist on the Soap UI Project rather than the Load UI assertions?
I am just a little confused. Thanks for any clarification anyone can provide!
After the test completes:
On the Design Tab at the top, it shows the Time (5 minutes), the number Sent (7936) and the Failures (934).
On the Design Tab on the Soap UI Runner, it shows number of Requests (7936), Running (0), Completed (7936), Queued (0), Discarded (3069) and Failed (321).
On the Report under Execution Data it shows Total number of requests (7936), Total number of failed requests (0), Total number of assertions (1237) and Total number of failed assertions (934). Under Execution Metrics for Runners it shows a count of (7936) and also Min, Max, Ave, Std-dev, Min/avg, Max/avg, err and ratio. Under Assertions it shows the Constraint column and the Failures. For my Through put - it is showing (261) errors and for Time Taken assertion it is showing (352).
I am trying to figure out the following (after test is complete):
On the Design Tab - top - what does the 934 Failures represent? What sort of Failures are they - Assertion failures? I don't think so, but am not sure what sort of failures they are?
On the Design Tab - on the Runner itself, if Discarded is 3069, I was expecting Completed to be (7936 - 3069) or (4867) not 7936. Also if 321 Failed - does that mean 321 Failed assertions? If so, why doesn't that value match the the Assertion values on the report? If it does not represent Assertion Failures but request failures - shouldn't it match the 934 value?
What exactly does Discarded mean? How are the Discarded requests being taken into account overall?
Why don't any of these numbers add up?
Are some of the Failures that are showing up, Failures of the Assertions that exist on the Soap UI Project rather than the Load UI assertions?
I am just a little confused. Thanks for any clarification anyone can provide!