Am 07.04.21 um 15:48 schrieb Krister Nilsson: > Hi Philippe! > > No worries! I guess we have to live with not everyone using the same tone in > a society like this. glinius helped me with what was wrong at least, even > though it is a little tricky to solve my use case under the existing > circumstances. I have a workaround at least. > > I wouldn't call myself a beginner, but there is certainly a lot left to > learn. Jmeter is in many ways a very powerful tool, but the frustration > sometimes get rather big since there seems to be so many special cases. To > take a bigger grip on the intuitivity issue would probably be a large > project, but would mean an improvement I believe. > > In my case I did try properties instead of variables, but it didn't make any > difference. Of course it is possible that I made some additional mistake...
It helps, if you try to setup a minimal test plan to work on these issues. That would have at least two positive results. First it should work (and be easier to understand) and second you could send those minimal tests to the mailing list. Then we could try to help you better with those corner cases. How did you define the property? Felix > > Thanks and regards > /Krister > > > -----Ursprungligt meddelande----- > Från: Philippe Mouawad <p.moua...@ubik-ingenierie.com> > Skickat: den 7 april 2021 14:39 > Till: JMeter Users List <user@jmeter.apache.org> > Ämne: Re: Jmeter not substituting variable in CSV Data Set Config > > Hello Krister, > > I'm sorry for your experience in this mailing list, the person who tried to > help you here is not a member of the project. > I guess his contributions help users, but sometimes the tone used is not the > most appropriate. > > Now, regarding the order of execution, I was not working on the project when > it was decided, but from my experience and understanding, the order is due to > the fact that in Configuration elements, we usually want to setup something > before executing any sampler, that's why the order in Plan does not apply and > we rely on scope instead as explained in reference documentation > > - > > https://jmeter.apache.org/usermanual/component_reference.html#config_elements > > > Scoping concept is another very important concept to understand besides the > order: > > - https://jmeter.apache.org/usermanual/test_plan.html#scoping_rules > > > I agree it is not very intuitive for beginners but it has pro/cons. > > Regarding your case, having this in mind, you should rely on Properties > instead of Variables for CSV Data Set filename configuration, see this for > Vars vs Properties > > - https://jmeter.apache.org/usermanual/functions.html > > I hope this helps. > > Regards > Philippe M. > https://leanpub.com/master-jmeter-from-load-test-to-devops > On Wed, Apr 7, 2021 at 2:17 PM Krister Nilsson < > krister.nils...@pensionsmyndigheten.se> wrote: > >> glin...@live.com! >> >> 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: glin...@live.com <glin...@live.com> >> Skickat: den 7 april 2021 13:01 >> Till: jmeter-u...@jakarta.apache.org >> Ä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-De >> fined-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: user-unsubscr...@jmeter.apache.org >> For additional commands, e-mail: user-h...@jmeter.apache.org >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org >> For additional commands, e-mail: user-h...@jmeter.apache.org >> >> > -- > Cordialement > Philippe M. > Ubik-Ingenierie > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org > For additional commands, e-mail: user-h...@jmeter.apache.org
OpenPGP_signature
Description: OpenPGP digital signature
