Changing projectors / reactors dependency implementations during tests

[talvbansal]

Changing projectors / reactors dependency implementations during tests

[sebastiandedeyne]

Maybe we should register event handlers after the app is booted @freekmurze?

[freekmurze]

I'd accept a PR that moved the registration to the boot method.

[talvbansal]

@sebastiandedeyne I've just tried moving this code

$this->app->singleton(Projectionist::class, function () {
            $config = config('event-projector');

            $projectionist = new Projectionist($config);

            $projectionist
                ->addProjectors($config['projectors'] ?? [])
                ->addReactors($config['reactors'] ?? []);

            return $projectionist;
        });

from the register to the boot method, but theres no change in the functionality. I assume by the time we're at the first line of a test method the app has finished registered and booted even if the test is blank.

I can't think of an obvious way to hook into the app lifecycle to swap Fakes in during tests unless I'm missing something obvious. If there is something please point me in the right direction and ill take another look.

As a work around for now I'm doing the following in my tests:

• Swapping the implementation for a fake
• Fetching the Projectionist from the app container
• Re-adding the reactor and overwriting its key held within the EventHandlerCollection.

        $this->app->singleton(ClaimsManagementNotifier::class, function () use ($fakeRequests) {
            $mock = new MockHandler($fakeRequests);

            $handler = HandlerStack::create($mock);
            $client = new \GuzzleHttp\Client(['handler' => $handler]);

            return new ClaimsManagementNotifier($client);
        });

        /** @var Projectionist $projectionist */
        $projectionist = $this->app->make(Projectionist::class);
        $projectionist->addReactor(AppClaimReactor::class);

[spatie-bot]

Dear contributor,

because this issue seems to be inactive for quite some time now, I've automatically closed it. If you feel this issue deserves some attention from my human colleagues feel free to reopen it.