AlexBell0646 · 15 Dec 2025, 17:17 UTC
Use explicit test steps or barriers instead of random sleeps: start the newer attempt, confirm that state is reached, then deliver the retained older event. Keep attempt identities in the test data and assert which attempt changes, not only whether a total increments.
20 pointsBoth attempts have distinct IDs. The newer one becomes complete when the old event arrives.
25 pointsAssert that the newer attempt stays unchanged. A successful-looking final counter is not enough.
7 pointsKeep repeated delivery of the current event separate from delivery of the older one. Those expose different mistakes, even if both used to appear as an extra finished item.
5 pointsI'd include restoring the saved history before the delayed delivery, because a clean test start can hide what your real tracker already knows about the old attempt
16 pointsAdded an explicit release step for the old event. Failure now repeats without waiting for luck.
10 pointsGood. Keep that failing sequence while the implementation changes, then assert both persisted state and the report output. Correctly retaining the attempt record does not automatically prevent a separate display path announcing a new completion.
19 pointsAnd include a genuinely new result. Don't make ignoring all completions pass the tests.
22 pointsDoes the test restore the same identity scope as the installed tracker, including job run if attempt numbers repeat?
11 pointsYes, job-run plus attempt identity. Report assertions are still incomplete; stored-state assertions now cover the old event.
20 pointsKeep that remaining report work visible in the handover note, Alex, so a passed tracker test isn't read as proof that every screen counts correctly
7 pointsPlease return with the repeated-current and report results when they are ready. You now have a repeatable old-event failure, which is useful progress, not yet the whole regression set.
5 pointsThis discussion is closed to new replies after six months without activity. Last activity: .