Changes since tdaq-03-00-xx
New features
Some changes concerning the cooking of environment for test processes:
the tested application environment (e.g. the one passed by rcdal) is not added to the default test environment
the value of TDAQ_APPLICTION_NAME is passed to a test process as new environment TMGR_OBJECT_ID. It is to be used in parameters of the test for templated RDB server.
TDAQ_APPLICTION_NAME env. is set to value of <test_id>_<object_id>: it will be seen in ERS messages as application name.
TDAQ_ERS_* environment for the test are overwritten: either by values read from respective TMGR_ERS_* environment, or if it is not set, by default values "lstdout".
Fixes and improvements
StartTest methods are executed from thread pool and do not block calling client (DVS, RC) in PMG calls
StartTest methods do not return exceptions, former CannotStartTest exception is returned in user callback
User callback function (or functor object) is passed to any StartTest call instead of to the TM_Client constructor
wider use of boost::
some code clean-up
- in case a random test host is bad PMG-wise, it is removed from the list and test started on another one (also patched in tdaq-03-00-01). Exception is thrown if no good hosts left in the pool.
Known bugs, problems and limitations
Test DAL: reverse aggregation relationship not resolved properly if an object is contained in more then one container.
Changes foreseen for next major release