Thanks for information. I feel this behavior should be in core. To avoid another element, I think updating Flow Control Action is a good candidate as it’s a sample about jmeter internals.
Thoughts? Regards On Monday, November 12, 2018, Andrey Pokhilko <a...@ya.ru> wrote: > Hi, > > There's already a plugin for that: > https://jmeter-plugins.org/wiki/SetVariablesAction/ > > It is exactly a sampler that is used to evaluate functions/variables. > > -- > > Andrey Pokhilko > > 11.11.2018 20:53, Philippe Mouawad пишет: > > Hello, > > Frequently when using JMeter functions, users don't really know for > certain > > use cases where to put the function, here are few examples: > > > > - Any function which output will not be used directly by sample > > parameters > > - Such type of functions: > > - https://jmeter-plugins.org/wiki/InterThreadCommunication/ > > - you want to create a variable from the output of a function and > update > > it on each iteration: > > - User Defined Variable is not an option as evaluation occurs on > > start of test > > - User Parameters being a preprocessor, it would be evaluated on > each > > call, so you need to nest it inside a Flow Control Action, not very > > intuitive right ? > > > > I also remember when I started using JMeter that I found this part > > counter-intuitive. > > > > I think it would be nice to have a solution for this, that would evaluate > > the variables/functions exactly at the place where the call is present > and > > without generating any SampleResult. > > > > We could implement this: > > > > - as an enhancement to Flow Control Action > > - as a new Sampler > > > > What's your thoughts on this ? > > > > Regards > > > -- Cordialement. Philippe Mouawad.
