Model-Based Design for Embedded Systems- P45: This book contains information obtained from authentic and highly regarded sources. Reasonable efforts have been made to publish reliable data and information, but the author and publisher cannot assume responsibility for the validity of all materials or the consequences of their use. | 416 Model-Based Design for Embedded Systems executed. A large amount of research is available in the literature for the case where the SUT cannot be reset and resetting input sequences must be devised in addition to the conformance testing sequences see 73 for an excellent survey . Very little work has been done about this problem in the context of timed automata 63 . Given that a test case is a deterministic program what does this program do It essentially interacts with the SUT through inputs and outputs it generates and issues the inputs to the SUT and consumes its outputs. Since the specification defines not only the legal values of inputs and outputs but also their legal timing it is very important that the test case be able to capture timing as well. In other words the test case must specify not only which input should be generated but also exactly when. Moreover the test case must specify how to proceed depending on what output the SUT produces but also on the time in which this output is produced. For example consider a specification for a computer mouse that states if the mouse receives two consecutive clicks the input in less than s then it should emit a double-click event to the computer. One can imagine various tests that attempt to check whether a given SUT satisfies the aforementioned specification and indeed behaves as a proper mouse . One test may consist in issuing two consecutive clicks s apart and waiting to see what happens. If the SUT emits a double-click then it passes the test otherwise it fails. But there are obviously other tests issuing two clicks s apart or s apart and so on. Moreover one may vary the initial waiting time before issuing the clicks. Moreover presumably the specification requires that the mouse continues to exhibit the same behavior not only the first time it receives two clicks but also every time after that. Then a test could try to issue two sets of two clicks and check that the SUT processes both of .
