Skip to content

test: push payload assertions accept either callback order - #24

Merged
FelineStateMachine merged 1 commit into
mainfrom
feat/push-test-delivery-order
Sep 5, 2026
Merged

test: push payload assertions accept either callback order#24
FelineStateMachine merged 1 commit into
mainfrom
feat/push-test-delivery-order

Conversation

@FelineStateMachine

Copy link
Copy Markdown
Owner

Motivation

The push payload test assumed its third callback was ID-only. Registration timestamps can reverse the two callbacks, causing a failure even when both deliveries are correct.

Change

Match the second event's deliveries by event ID and exact payload content, preserving total counts, callback URL, normalized relay URL, complete-event content and ID-only privacy assertions. Parameterized fixtures make the ID-only registration older and newer than the full-event registration. Only test/object/push.test.ts changes; production behavior is unchanged.

Testing Completed

  • Both timestamp variants pass in three fresh focused runs (six cases).
  • npm run typecheck passes, including generated-file, console and configuration checks.
  • npm test -- --maxWorkers=1: 49 files, 253 tests pass.

Responsible AI disclosure

Codex authored and validated this test-only follow-up. Human review is requested; no merge or deployment was performed.

Both registration timestamp orders exercise exact full-event and ID-only payload matching while preserving delivery counts and callback identity.
@FelineStateMachine
FelineStateMachine merged commit 622e04b into main Sep 5, 2026
1 check passed
@FelineStateMachine
FelineStateMachine deleted the feat/push-test-delivery-order branch September 5, 2026 00:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant