Let me give my two cents to the situation.
Only the Aggregate creation test works, as that’s the only place where the test’s “given” is set correctly.
FixtureConfiguration#givenNoPriorActivity as only used whenever a new Aggregate is instantiated. That’s what no prior activity is aimed at.
All your other command handlers, so from the snippet the Update and Delete command handlers, do have a given event to source the aggregate for testing.
Hence for those tests, you should use
You should fill that method’s
events parameter with the events you expect to have occurred on the aggregate before handling that command.
As a side note, I’d like to point out that CUD-like commands and events are typically not recommended. The beauty of this message-driven application style is that your commands and events can express the exact adjustments in your application. Things like “patient visited doctor” or “patient address changed.”
Using messages of that format clearly shows to you and your business what’s happening in your app.