LoadTests execute multiple runs of a SoapUI test at the same time. You may need to configure some test steps to adapt the test for your purposes.
The Run TestCase step can be configured in the following ways:
Create isolated copy for each run – every time the Run TestCase step starts, it will create a copy of the target test case and run it. This approach has the best performance and prevents any conflicts during the execution.
Run primary TestCase (wait for running to finish) – if the target test case is already running, the next simulated user will be delayed until the case finishes. This approach is much slower, but you can change the test case during the test run.
Run primary TestCase (fail if already running) – this option is not suitable for load testing.
You can share the DataSource test step between users in the load test. By default, each user will use an individual copy of the data source. Set the Shared option to force all users to use the same copy of the data source. This will exhaust it much faster. Set the Restart Shared option to restart shared DataSource after it was used and continue the load test.
To stop the load test after DataSource has been exhausted, set the Fail on Empty option.
You can choose what data from DataGen should be shared between test runs. For example, if you use the generated property with the Number type to create unique IDs, select the Shared check box to make them unique. You can then use a different value from DataGen without selecting the Shared check box. This value will be the same for all test runs.
For information on the specifics of using shared DataSinks, see Using Shared DataSinks.