- Most SUTs implement a response
shut_off
that is not specified. If this was a singular case - only one SUT had this response - then I'd regard it as an anomaly, but (for now) the count is 3.
- Locking while locked should give a
!invalid_command
but SUT sends!locked
- Implements
!shut_off