Test Affordances

[DanielCoulbourne]

Adds Verbs::commitImmediately()

You can call Verbs::commitImmediately() in your tests to commit on every fire(). This is an ergonomic improvement for tests where calling Verbs::commit() after each event and testing the projections was a pain.

When app()->isRunningUnitTests() is false, calling Verbs::commitImmediately() will throw a RuntimeException. If you really know what you are doing, you can allow commitImmediately outside your tests by setting config('verbs.allow_commit_immediately_outside_tests') to true

Adds $event->verbs_should_commit_immediately

You can set the protected bool $verbs_should_commit_immediately property on any Event. This will cause Verbs to commit immediately when firing this event.

Adds State::factory() method and VerbsStateInitialized event.

This allows you to call:

BankAccountState::factory(
    data: ['balance' => 1337]
    id: $bank_account_id
);

or in the case of a singleton state:

ChurnState::factory(['churn' => 40]);

Calling these methods will fire (and immediately commit) a new VerbsStateInitialized event, which will fire onto the given state, identified by the id argument (if id is null, we assume it is a singleton) and return a copy of that state.

This is primarily designed for booting up states for testing, but it may also be useful in migrating non event-sourced codebases to Verbs, when there is a need to initiate a state for legacy data.