If you have an interface who's public API allows a developer to pass a Closure / callable, but causes no internal or external side-effects, as these are left up to the developer using the interface, this package may assist in testing. This class adds some named assertions which gives you an API that is very much inspired by Laravel's service fakes. It may be a little more verbose, but it changes the language of the tests to better reflect what is going on.
It also makes it easy to assert the order of invocations, and how many times a callable has been invoked.
You can install the package using composer:
composer require timacdonald/callable-fake --dev
This packge requires you to be testing a pretty specfic type of API / interaction to be useful. Imagine you are developing a package that ships with the following interface...
interface DependencyRepository
{
public function each(callable $callback): void;
}
This interface accepts a callback, and under the hood loops through all "dependecies" and passes each one to the callback for the developer to work with.
Let's see what the a test for this method might look like...
public function testEachLoopsOverAllDependencies(): void
{
// arrange
$received = [];
$expected = factory(Dependency::class)->times(2)->create();
$repo = $this->app[DependencyRepository::class];
// act
$repo->each(function (Dependency $dependency) use (&$received): void {
$received[] = $dependency;
});
// assert
$this->assertCount(2, $received);
$this->assertTrue($expected[0]->is($received[0]));
$this->assertTrue($expected[1]->is($received[1]));
}
public function testEachLoopsOverAllDependencies(): void
{
// arrange
$callable = new CallableFake();
$expected = factory(Dependency::class)->times(2)->create();
$repo = $this->app[DependencyRepository::class];
// act
$repo->each($callable);
// assert
$callable->assertTimesInvoked(2);
$callable->assertCalled(function (Depedency $dependency) use ($expected): bool {
return $dependency->is($expected[0]);
});
$callable->assertCalled(function (Dependency $dependency) use ($expected): bool {
return $dependency->is($expected[1]);
});
}
All assertions are chainable.
$callable->assertCalled(function (Dependency $dependency): bool {
return Str::startsWith($dependency->name, 'spatie/');
});
$callable->assertNotCalled(function (Dependency $dependency): bool {
return Str::startsWith($dependency->name, 'timacdonald/');
});
Ensure the callable was called in an explicit order, i.e. it was called as the 0th and 5th invocation.
$callable->assertCalledIndex(function (Dependency $dependency): bool {
return Str::startsWith($dependency, 'spatie/');
}, [0, 5]);
$callable->assertCalledTimes(function (Dependency $dependency): bool {
return Str::startsWith($dependency, 'spatie/');
}, 999);
$callable->assertTimesInvoked(2);
$callable->assertInvoked();
$callable->assertNotInvoked();
If the method is type-hinted with \Closure
instead of callable, you can use this method to transform the callable to an instance of \Closure
.
$callable = new CallableFake;
$thing->closureTypeHintedMethod($callable->asClosure());
$callable->assertInvoked();
if ($callable->wasInvoked()) {
//
}
if ($callable->wasNotInvoked()) {
//
}
$invocationArguments = $callable->called(function (Dependency $dependency): bool {
return Str::startsWith($dependency->name, 'spatie/')
});
If you need to specify return values, this could be an indicator that this is not the right tool for the job. But there are some cases where return values determine control flow, so it can be handy, in which case you can pass a "return resolver" to the named constructor withReturnResolver
.
$callable = CallableFake::withReturnResolver(function (Dependency $dependency): bool {
if ($dependency->version === '*') {
return '🤠';
}
return '😀';
});
// You would not generally be calling this yourself, this is simply to demonstate
// what will happen under the hood...
$emoji = $callable(new Dependecy(['version' => '*']));
// $emoji === '🤠';
And a special (vegi) thanks to Caneco for the logo ✨
You are free to use this package, but I ask that you reach out to someone (not me) who has previously, or is currently, maintaining or contributing to an open source library you are using in your project and thank them for their work. Consider your entire tech stack: packages, frameworks, languages, databases, operating systems, frontend, backend, etc.