Projectors and Reactors still trigger in tests despite using Event::fake() about laravel-event-sourcing HOT 6 CLOSED

I also have the same issue which is manifesting itself by the test failing because an aggregate UUID isn't being supplied to the projector.

Ideally Event::fake() would solve this by not allowing the projectors to run, however regardless of whether the fake() method is called in the setUp in the test or just before the actual test case it still runs.

TypeError : Argument 2 passed to App\Projectors\InvoiceProjector::onRaiseFirstInvoice() must be of the type string, null given

I notice that this is when using the given method as below:

BookingAggregate::fake()
            ->given(new RaiseFirstInvoice)
            ->when(function (BookingAggregate $aggregate) {
                $aggregate->raiseInvoice();
            })
            ->assertRecorded(new RaiseSecondInvoice)
            ->assertNotRecorded([
                RaiseFirstInvoice::class,
                RaiseRegularInvoice::class,
            ]);

The tests run fine if I remove the Projector.

from laravel-event-sourcing.

Took a quick look at the Spatie\EventSourcing\Projectionist Class and right now it seems that the Spatie\EventSourcing\Projectionist::withoutEventHandlers method suits this case. When I call the method (app(Spatie\EventSourcing\Projectionist::class)->withoutEventHandlers()) before faking the Aggregate the Projectors and Reactors of course do not get triggered. Facade usage \Spatie\EventSourcing\Facades\Projectionist::withoutEventHandlers(); is possible too.

This only works when you don't want any Projectors and Reactors to be triggered.

from laravel-event-sourcing.

Does calling withoutEventHandlers() fix all the issues you're having? Or is there still some unexpected behaviour?

from laravel-event-sourcing.

Right now it does fix the issue for me. Couldn't come up with a test scenario where this won't work as we can just trigger manually generated Events to test Projections and Reactions.

But it would be nice to have an option (like retrieve) to supply a UUID to the FakeAggregateRoot in case they are needed for Projections in Integration/Feature Tests. That would also solve @danielwaghorn issue with the Aggregate UUID not being supplied to the Projector.

from laravel-event-sourcing.

I can confirm that adding Projectionist::withoutEventHandlers(); lets my tests run successfully. This works for me as I'm just testing the Aggregate as a unit. If I'm doing an integration test I tend to want the events handled by the Projectors and therefore present in the database to assert against.

Is this worth me making a PR to the docs to suggest this as a suitable means of disabling projectors rather than Event::fake()?

from laravel-event-sourcing.

Feel free to do so! I'd suggest just adding the Projectionist::withoutEventHandlers(); part with some extra explanation, the Event::fake() can still be used to prevent storing the events as that uses Laravel's event system

from laravel-event-sourcing.