Re: Property files question

On 01/04/2008, Krzysieq <krzysieq <at> gazeta.pl> wrote:
> Ok, I'll try to show some of the bigger picture. We have an internal tool
>  for management of property files. We use those files not only for tests, but
>  also for building our software. They are generated per-environment. Each
>  contains over 50 props, not all of which are relevant to the tests, but all
>  of them are different, or at least can be different, in each file. We also
>  have test campaigns that CruiseControl runs against different envirionments
>  - acceptance, integration and so on. Here our property files work fine
>  because there's no gui, and a set of tests is run only once.

Do all the files define the same set of property names?
If so, then what I suggested  will work.
If not, then you would need to extend the fix to first delete the
properties defined in the first file, before applying the properties
in the new file. This would mean keeping a copy of the currently
loaded properties separately from the JMeter properties.

>  To "emulate" that behavior in the gui mode, our jmeter files contain one
>  ugly walkaround. Each of them has a "user defined variables" element per
>  environment (gives us 4 sets of the same properties per jmx), which use the
>  syntax ${__P(property,default)} to use whatever comes from a file, or the
>  default value for the particular environment in case no prop file is
>  supplied (as in gui mode usually). Enable the one You want, disable the
>  rest, and You're testing the environment You want. This works, but is ugly
>  as hell and we'd like to drop it in favor of a cleaner solution. It's
>  possible to have 4 shortcuts on the desktop each starting jmeter with a
>  different property file. This is a solution, although not the prettiest
>  either, because then our tests start to depend on the configuration of the
>  machine, from which they are run.