AspectMock is a PHP library that allows mocking of any method call, including static and private methods, without requiring code refactoring. It uses aspect-oriented programming to intercept method calls and return mock values. To use it, install via Composer, create a custom autoloader for tests, and define the class and methods to mock along with their return values. AspectMock makes it easy to mock code as written without dependency injection refactoring required by other mocking tools.

1. AspectMock
Making it easier to write unit tests

2. So, yeah, tests are important
“Test code is just as important as production code.”
“… tests enable change”“Code, without tests, is not clean. No matter how elegant it is, no
matter how readable and accessible, if it hath not tests, it be unclean.”
“All software you write will be tested – if not by you and
your team, then by the eventual users.”
“…legacy code is simply code without tests.”
“Code without tests is bad code. … With tests we can change the
behavior of our code quickly and verifiably. Without them, we
really don’t know if our code is getting better or worse.”
From Clean Code by Robert Martin, The Pragmatic Programmer by Andrew Hunt and David Thomas, and Working Effectively With Legacy Code by Michael Feathers

3. If you have trivial methods, tests are easy
Code Test

4. But who has trivial methods?

5. “They” say use Dependency Injection and mocks
Changing the
method’s
signature requires
refactoring all
method calls.
DI does nothing
for static
method calls
https://phpunit.de/manual/current/en/test-doubles.html

6. Or you could write integration tests …
Code Test
Even with integration tests, this
path cannot be tested because it
is a time-sensitive conditional
That’s a lot of work

7. Is there a third option?
A. Refactor all of your code to use Dependency Injections so you can mock dependencies.
B. Write intricate integration tests with heavy setup and teardown
C. ??

8. C. Use AspectMock
• Allows you to mock any method call (static, private, built-in PHP)
• Does not require refactoring existing code
• Installs via Composer (and configure an autoloader for tests)
• Can return a different mock value for each individual test
• Easy to use
• Magical

9. AspectMock mocks your code as it is
Code Test

10. Here’s the basic setup
• Import AspectMockTest
• In tearDown() method, run clean() to
reset the mocks between tests
• Define the class to be mocked, and the
desired results for each of its methods
• Write your test

11. Code
Want a different
value for each
test? Okay
Test

12. RealSample
TestCodeRealSample

13. So, how does it work?
• Relies on Aspect Oriented Programming
• Some concerns cut across classes (security, logging, etc.)
• Identify join points (method invocation, method return)
• Write code that provides advice at designated join points
• AOP code can target methods without cluttering those methods
• Uses PHP implementation of AOP called Go! AOP Framework
(http://go.aopphp.com)

14. Setup
1. Install via Composer
Be sure to include any path
you may mock, and exclude
all test-related paths
2. Create custom autoloader
3. Point phpunit to
special autoloader

15. Ready to try it for yourself?
Website: https://github.com/Codeception/AspectMock