TMC Test Scenarios and Harness

At the moment the code of the test harness is not very modular and easy to extend and to understand; the code is also duplicated in several places for the different integration testing initiatives. For example, the current mechanism for checking what events are raised by the SUT is the one designed for unit testing, that has different requirements than integration testing, which makes it not the most suitable one (eg no timeouts can be specified). Fixing these things will improve uptake by other teams, avoiding that they are forced to reinvent the wheel, and improve their productivity and effectiveness. In addition, tests can only be run in a very unflexible way (all together, via 2 steps that are not separated: setting up the SUT and  running  the tests): this slows down test execution and reduces flexibility of the tester (who cannot run a single test at the time, for example). Fixing this will improve speed of execution of tests, and flexibility of how tests are run. as an effect, testers will be more effective in tracing and debugging individual tests, leading to shorter cycle time for tests. Finally, when running tests there is little support by logging in terms of tracing what is happening. For example, no clear print out is produced identifying the version of the different SUT components. Fixing this will improve observability of test executions, and as a consequence productivity of testers.