I would like to see some improvements in the saga test support for Axon 3.x. My saga is responsible for scheduling events based on a scheduling configuration.
Let’s say the configuration claims that every day an event should occur at 07:00, 14:00 and 19:00 o’clock. When the saga is started it looks for the next scheduling time and schedules and event. The saga is registered to this event and when the event is due, the saga handles it by scheduling the next event. This is done infinitely until the saga is ended.
Start Event±---->Saga±------>scheduled event(s)