pmdk icon indicating copy to clipboard operation
pmdk copied to clipboard

Load custom test config files from TEST*

Open tomaszkapela opened this issue 8 years ago • 1 comments

RUNTEST has the nice feature of loading per test group configuration files (which was done for remote tests). However in the odd case you would want to run the test not through RUNTEST - which you probably shouldn't - this functionality is absent. The question is, do we want it there for consistency? And there is still the issue of having this on Windows.

tomaszkapela avatar Jan 26 '17 12:01 tomaszkapela

If you can load it directly from the TEST file, you could just put . ./config.sh into each TEST file in given directory and that's it. Or, we can do it inside setup function - if ./config.sh is present, then load it. However, the whole point is that by using config.sh you can override some global settings that are usually configured in RUNTESTS script (i.e timeout), before the TEST scripts are even started. Can we do it with config.sh? Perhaps we can - i.e. as for timeout, maybe we could move timeout to expect_(ab)normal_exit. If the same can be done for all the other configuration settings, than handling config files could be moved to setup, thus it would work regardless of the way the TEST script is run.

krzycz avatar May 17 '17 22:05 krzycz

I believe it is already resolved.

janekmi avatar Aug 30 '23 16:08 janekmi