Our offline UR5e bracket tracker assigns an earlier attempt's completion to the current attempt if it arrives late, but the random-delay test does not reliably create that order; what should I ask the developer to control explicitly?
Control the event order and test clock. Specify both attempt identities, start them deliberately, then deliver the old result while the new attempt is pending and again after it finishes. Assert both attempt states and the physical bracket count after each step. Add duplicate delivery, unknown identity and restart cases separately. None should need a random sleep or a new physical inspection request.
9分