Technical detail ยท Ideate, Prototype, and Test
Tests Need State, Payload, Timing
4.6.1 Tests Need State, Payload, Timing
An alert test needs more than a happy path. Show what happens while an alert is pending, when data is stale, and after a person acknowledges it. For setup, include a failed scan, a bad password, and a retry. These states help a team see whether people can recover from a fault.
When a prototype sends data, keep a sample message and its time. Record where it came from, its version, and any retries. This makes it possible to trace a delayed alert back through the system. A screen that looks right does not by itself prove that the data path works.
Measure the risk under test. For a sensor, compare known inputs with readings and count missed and false events. For a workflow, observe task success and the time to acknowledge an alert. Keep the test setting, artifact version, failures, and decision with the evidence. Then the team can tell whether to change the idea, improve the prototype, or test it in a more realistic setting.