New features since tdaq-01-01-00

Changes in test-repository.schema.xml

New attributes for Test base class. See tmgr release notes for the details.

DVS core

User can choose different levels of complexity of testing <>using Level Selector menu under Options menu in  the GUI. Only those tests with a complexity value which is equal with this user provided criteria will be executed. The default value  in the Level Selector is "none", meaning that all the tests will be executed independant on their particular complexity value.
<>User can select at run time a test or a sub-set of tests using Mask Selector menu under Options menu in GUI. Only those tests with a test_mask value that fits this user  provided expression will be executed. This selection is made without the need to edit the configuration database.
<>
Tests are blocked at execution depending on their scope defined value and system state.
The existing mechanism is extended to cover syncronization between components belonging to one parent in the tree.
Test logs are available in the same location as all other applications logs: LogsRoot/partition_name/user_name/***.testout
This log is created when test returns its status code to the TestManager. During the run time another temporary file is created and the user can use this log to follow the correct execution of the test. The temporary log is in the same location:  LogsRoot/partition_name/user_name/***.testout_testName
The user has the possibility to launch interactive tests. This gives access only to specific binaries defined in the database, in specific conditions and by authorized users.
When an interactive session will be started, a connection to the host machine is made, an xterm is started, the correct environment is set and the defined binary is launched. After the test is finished, the xterm will resume its activity within 4 seconds.

DVS GUI

Search capabilities are added to the Log Browser, with case in/sensitive.

Known bugs, problems and limitations