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

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,
Dain
SmartBear 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?

This is defnitely possible, as was shown to us by one of our developers today. All that's needed is a bit of Groovy wizardry, and it's possible to use a script to bypass the datasource tool. I will post again once I've figured this part out, but it should be possible to implement this in SoapUI (standard version) and export it to LoadUI

Update:

So to bypass the SoapUI DataSource function, I've written a simple script that reads in the values from a CSV and iterates to a new record after every run.

def file = new File("C:/[LOCATION OF YOUR CSV FILE]
def values=[]
def username
def password
def lines = file == null ? [] : file.readLines()

for (line in lines) {
 
     propArray = line.split(",")
     username = propArray[0]
     password= propArray[1]
     testRunner.testCase.testSteps["username"].setPropertyValue("username", username)
     testRunner.testCase.testSteps["password"].setPropertyValue("password", password)
     testRunner.runTestStepByName("[REQUEST NAME DEFINED IN YOUR TEST STEPS]")
   
   }

Brilliant thanks. I'll see if I can get this to work.

Your feedback on this would be really useful actually, because I'm trying to export it to LoadUI and I'm finding it hard to verify the results, i.e. finding out what specific requests have failed/passed.

The test seems to work fine in SoapUI in that each value is parsed into the username/password properies and then used in the request. I should point out that the requests I'm making are in the JSON format, so I can't vouch for other types of requests being sent in

And yet another update (or more of an FYI) with that segment of code, you've essentially got two test steps a dataSource and a groovy script. The Groovy script simulates the role of passing username/password into a properties file, as well as using these values in the next step and repeating.

It probably requires a bit more refining, but it gives the bare bones of a nice little script