Example Use Case: We have 100 users and they’ll be using data that can only be used once (meaning the application will not accept that data again, unless of course it is “reset” by the application team). We want that each iteration is assigned a unique value and that it changes from iteration to iteration. There can be other use cases where we just want this even though the data can be used several times.
This would be something similar to LoadRunner Select next row: Unique and Update value on: Each iteration.
For setting this up, you’ll need to declare a property at the clip level. There are two main different configurations depending on your composition configuration.
First. Infinite Clip Repeats (Renew Parallel Repeats Disabled for the Track). Leave everything as default values.
Second. Renew Parallel Repeats Enabled for the Track (Clip Repeats Disabled). You can use either the configuration above or the configuration below. For the configuration below check “Property value is tied to the virtual user” and also “New value per user virtual iteration” when declaring your property.
Check “Save value for analytics” to see the values used after the composition is played with the widget “Property Value Composition Analysis”. You can change the other settings depending on your needs. The most important of these settings is the EOF Action. As for this example I’ve left the default values.
Find attached a composition with the second configuration (using Renew Parallel Repeats). Since it is set to renew parallel repeat, it will run infinitely, make sure to stop it after some iterations have completed to see the behavior. The composition is set to “Preview Mode”, meaning it will not be sending any traffic to the target but it will compute the seed data distribution.