> By the way, I wonder if we can explicitly forbid the use of ${...}
> expressions in file names.
Mm. I see it as a quite limiting change, considering the test plan can
be run in different envs with different jmeter installation paths, or
for ex. I run it locally on the pre-installed jmeter instance, and
ci/cd runs it via jmeter maven plugin - which requires the filenames
to be resolved dynamically.> As a side note, programmatic test plan generation gets this "Include + > Module controller" for free. > I agree "JMeter libraries" is useful for UI, however, I wonder if you > considered programmatic test plan generation. Well, in my case the ambition is to use a jmeter benefit in it's visual way of building test scenarios in just a few clicks having all those reusables properly organized in the libraries. (we are intended to use jmeter for both functional/feature and load/performance backend testing, so the scenarios are supposed to be quite complex and diverse) //Lena
