Summary
Add documentation with examples showing how to test sagas using Wolverine's TrackedSession and existing testing infrastructure.
Background (Gap Analysis)
NServiceBus has a dedicated saga scenario testing library with virtual storage and virtual time. Rebus has SagaFixture. Wolverine's TrackedSession already covers these scenarios but could benefit from clearer documentation.
Proposed Content
- How to set up saga integration tests with
TrackedSession
- Testing saga state transitions across multiple messages
- Testing saga timeouts and scheduled messages
- Asserting on sent/published messages from saga handlers
- Common patterns and best practices
- Comparison note explaining how TrackedSession maps to NServiceBus/Rebus saga testing concepts
Identified via gap analysis comparing Wolverine to NServiceBus, MassTransit, Rebus, Brighter, MuleSoft, Neuron ESB, and Apache Camel.
Summary
Add documentation with examples showing how to test sagas using Wolverine's
TrackedSessionand existing testing infrastructure.Background (Gap Analysis)
NServiceBus has a dedicated saga scenario testing library with virtual storage and virtual time. Rebus has
SagaFixture. Wolverine'sTrackedSessionalready covers these scenarios but could benefit from clearer documentation.Proposed Content
TrackedSessionIdentified via gap analysis comparing Wolverine to NServiceBus, MassTransit, Rebus, Brighter, MuleSoft, Neuron ESB, and Apache Camel.