Forum Discussion

pandap's avatar
pandap
Contributor
12 years ago

Issue with Test Step Count in Load Test

Hi,

The test step count of type "REQUEST" shown on the screen when you run load test in SoapUI doesn't match against the records inserted in the database using event "LoadTestRunListener.afterTestStep".

Load Test Scenario: 2 request per second / With Total Runs set to 600
Count for Request step on the report shows 600 which is as expected but number of the records inserted is 609 which is in excess. As I am capturing the raw request and response I am seeing valid request and response for all the 609 requests.

I think even though the report show 600 count for request step, the soapui is sending few extra requests.

Thanks,
Prashanth

5 Replies

  • MarcusJ's avatar
    MarcusJ
    Icon for Staff rankStaff
    12 years ago
    Hi,

    We are looking into this.

    Is there any more information you can provide to support your findings, such as number of threads, test delay, etc.?

    Also, can you double check your database to ensure you did not have records in the database before doing a loadtest. I also don't understand what you mean by 2 requests per second along with setting the total runs to 600.

    I tried a simple load test with 1 thread, one request test step, and a limit of 30 total runs while appending to a file with the word "test" in the "LoadTestRunListener.afterTestStep", and it appended the word 30 times to the file which is what I would expect.
  • pandap's avatar
    pandap
    Contributor
    12 years ago
    Hi,

    Sorry for the delayed message I was off due to Diwali festival!!!

    I am attaching the screen shot of the LoadTest screen which will give you all the details you are interested. The rate value on the load test is set to 2 which I was referring as 2 request per second because it actually generates two request per second.

    I am not sure if datasource/datagen has anything to do with this, because based on your test you are triggering only 30 times the event which is same as the test step execution count. I have also attached the Data Source Options screen just in case you are interested in it.

    Thanks,
    Prashanth
  • MarcusJ's avatar
    MarcusJ
    Icon for Staff rankStaff
    12 years ago
    Hi,

    I see that you have three test steps and you are using the event "LoadTestRunListener.afterTestStep".
    This event would be triggered after every test step in the load test. What you can try if possible is running the EIP_MeterReadWS test step separately as a load test and see if the database insertions are the correct number of times. The counts for the first two steps based off the screen shot are higher than the third step and since you are using an event handler that could be causing the extra insertions.
  • pandap's avatar
    pandap
    Contributor
    12 years ago
    Hi,

    But I need to do data driven testing, I tried to trigger event only when the request step is executed using the Target option. But this doesn't trigger this is another issue I had faced, so I am controlling to trigger using groovy script in the event handler by using the below code.

    if (testStepResult.testStep.config.type == 'request')

    Let me know if you still want me to do try just running with EIP_MeterReadWS.

    Thanks,
    PRashanth