E2E test: Subscribe with OffsetSpec::offset(N) — resume from specific offset#308
Closed
E2E test: Subscribe with OffsetSpec::offset(N) — resume from specific offset#308
Conversation
…153 Add three test methods to SubscribeTest.php: - testSubscribeFromSpecificOffset(): verifies subscribing from offset 5 receives messages 5-9 - testSubscribeFromOffsetZero(): verifies offset 0 behaves like first() - testSubscribeFromOffsetBeyondEnd(): verifies behavior when offset exceeds stream length Tests follow the established pattern from OsirisChunkParserE2ETest and validate the primary production use case for stream consumers (resuming from stored offset).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #153
Problem
SubscribeTestcoversOffsetSpec::first(),last(), andnext(), but never testsOffsetSpec::offset(N)with a concrete offset value. This is the most common production scenario — consumers resuming from a stored offset after restart.Expected test
Why it matters
OffsetSpec::offset()serializes differently (TYPE_OFFSET = 0x0004 with uint64 value)Acceptance criteria
first())