In the previous post, I walked through the compensation logic in each service. The code looks clean on paper. But sagas have a lot of moving parts, and bugs tend to hide in the transitions between services, not inside a single service. This post covers how I test the saga system: unit tests for each service, orchestrator routing tests, and the edge cases that caught me off guard. Testing the Orchestrator Routing The orchestrator's state transition table is the most critical piece. If it routes to the wrong topic, the entire saga breaks. I test every (source, status) combination: @Test void shouldReturnNextTopicGivenValidSourceAndSuccessStatus () { setEvent ( PAYMENT_SERVICE . toString (), SUCCESS ); TopicsEnum topic = sagaExecutionController . getNextTopic ( event ); assertEquals ( INVENTORY_SUCCESS , topic ); } @Test void shouldReturnFailTopicGivenValidSourceAndFailStatus () { setEvent ( PAYMENT_SERVICE . toString (), FAIL ); TopicsEnum topic = sagaExecutionController .…