AlexBell0646 · 31 Aug 2025, 07:42 UTC
Put the events in a test queue and release them one at a time. Start attempt A, hold its completion, start B, then deliver A's completion. Assert which attempt changes after each step, not just the final count.
20 pointsThat sequence reproduces it every time. Both attempts currently match on the coupon label only.
12 pointsGive attempts their own identity in the proposed interface, then replay the same sequence against the change. The coupon name can stay useful to people without doing the matching job on its own.
13 pointsAnd show the old result as old, not just quietly ignore it
-9 pointsJane, would you show it under the earlier attempt? We still need its result for the history.
22 pointsYes, when it matches. Unknown identity needs somewhere separate instead of a guessed home.
20 pointsRepeat the sequence across restart. The saved identities must still distinguish A from B afterward.
20 pointsAlso deliver A's completion twice. It should update A once without incrementing the count again or touching B. You've already got the awkward event queued, so that extra case is cheap.
4 pointsDuplicate case added, thanks Luca. Developer is revising the saved attempt identity; restart case still fails.
25 pointsRevised offline cases now keep A and B separate after reopening. An unmatched completion appears in review, not against the latest coupon. Controls still needs to check the real interface supplies the same identity.
25 pointsWho owns unmatched entries on the next shift? The test can preserve uncertainty without resolving that responsibility.
8 pointsThis discussion is closed to new replies after six months without activity. Last activity: .