Hello all,I was wondering if anyone could help me with this.Basically, I am using SoapUI Pro 4.0.1 to put my tests together. I am using a CSV file as my datasource, making a request with one value, then after a successful iteration, using datasource loop to go to the next record.If I export the test to a LoadUI project, will the datasource loop also be included during the testing process within LoadUI? I'm relatively new to the tool, so I'd just like to know if the test defined in SoapUI will be reflected in LoadUI.Many thanks,Mike

Hi,Yes, it will be. Usually you won't want each execution of the soapUI runner in loadUI to run through the entire loop though, so a common approach is to make sure the DataSource is set to "Shared" (and to restart), and to disable the DataSource Loop TestStep. This way, each time the soapUI Runner is executed it will just run the loop one time, incrementing the loop counter for the next iteration.Regards,DainSmartBear Software

OK, well my test scenario is this:I want to run a load test for 2 hours, 10 VUs in total with a ramp up of 5 users every 10 minutes (this will be run in conjuction with other tests). I want to run an authentication request test, and this works by sending in a username and password. This results in the user being assigned a session token which asts for 10 minutes, though it is possible to login again with the same user, after a few miliseconds.I currently have a datasource with 200 usernames and passwords and after each iteration of the test, I want it to go to the next record. If it gets to the end of the list, it can start again because enough time will have passed for successful re-authentication.I've attached screenshots of my setup, so could you help verify if anything needs to be changed so it will run with LoadUI? I'm a bit unsure as to why DataSource loop is discouraged...

I think because if you have the data source loop, it means that each time the SOAPUI test is run via Load UI it will trigger the SOAPUI test which will run and (if you have data source loop) cycle through all 200 in your list before passing control back to loadUI for the next trigger of the SOAPUI test to happen again. What you would in effect be doing is timing SOAPUI cycling through 200 usernames and passwords, and that would constitute 1 LOADUI request.

That makes a lot of sense, and would definitely act to the detriment of performance when running the test in this way.I think the solution we're taking is to write a Groovy script to iterate through a CSV file and make this part of the test step, so we can use the free version as opposed to using SoapUI pro - the licensing thing just wouldn't work out for us

So does this mean that you think you can somehow persist the place you got to in your list (within SOAPUI) so that each time the test is invoked by LOADUI it uses the next values in the list?

Are all test steps defined in SoapUi carried over to LoadUI?

16 Replies

AndyHughes
Regular Contributor
15 years ago
You can use property transfers to get the actual results of each loadui request. Set the property transfer at test case level and then populate the property with the response string. Then in the SOAPUI runner in LOADUI, export the test test case properties.
PerfTestMike
Contributor
15 years ago
Thanks for the tip! Can you provide some screenshots and numbered instructions regarding this? I'm a tad lost, but I understand the idea
AndyHughes
Regular Contributor
15 years ago
As requested...in SoapUI

...and in LoadUI

It then comes out on the table logs attached to the SoapUI runner.
ajaychandraredd
15 years ago
Hi Mike,

I used the script from your post that reads in the values from a CSV and iterates to a new record after every run, which worked fine in SOAPUI 4.0.1. But with LoadUI 1.5.0 always the last request is being read, i am sure i missing something here. Can you please suggest if i need to set any other settings before creating the same project in LoadUI.

I am using below components

1) Fixed rate generator
2) soapUI Runner.

Please find the attachments for the screenshots. It also includes the test data format in the CSV file

Thank U.

SmartBearQ-1.doc170 KB
PerfTestMike
Contributor
15 years ago
Hello, thanks for trying this out.

I will have a look into this, as I didn't do anything more with it as we opted to go for SoapUI pro and use databanking. It is probably a minor script change that will need to be modified so that the script iterates through each row. I wish Java could be used instead of Groovy because I had never even touch Groovy before using this tool

I'll get back to you on this, though
PerfTestMike
Contributor
15 years ago
OK, so update time!

As an alternative to exporting your test from SoapUI to LoadUI, what you can do is:

1) Create your test in SoapUI;

2) recreate it in LoadUI manually;

3) save script in C:\Program Files\Eviware\LoadUI\Script Components;

4) manually recreate your test using the attached CSV reader (created for standard CSV use which takes the first row as the field name and the following rows underneathe as the corresponding values);

4a) Place this element between the load generator and the soapUI runner;

The advantage of this is that it removes the user from any test-exporting related issues (as I've found my tests have corrupted after exporting from SoapUI to LoadUI). It should mean you can create a test without having to mess about with setting up data in soapUI
CSVLoader.groovy1 KB

Forum Discussion

Are all test steps defined in SoapUi carried over to LoadUI?

16 Replies

Recent Discussions

Unable to authenticate license in Ready API Login button unresponsive

Assertions Panel issue to update assertions since update 3.63

ReadyAPI websocket plugin issue

Related Content

NameError: name 'Aliases' is not defined

Defining conditional attributes in OpenAPI

'Project not defined' errors after updating to 15.77.6.7