patchlevel / event-sourcing-phpunit
PHPUnit testing utilities for patchlevel/event-sourcing
Requires
- php: ~8.2.0 || ~8.3.0
- patchlevel/event-sourcing: ^3.8.0
- phpunit/phpunit: ^10.1.0||^11.0.0
Requires (Dev)
- infection/infection: ^0.29.0
- patchlevel/coding-standard: ^1.3.0
- phpstan/phpstan: ^2.1.0
This package is auto-updated.
Last update: 2025-02-22 11:12:05 UTC
README
Testing utilities
With this library you can ease the testing for your event-sourcing project when using PHPUnit. It comes with utilities for aggregates and subscribers.
Installation
composer require --dev patchlevel/event-sourcing-phpunit
Testing Aggregates
There is a special TestCase
for aggregate tests which you can extend from. Extending from AggregateRootTestCase
enables you to use the given / when / then notation. This makes it very clear what the test is doing. When extending the
class you will need to implement a method which provides the FQCN of the aggregate you want to test.
final class ProfileTest extends AggregateRootTestCase { protected function aggregateClass(): string { return Profile::class; } }
When this is done, you already can start testing your behaviour. For example testing that a event is recorded.
final class ProfileTest extends AggregateRootTestCase { // protected function aggregateClass(): string; public function testBehaviour(): void { $this ->given( new ProfileCreated( ProfileId::fromString('1'), Email::fromString('hq@patchlevel.de'), ), ) ->when(static fn (Profile $profile) => $profile->visitProfile(ProfileId::fromString('2'))) ->then(new ProfileVisited(ProfileId::fromString('2'))); } }
You can also provide multiple given events and expect multiple events:
final class ProfileTest extends AggregateRootTestCase { // protected function aggregateClass(): string; public function testBehaviour(): void { $this ->given( new ProfileCreated( ProfileId::fromString('1'), Email::fromString('hq@patchlevel.de'), ), new ProfileVisited(ProfileId::fromString('2')), ) ->when( static function (Profile $profile) { $profile->visitProfile(ProfileId::fromString('3')); $profile->visitProfile(ProfileId::fromString('4')); } ) ->then( new ProfileVisited(ProfileId::fromString('3')), new ProfileVisited(ProfileId::fromString('4')), ); } }
You can also test the creation of the aggregate:
final class ProfileTest extends AggregateRootTestCase { // protected function aggregateClass(): string; public function testBehaviour(): void { $this ->when(static fn () => Profile::createProfile(ProfileId::fromString('1'), Email::fromString('hq@patchlevel.de'))) ->then(new ProfileCreated(ProfileId::fromString('1'), Email::fromString('hq@patchlevel.de'))); } }
And expect an exception and the message of it:
final class ProfileTest extends AggregateRootTestCase { // protected function aggregateClass(): string; public function testBehaviour(): void { $this ->given( new ProfileCreated( ProfileId::fromString('1'), Email::fromString('hq@patchlevel.de'), ), ) ->when(static fn (Profile $profile) => $profile->throwException()) ->expectsException(ProfileError::class) ->expectsExceptionMessage('throwing so that you can catch it!'); } }
Using Commandbus like syntax
When using the command bus and the #[Handle]
attributes in your aggregate you can also provide the command directly
for the when
method.
final class ProfileTest extends AggregateRootTestCase { // protected function aggregateClass(): string; public function testBehaviour(): void { $this ->when(new CreateProfile(ProfileId::fromString('1'), Email::fromString('hq@patchlevel.de'))) ->then(new ProfileCreated(ProfileId::fromString('1'), Email::fromString('hq@patchlevel.de'))); } }
If more parameters than the command is needed, these can also be provided as additional parameters for when
. In this
example the we need a string which will be directly passed to the event.
final class ProfileTest extends AggregateRootTestCase { // protected function aggregateClass(): string; public function testBehaviour(): void { $this ->given( new ProfileCreated( ProfileId::fromString('1'), Email::fromString('hq@patchlevel.de'), ), ) ->when(new VisitProfile(ProfileId::fromString('2')), 'Extra Parameter / Dependency') ->then(new ProfileVisited(ProfileId::fromString('2'), 'Extra Parameter / Dependency')); } }
Testing Subscriber
For testing a subscriber there is a utility class which you can use. Using SubscriberUtilities
will provide you a
bunch of dx features which makes the testing easier. First, you will need to provide the utility class the subscriptions
you will want to test, this is done when initialiszing the class. After that, you can call these 3 methods:
executeSetup
, executeRun
and executeTeardown
. These methods will be calling the right methods which are defined
via the attributes. For our example we are taking as simplified subscriber:
use Patchlevel\EventSourcing\Attribute\Setup; use Patchlevel\EventSourcing\Attribute\Subscribe; use Patchlevel\EventSourcing\Attribute\Subscriber; use Patchlevel\EventSourcing\Attribute\Teardown; #[Subscriber('profile_subscriber', RunMode::FromBeginning)] final class ProfileSubscriber { public int $called = 0; #[Subscribe(ProfileCreated::class)] public function run(): void { $this->called++; } #[Setup] public function setup(): void { $this->called++; } #[Teardown] public function teardown(): void { $this->called++; } }
With this, we can now write our test for it:
use Patchlevel\EventSourcing\Attribute\Subscriber; use Patchlevel\EventSourcing\Subscription\RunMode; use Patchlevel\EventSourcing\PhpUnit\Test\SubscriberUtilities; final class ProfileSubscriberTest extends TestCase { use SubscriberUtilities; public function testProfileCreated(): void { $subscriber = new ProfileSubscriber(/* inject deps, if needed */); $util = new SubscriberUtilities($subscriber); $util->executeSetup(); $util->executeRun( new ProfileCreated( ProfileId::fromString('1'), Email::fromString('hq@patchlevel.de'), ) ); $util->executeTeardown(); self::assertSame(3, $subscriber->count); } }
This Util class can be used for integration or unit tests.