What problem does it solve? Writing integration tests for message subscribers often requires a live Service Bus connection and ad-hoc setup, making tests slow, fragile, and inconsistent. This Skill guides you through testing CoreEx Subscribe hosts against a real database, cache, and outbox by simulating broker message receipt in-process. ## Core Features & Use Cases - Simulated Message Receipt: Build an EventData, convert it to a ServiceBusReceivedMessage, and invoke ServiceBusSubscribedSubscriber.ReceiveAsync without any live broker connection. - Scenario-Matched Test Shapes: Provides distinct patterns for command subscribers (outcome plus outbox assertions), event-data-sync subscribers (local state assertions via the sync adapter), and event-business-process subscribers (downstream service and event assertions). - ErrorHandler and Plumbing Assertions: Assert handled-exception outcomes via EventSubscriberHandledException and verify unsubscribed subjects complete silently rather than being dead-lettered. - Use Case: After implementing a reservation-confirm command subscriber, generate a SubscriberTests partial class that seeds the database, simulates the command message, and asserts the expected outbox events and state changes. ## Quick Start Write an integration test for my reservation-confirm command subscriber that simulates the message receipt and asserts the resulting outbox events.
