Wallogit.com
2017 © Pedro Peláez
PHPunit mock fixtures
, (*1)
Still not 100% stable. Use with caution, (*2)
Quoting from phpunit:, (*3)
Sometimes it is just plain hard to test the system under test (SUT) because it depends on other components that cannot be used in the test environment. This could be because they aren't available, they will not return the results needed for the test or because executing them would have undesirable side effects. In other cases, our test strategy requires us to have more control or visibility of the internal behavior of the SUT., (*4)
When we are writing a test in which we cannot (or chose not to) use a real depended-on component (DOC), we can replace it with a Test Double. The Test Double doesn't have to behave exactly like the real DOC; it merely has to provide the same API as the real one so that the SUT thinks it is the real one!, (*5)
It is almost impossible to write good tests without stubbing objects, because we often need to imitate writing to a database or calling an external service., (*6)
Amock lets you create these stub objects in yaml instead of "polluting" your tests with irrelevant code., (*7)
composer require --dev thanos-kontos/amock, (*8)
Add a directory to store your fixtures e.g. tests/mock_fixtures and as as many yaml files as you want., (*9)
# tests/mock_fixtures/repositories.yml
MyProject\Library\UserRepository:
mockUserRepository:
disableConstructor: true
mockMethods:
insert: '@null'
update: '@null'
MyProject\Library\ProductRepository:
mockProductRepository:
disableConstructor: true
mockMethods:
insert: '@null'
update: '@null'
# tests/mock_fixtures/gateways.yml
MyProject\Library\SomeApiGateway:
mockSuccessResponse:
disableConstructor: true
mockMethods:
getHelloReponse: '@string:{"hello":"world"}'
mock404Response:
disableConstructor: true
mockMethods:
getHelloReponse: '@string:{"error": "404","message":"Not found"}'
sampleSetter: '@self'
methodThatReturnsDifferentValueOnConsecutiveCalls:
- '@string:{"hello":"world"}'
- '@integer:123'
- '@boolean:false'
methodThatReturnsArray: '@array:{"111":"aaa","222":"bbb"}'
methodThatReturnsBoolean: '@boolean:false'
methodThatReturnsInteger: '@integer:123'
methodThatReturnsNull: '@null'
mockExceptionResponse:
disableConstructor: true
mockMethods:
getHelloReponse: '@exception:\MyProject\Library\Exception\ApiException'
On your test setUp method, (*10)
$config = new \Amock\Configuration('yaml', 'dir', '/path/to/mock_fixtures');
$this->amock = \Amock\Amock::create($config, $testCase);
or, (*11)
$config = new \Amock\Configuration('yaml', 'file', '/path/to/mock_fixtures/somefile.yml');
$this->amock = \Amock\Amock::create($config, $testCase);
Then you can use the configured mocks in your tests:, (*12)
$stub = $this->amock->get('mock404Response');
There is an dummy project here that you can use as a reference., (*13)
Amock is released under the MIT License., (*14)
PHPunit mock fixtures
MIT
test mock phpunit fixture
PHPunit mock fixtures
MIT
test mock phpunit fixture
PHPunit mock fixtures
MIT
test mock phpunit fixture