AndyHughes
14 years agoRegular Contributor
Another table log issue....
I've got a load test set up to out put the results at test step level in a table log. Which works.
There are 4 test steps 1. Data source 2. The request, 3. Properties and 4. Property transfer.
The load test is a ramp up with a limit set at 3000 requests. After about 2:30 the test ends and I save the results to a csv.
However the .csv shows an inconsistent number of test steps. For example there are 3779 rows which represent the test case as a whole and only 2530 representing the step which is the request. property trans = 2603, properties=2770 data source=3303
I could understand a little inconsistency, as by the end of the test the rate is around 40/sec. So maybe some don't finish etc. But we are talkin hundreds here.
Also, in the is file the 1st response for the request test step is recorded at 17:07:19:558
But in the Average table (which polls every half second) the 1st request which completes is recorded at 17:07:14:387, this is 5 seconds before the 1st response time in the other table. (and the requests take in the order of 20-30ms)
Any idea what's going on?
There are 4 test steps 1. Data source 2. The request, 3. Properties and 4. Property transfer.
The load test is a ramp up with a limit set at 3000 requests. After about 2:30 the test ends and I save the results to a csv.
However the .csv shows an inconsistent number of test steps. For example there are 3779 rows which represent the test case as a whole and only 2530 representing the step which is the request. property trans = 2603, properties=2770 data source=3303
I could understand a little inconsistency, as by the end of the test the rate is around 40/sec. So maybe some don't finish etc. But we are talkin hundreds here.

Also, in the is file the 1st response for the request test step is recorded at 17:07:19:558
But in the Average table (which polls every half second) the 1st request which completes is recorded at 17:07:14:387, this is 5 seconds before the 1st response time in the other table. (and the requests take in the order of 20-30ms)
Any idea what's going on?