Mockery Global Configuration¶
To allow for a degree of fine-tuning, Mockery utilises a singleton configuration object to store a small subset of core behaviours. The three currently present include:
- Option to allow/disallow the mocking of methods which do not actually exist fulfilled (i.e. unused)
- Setter/Getter for added a parameter map for internal PHP class methods
Reflectioncannot detect these automatically)
By default, the first behaviour is enabled. Of course, there are situations where this can lead to unintended consequences. The mocking of non-existent methods may allow mocks based on real classes/objects to fall out of sync with the actual implementations, especially when some degree of integration testing (testing of object wiring) is not being performed.
You may allow or disallow this behaviour (whether for whole test suites or just select tests) by using the following call:
Passing a true allows the behaviour, false disallows it. It takes effect immediately until switched back. If the behaviour is detected when not allowed, it will result in an Exception being thrown at that point. Note that disallowing ths behaviour should be carefully considered since it necessarily removes at least some of Mockery’s flexibility.
The other two methods are:
\Mockery::getConfiguration()->setInternalClassMethodParamMap($class, $method, array $paramMap) \Mockery::getConfiguration()->getInternalClassMethodParamMap($class, $method)
These are used to define parameters (i.e. the signature string of each) for the
methods of internal PHP classes (e.g. SPL, or PECL extension classes like
ext/mongo’s MongoCollection. Reflection cannot analyse the parameters of internal
classes. Most of the time, you never need to do this. It’s mainly needed where an
internal class method uses pass-by-reference for a parameter - you MUST in such
cases ensure the parameter signature includes the
& symbol correctly as Mockery
won’t correctly add it automatically for internal classes.