Testing with multiple AggregateRoot about eventsauce HOT 3 CLOSED

So the first one seems relatively straight forward to resolve from what I can see here. The CategoryCreated event should have a categoryId, so you test it like this:

public function test_adding_a_person_to_an_event_with_category()
{
    $categoryId = uuid();

    $this->given(
        new EventStarted(),
        new CategoryCreated($categoryId)
    )->when(
        new AddPerson($this->aggregateRootId, $categoryId), // <- what is $categoryId?
    )->then(
        new PersonAdded(),
    );
}

The trick for this to always have deterministic identifiers. Your command to create the category should contain the ID to create it and the corresponding event should have to ID for future reference. For the other case, you've got two models that interact with each other. For this, you can use a process manager that listens to events from one aggregate and act on the other. Process managers are explained in the docs and are basically just consumers of messages that, instead of accumulating state, act. So to test this you have your first aggregate, test it in isolation. Test the process manager (only needs to forward the calls) and then test the person aggregate. You shouldn't want to capture this in one test because it's a different unit of isolation. Let me know if this helps, if not we can discuss further.

from eventsauce.

The first one makes sense that way.

On the last one; I've discussed it with my team too, that it makes sense to be able to test each aggregate in isolation. However, due to invariants being as much as across the entire domain, we were confused with how to split up the aggregates and how to test these.

Thank you for you quick response @frankdejonge, we'll explore this and report back with our solution.

from eventsauce.

Closing this for inactivity, can be re-opened later if needed.

from eventsauce.