Integration Testing with Wolverine Added in 1.2.0
End-to-end integration testing for Wolverine: tracked sessions to assert published/sent messages, choosing between stubbed transports and a real broker (DisableAllExternalWolverineTransports uses a NullSender and DROPS explicitly-routed messages, producing a green suite over a system that did nothing), how a tracked session decides it is DONE (conditions replace quiescence rather than adding to it, the 5-second default timeout, untracked external transports, batched messages finishing after the session, DoNotAssertOnTimeout as the only way to suppress the timeout assertion since Wolverine 6.30.1), why InvokeMessageAndWaitAsync rethrows instead of recording, the ways a tracked test goes vacuously green, never sleeping to wait, cascading message chains, waiting for BatchMessagesOf batches before a database reset, scheduled messages, Marten and Polecat event-sourcing tests, IInitialData seeding, DB cleanup, xUnit v2 vs v3 IAsyncLifetime, and solo-mode test hosts.
Use when writing integration tests that verify message handling, routing, and persistence, when a tracked test passes suspiciously fast or proves nothing, or when combining Alba HTTP with Wolverine message tracking.
Skill details
- Skill name:
wolverine-testing-integration - Applies to:
wolverine,marten,polecat - Tags:
testing,integration-testing,tracked-sessions,database,scheduled-messages,polecat,transports,codegen-preview,StubEventStream - Added in: 1.2.0
- License: Proprietary. Copyright JasperFx Software LLC.