[email protected]!

That was a pretty arrogant answer! I refrain myself from further discussion 
though, except that proposing that patience is a virtue if you're working for a 
support organization.

I do apologize for being a bit ignorant myself not thinking about the execution 
order in this case. I think however, that I am not the only one thinking that 
Jmeter is not very intuitive. It is not uncommon with tools where things are 
actually executed in the "order of appearance". There may be good reasons for 
why it is like it is now, but allow me to ask why, if a Configuration Element 
is always executed prior to all other, is it allowed to be placed (almost) 
anywhere? Perhaps an area for improvement?

Thanks a lot for your answer!
BR
/Krister

-----Ursprungligt meddelande-----
Från: [email protected] <[email protected]> 
Skickat: den 7 april 2021 13:01
Till: [email protected]
Ämne: Re: Jmeter not substituting variable in CSV Data Set Config

Of course it doesn't. Could you please bookmark the  Execution Order
<https://jmeter.apache.org/usermanual/test_plan.html#executionorder>   
chapter and re-read it prior to asking the next question. 


CSV Data Set Config is a *Configuration Element* so it's being executed before 
the JSR223 Sampler and in fact before everything else. 

The only configuration element which takes precedence is  User Defined 
Variables 
<https://guide.blazemeter.com/hc/en-us/articles/207421395-Using-User-Defined-Variables-Using-User-Defined-Variables>
so you can define your *testdata* variable there and if you want to make it 
dynamic - use __groovy() function
<https://jmeter.apache.org/usermanual/functions.html#__groovy>   to
calculate/assign the value. 





--
Sent from: http://www.jmeter-archive.org/JMeter-User-f512775.html

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to