This test module shows the utilization of Simulink models for test purposes in a very simple way.\n\nVerdicts for the test cases can be derived in different ways:\na) Evaluate a (physical) result value directly in the test module. \nThe allowed range is specified within the test module, there is no need to provide the range to the Simulink model.\nb) Delegate the physical value evaluation to the Simulink model\nProvide the allowed range to Simulink and only consider a result variable (that will contain passed of failed) in the test module.\nWithin this test module, both approaches are shown. This testcase measures the time which is needed for a full brake. \nHere, the evaluation of the physical value is done in the XML test module. (see test module description)\n 100 $ABSon$ 0 1 0 0 This testcase checks the distance for the brake sequence. A Simulink model takes the actual brake distance and the setpoint for an upper limit as input. If the limit is excessed the system variable BrakeDistVerdict is set as an output of the Simulink model. This system variable represents the verdict of the test case and is evaluated by the state change pattern within the test module. 100 0 $ABSon$ 1 0 0 This testcase modifies internal characteristics of the application model which is connected to the chassis node as a Simulink model. Different set points for the slip value are set before the brake sequence is started. The control algorithm will behave differently upon these values. It can be observed in the graphics window. This test will always succeed. 100 0 1 0 $slipValue$ 1 0 0 0 1 0 1 0.15 0.11 0.13