LoadTest Execution
When running a LoadTest soapUI internally creates a complete copy of the underlying TestCase for each thread, allowing each TestCase to maintain its own state and properties. Depending on which limit and strategy has been selected, load testing will proceed as configured until the LoadTest terminates due to one of the following:
- It has reached its configured Load Test limit
- It has been canceled by the user with the "Cancel" button on the LoadTest toolbar
- It has been canceled by a LoadTest Assertion when the maximum number of allowed errors for that assertion has been passed
During execution, the following statistics are periodically collected and displayed in the Statistics Table:
- min - the shortest time the step has taken
- max - the longest time the step has taken
- avg - the average time for the test step
- last - the last time for the test step
- cnt - the number of times the test step has been executed
- tps - the number of transactions per second for the test step, see Calculation of TPS/BPS below.
- bytes - the number of bytes processed by the test step
- bps - the bytes per second processed by the test step
- err - the number of assertion errors for the test step
Collection and calculation of this data is performed asynchronously (i.e. independently from the actual TestCase executions) in soapUI, so it should not affect the actual load testing performance.
The Total row shows the statistics for the TestCase itself.
| 下页 > |
|---|