Forum Discussion

LKRIST's avatar
LKRIST
Occasional Contributor
12 years ago

Loadui incorrect execution count

HI All,

we are doing loadtest using loadui and we are facing several issues
The loadui uses the soapui runner.
Attaching the soapui and loadui project for your reference.
Below are the issues..
1) When I import the soapui project into SOAPUIRunner, the Datasource loop step is disabled by default. I have to enable manually

2) I am doing loadtest with the test case RDCBATCH_AST-0001_TS01_TC02 from the soapui project.
For each run, The datasource step should query 5 rows from the database and constructs single webservice request and make webservice call
I am running 5 messages / minute. At the end of the test I expect the test steps execution count in the soapui runner console as below


Datagen - 5
Properties - 5
Datasource - 5
Groovy script - 25
Datasource loop - 25
Test Request - 5
GroovyUnsetProp - 5


But the execution count displayed is incorrect, I see the below result in the soapui runner console
Datagen - 5
Properties - 5
Datasource - 5
Groovy script - 8
Datasource loop - 8
Test Request - 4
GroovyUnsetProp - 0

The webservice request is not constructed properly and the test case fails.
From the soapui runner console below counts are incorrect
Groovy script - 8
Datasource loop - 8
Test Request - 4
GroovyUnsetProp - 0


Can you let us know why the above 4 steps are not executed correctly?
Is the Datasource step not synchronized? am I doing something wrong in the properties usage?

Please help us to investigate.. we are working on a tight schedule and we need to complete the test by today.
This is first loadtest we are doing using loadui. Please consider this as urgent and send us your feed back asap.
I have also attached the log from the soapui runner(rep.csv)… also the soapui runner console screenshot and error.log

Thanks in advance

1 Reply

  • Hello,
    What you found turned out to be a bug. The fix for this is already done and will be included in the next release.

    Why we are disabling all datasources by default is because each virtual user in LoadUI is not supposed to use different credentials, acting as multiple users. Instead LoadUI makes data sources be shared cross different virtual users making each new virtual user taking the next value from the data source. This sharing of datasources actually broke your test which used a data source to build a single request.

    We fixed this by adding a setting for this in the SoapUI Runner, enabling you to choose if you want the sharing behavior or let it be decided by the SoapUI project.

    Thank you for reporting this!

    Regards,
    Max