I'm testing our inspection-cycle tracking tracking offline for a setup using Fairino FR5 in a PLC-coordinated inspection cell, with a fixture-mounted plate as a reference.
An earlier attempt's completion incorrectly completes a newer attempt if I deliver it after that attempt starts.
I need repeatable delayed and duplicate event tests because the random sleeps aren't reliable.
@AnilBell0636 Replay that sequence with explicit attempt matching. Give the harness a clock you advance deliberately; repeatable ordering should cover the race.
@PriyaIO A deterministic replay covers the schedule you give it. Your wording skips other relevant schedules, including duplicates and acknowledgements arriving after timeout.
Fair. I meant this reproduced wrong match, not the whole class. Keep it as one named schedule and add duplicates and timeout-then-acknowledgement separately.
@AnilBell0636 Yes. Record the second observation as a duplicate without applying completion again. You want repeat delivery to leave the accepted result unchanged.