Close outbox seam test-coverage gaps#344
Merged
Merged
Conversation
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.
Summary
BrokerOutboxDispatcher/TransactionalPublishFilter coverage for happy publish/send
paths, the missing-DestinationAddress error, and EnableTracing fidelity.
failure isolation; every public OutboxProcessingOptions toggle now has at least one
behavioral test (EnableMetrics and Retention.* were the remaining gaps).
transaction is actually relayed and consumed with its stable message id preserved,
and a rolled-back transaction is never relayed.
Verification
passed (net9.0, net10.0); Docker was available and the new relay tests ran for real.
Backport to v1.0: no — test-only additions ship with the next release.