440 seconds
We write another test method to check that the controller reports a lost message.
This test succeeds as well. After a Timeout event follows the Poll handler, the
ReportLostMessage handler runs. The sensor status remains OK, so the controller
still carries out the calibrate command.
>nunit-console /include=LostMessage Tests.dll
...
Included categories: LostMessage
.?Timeout, Timeout, Error
Reset
?Message ??™99.9??™, Message, Error
CheckMessage ??™99.9??™, compare to 99.9, OK
?Timeout, Timeout, OK
Poll
44 Why We Need Model-Based Analysis
?Timeout, Message, OK
ReportLostMessage
?Command, Timeout, OK
Calibrate ??™99.9??™
?Timeout, Timeout, OK
Poll
?Message ??™99.9??™, Message, OK
CheckMessage ??™99.9??™, compare to 99.9, OK
?Command, Timeout, OK
Calibrate ??™99.9??™
?Exit, Timeout, OK
Did the expected handlers run? [y/n] y
Tests run: 1, Failures: 0, Not run: 0, Time: 8.606 seconds
These tests confirm that the controller works as intended in these runs. Can we
conclude from this that the controller will always work?
3.4 Failures in simulation
We experiment with the simulator and find that the controller does not always behave
as we intend. Recall that we intend that a calibrate command will be carried out if
the most recent sample from the sensor is within-range, but will not be carried out
if the most recent sample is out-of-range.
Pages:
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82