Which failures should a smart-glasses reliability test include?
Include lost connections, duplicate delivery, stale responses, expired requests and recovery after sleep. Verify the actual result at the relevant endpoint. An intermediate service marking a message delivered may establish receipt at that service, without proving that the glasses showed it or the host performed an action.
Test whether the right event reaches the right task
A failure can be subtle: the display updates successfully but with an old response, or a repeated input triggers an action twice. Request identifiers and explicit state transitions make those cases easier to detect. Recovery should preserve what remains valid and discard what no longer applies.
Script a cancelled request that completes late and require the application to reject its result. That checks the meaning of delivery, which a simple connected-versus-disconnected test can miss.