← Back to the chapter · Next detail →
Technical detail · End-to-End Testing: Claims and Layers
State transitions and evidence limits
A state machine is a model of the named states a system can be in and the events that move it between them. A connected device’s states and transitions span firmware, hardware, radio, cloud services, mobile apps, and operations.
MQTT QoS (Quality of Service) is the message-delivery setting that controls what acknowledgement and retry behavior the broker and client use; it affects whether duplicate messages can arrive. A duplicate-message defect may also involve packet loss, retained sessions, queue IDs, timestamp ordering, backend handling that processes a repeated message without repeating its effect (idempotency), and dashboard refresh.
A failed OTA update might involve bootloader slots, image signatures, battery state, flash wear, interrupted downloads, and rollback rules. Bootloader slots are separate storage areas where a device can keep its current firmware and a candidate update, allowing it to return to the known-working image if the update fails. A schema migration updates stored data to a new format or meaning so new firmware can read it; interruption or incompatibility can leave old data unusable. These interacting behaviors can create defects across layers.
That is why a release gate needs traceability, not just pass rate. The reviewer should see which claim was tested, which state was forced, which logs and measurements were captured, which defect or waiver remains, and which owner can act if the field signal changes. A green dashboard without this chain can hide a skipped environmental run, a quarantined security test, or a failure that only appears during reconnect.
Evidence also has timing and observability limits. A firmware log can prove the device queued a reading, but it may not prove the broker accepted it once. A cloud metric can show ingestion latency, but it may not distinguish RF loss from backend throttling. A current trace can show sleep entry, but it may not prove the same behavior at low temperature or after an interrupted OTA update. Validation has to combine artifacts at the same scenario boundary.