Forum Discussion

chioubaca's avatar
chioubaca
Occasional Contributor
12 years ago

[Soapui Load Tests] Setting rate and limit using properties

Hi all,

I'm evaluating SoapUI Pro for our needs and I try to launch a load test using properties values for setting up some of the load test parameters.

I've created a loadtest using fixed-rate strategy, I've created global properties RATE and LIMIT (with correct values) and I have set ${#Global#RATE} as rate value and ${#Global#LIMIT} as limit value in my loadtest.
It worked well during the first execution of my loadtest but, when I modified the properties values and re-launch the loadtest it still used the old values (the one that were set at the creation of the properties).

Is it possible to launch a loadtest with dynamic parameters as I'm trying to do ?
Thanks by advance for your answer

2 Replies

  • You are pointing to Global properties. These properties are saved in preferences file: C:\Users\<username>\soapui-settings.xml

    So if you hit save, you might have only saved the project. Make sure to do: File > Save Preferences.

    Also, I would recommend that instead of Global properties you would use Project-level or TestSuite-level properties instead (http://www.soapui.org/Functional-Testin ... rties.html)

    Thanks,
    Michael Giller
    SmartBear Software
  • chioubaca's avatar
    chioubaca
    Occasional Contributor
    Thanks for your answer, indeed I was not saving the references file before updating the properties values but saving this file before launching my load test doesn't solve the problem.
    I also tried to use TestSuite-level properties without success.

    The "Limit" value doesn't seems to be configurable using property (when I enter ${#TestSuite#LIMIT} as value in the limit field and then click on other field, the value of the "Limit" field gets back to its old value - without property).
    The "Rate" value seems to accept a property-based value (I enter ${#TestSuite#RATE}) but, when I launch my load test, the TPS value doesn't match with the rate-property value (for example 50) but match with the rate value setted before the property (in my example 90).