Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/timacdonald/callable-fake
A PHP testing utility that allows you to fake, capture, and assert against invocations of a callable / Closure.
https://github.com/timacdonald/callable-fake
callable closure hacktoberfest php testing
Last synced: 1 day ago
JSON representation
A PHP testing utility that allows you to fake, capture, and assert against invocations of a callable / Closure.
- Host: GitHub
- URL: https://github.com/timacdonald/callable-fake
- Owner: timacdonald
- License: mit
- Created: 2020-04-05T04:13:27.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2024-06-26T22:29:15.000Z (3 months ago)
- Last Synced: 2024-09-28T00:27:58.379Z (6 days ago)
- Topics: callable, closure, hacktoberfest, php, testing
- Language: PHP
- Homepage:
- Size: 1.2 MB
- Stars: 45
- Watchers: 3
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: readme.md
- License: license.txt
Awesome Lists containing this project
README
# Callable / Closure testing fake
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.
## Installation
You can install the package using [composer](https://getcomposer.org/):
```
composer require timacdonald/callable-fake --dev
```
## Basic usage
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...
```php
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.
### Before
Let's see what the a test for this method might look like...
```php
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]));
}
```
### After
```php
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]);
});
}
```
## Available assertions
All assertions are chainable.
### assertCalled(callable $callback): self
```php
$callable->assertCalled(function (Dependency $dependency): bool {
return Str::startsWith($dependency->name, 'spatie/');
});
```
### assertNotCalled(callable $callback): self
```php
$callable->assertNotCalled(function (Dependency $dependency): bool {
return Str::startsWith($dependency->name, 'timacdonald/');
});
```
### assertCalledIndex(callable $callback, int|array $index): self
Ensure the callable was called in an explicit order, i.e. it was called as the 0th and 5th invocation.
```php
$callable->assertCalledIndex(function (Dependency $dependency): bool {
return Str::startsWith($dependency, 'spatie/');
}, [0, 5]);
```
### assertCalledTimes(callable $callback, int $times): self
```php
$callable->assertCalledTimes(function (Dependency $dependency): bool {
return Str::startsWith($dependency, 'spatie/');
}, 999);
```
### assertTimesInvoked(int $times): self
```php
$callable->assertTimesInvoked(2);
```
### assertInvoked(): self
```php
$callable->assertInvoked();
```
### assertNotInvoked(): self
```php
$callable->assertNotInvoked();
```
## Non-assertion API
### asClosure(): Closure
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`.
```php
$callable = new CallableFake;
$thing->closureTypeHintedMethod($callable->asClosure());
$callable->assertInvoked();
```
### wasInvoked(): bool
```php
if ($callable->wasInvoked()) {
//
}
```
### wasNotInvoked(): bool
```php
if ($callable->wasNotInvoked()) {
//
}
```
### called(callable $callback): array
```php
$invocationArguments = $callable->called(function (Dependency $dependency): bool {
return Str::startsWith($dependency->name, 'spatie/')
});
```
## Specifying return values
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`.
```php
$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 === '🤠';
```
## Credits
- [Tim MacDonald](https://github.com/timacdonald)
- [All Contributors](../../contributors)
And a special (vegi) thanks to [Caneco](https://twitter.com/caneco) for the logo ✨
## Thanksware
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.