Test application structure:

CS +---> threaded fanout +------------------+
             +                              v
             +--------+                   +Device1+
                      |                   |       |
                      v                +--+       |
  CS   <---------+ Module1 <-------+   v          |
              |       ^            +Consuming     |
              |       +---------+    fanout       |
              +----+            +      +          |
                   v         Device2   |          |
  CS   <---------+ Module2             |          |
                                       |          |
  CS   <-------------------------------+          |
                                                  |
                                                  |
  CS   <---------+ Trigger <----------------------+
                      ^
                      |
                      +
                      CS

They return as soon as the condition is fulfilled, so there is no harm in having long timeouts in case the tests are successful. The only drawback is that it takes longer in case of errors.

		add bool thereHaveBeenExceptions
		write test for taht
			testExceptionsDummyDevice.cc

wip #47: add test for direct connections from ConfigReader to a device. The test is currently failing.

		writeAfterOpen writes constants to devices
		remove writeAfterOpen in recovery loop
			that should be in writeRecoveryOpen
		extend testProcessVariableRecovery for constants

  - Handle illegal writes to read-only accessors in doPreWrite().
    Otherwise, attempting to write to the recovery accessor would result
    in a nullpointer access.
  - Related test case.

test was broken by its design, which became now evident with the proper initial value propagation

forgot to commit latest change: testProcessVariableRecovery now tries to get exception by reading (not writing), currently failing