That doesn't really solve my problem. What I want is for the test to behave slightly differently - including or excluding different steps each run - so that a load test will eventually cover all the possibilities. I've worked something out using groovy scripts, but its a bit crude and clumsy, because I don't appear to be able to set custom variables at the test step level?
What I tried to make:
A generic REST test step, disabled, that sets a user on an event to a state. all of which are specified in custom test _case_ variables. This step is disabled.
Individual test steps with identical groovy scripts, that randomly set the test _case_ variable for state, copy variables for the user and event from the _step_ to the _case_, and then runs the REST step above. These test steps would have identical scripts, to make maintenance easy, but different test step variables to specify which user and event I wanted to modify.
What I apparently had to make do with, because I couldn't find any way to set custom variables at the test step level:
As above, but each groovy script is hard-coded with the user and event name. Seems like there should have been a better way to parameterize this into a function, but I couldn't figure it out.