iso9001
15 years agoNew Contributor
load test basics
hello everybody,
i am trying to understand and get adjusted to the features of load tests in soapUI but i can be considered as a newbie. there are some point that i want to make clear in my mind and i need your help. here are my questions:
1.) when i export the data as described here: http://www.soapui.org/Load-Testing/expo ... stics.html (please check the charts at the bottom starting with the pie chart). other than the pie charts, there are graphs but there isn't any naming on the x and y axis. besides there is another y axis on the right side of the charts. i understood that y axis on the left represents the values (i.e. the average times) and the x axis represents the steps (the number equals to the count value) but i don't know what the y axis on the right side represents? i checked the official site but was unable to find what i am looking for
2.) when i am running the load test, i select the thread as 10. i know that thread are virtual users that are sending requests to the app-server. let's assume that i run the test for 10 seconds, with the test delay 100 ms. so, i assume that, since the delay is 100 ms and the total time is 10 seconds, how many times (test runs) will occur? is the result 1000ms/100ms=10times and 10times*10seconds=100 times? moreover, since there are 10 threads, how many requests are going to be sent to the server? is it 100times*10threads=1000requests?
3.) i added the Step Average assertion to my test. configuration is as follows:
minimum requests=0
max average=500
max errors=0
sample interval=20
teststep=any
after i run the test, the avg time is calculated as, say, 600 ms. however, even though i selected the assertion max average as 500 ms, the test does not fail. how is the assertion mechanism of the load test works? is it related with the sampling? i assume that after 20 request is made, soapUI calculates the average of first 20 and then compares it to 500 ms. if it passes over, that *20th* request fails. is that true or something different is behind the scenes?
4.) is it possible to save all the responses separately into a folder so that i can check the contents of each response? if it is possible, how can i do that?
5.) what does the count *rat* in the main load test window mean? if it is ratio how is it calculated? assuming 100 request is made (i believe this is the column cnt) and if the error count is 10 (this must be err column), why the ratio remains as 0 but not 10 per cent?
i am sorry if my questions sound silly or if i wasted your time. thanx to all who wished to spend some time for me.
best regards,
- iso
i am trying to understand and get adjusted to the features of load tests in soapUI but i can be considered as a newbie. there are some point that i want to make clear in my mind and i need your help. here are my questions:
1.) when i export the data as described here: http://www.soapui.org/Load-Testing/expo ... stics.html (please check the charts at the bottom starting with the pie chart). other than the pie charts, there are graphs but there isn't any naming on the x and y axis. besides there is another y axis on the right side of the charts. i understood that y axis on the left represents the values (i.e. the average times) and the x axis represents the steps (the number equals to the count value) but i don't know what the y axis on the right side represents? i checked the official site but was unable to find what i am looking for
2.) when i am running the load test, i select the thread as 10. i know that thread are virtual users that are sending requests to the app-server. let's assume that i run the test for 10 seconds, with the test delay 100 ms. so, i assume that, since the delay is 100 ms and the total time is 10 seconds, how many times (test runs) will occur? is the result 1000ms/100ms=10times and 10times*10seconds=100 times? moreover, since there are 10 threads, how many requests are going to be sent to the server? is it 100times*10threads=1000requests?
3.) i added the Step Average assertion to my test. configuration is as follows:
minimum requests=0
max average=500
max errors=0
sample interval=20
teststep=any
after i run the test, the avg time is calculated as, say, 600 ms. however, even though i selected the assertion max average as 500 ms, the test does not fail. how is the assertion mechanism of the load test works? is it related with the sampling? i assume that after 20 request is made, soapUI calculates the average of first 20 and then compares it to 500 ms. if it passes over, that *20th* request fails. is that true or something different is behind the scenes?
4.) is it possible to save all the responses separately into a folder so that i can check the contents of each response? if it is possible, how can i do that?
5.) what does the count *rat* in the main load test window mean? if it is ratio how is it calculated? assuming 100 request is made (i believe this is the column cnt) and if the error count is 10 (this must be err column), why the ratio remains as 0 but not 10 per cent?
i am sorry if my questions sound silly or if i wasted your time. thanx to all who wished to spend some time for me.
best regards,
- iso