Changes since tdaq-01-08-00
API changes
Now it is possible to pass a user-defined parameter to TestObject and
StartTest methods. This parameter is then returned in test_data
structure in the test completed callback, so user cab get the
information about the object which launched the test:
struct test_data
{
...
void* td_user_data ; // parameter that may be filled by the user and then accessed in the callback
}
std::string
TestObject( ConfigObject& obj, void * user_data = 0, const std::string& scope = "")
New features
To improve the performance in case of many tests launched on a single
(default Partition) node, do distribution of the load: if explicit host
for a test is not defined, use random computer from "TestsComputers"
ComputerSet defined in the database. The Partition default host is also
used in addition to those defined in TestsComputers set.
NB: for
proper DB archiving, this ComputerSet object is to be linked with some
segment (using "Uses" relationship), presumably with
OnlineInfrastructure segment.
Known bugs, problems and limitations
Logs of processes are
viewed only if TDAQ_LOGS_PATH points to a location which is shared
between
client (DVS) and server (PMG agent where a test is launched). In
future, use of Logs Service is foreseen.
Changes forseen for next major release
Merjing of test DAL schema with core schema, using class type and
direct relationship to a new 'Testable' base classe instead of strings
for tests bindings to objects.