Name	Size	Mode	Actions
alternative_should_receive_syntax.rst	2381	0644	editdlrm
argument_validation.rst	10745	0644	editdlrm
creating_test_doubles.rst	14462	0644	editdlrm
demeter_chains.rst	1639	0644	editdlrm
expectations.rst	15946	0644	editdlrm
final_methods_classes.rst	1351	0644	editdlrm
index.rst	421	0644	editdlrm
instance_mocking.rst	805	0644	editdlrm
magic_methods.rst	687	0644	editdlrm
map.rst.inc	550	0644	editdlrm
partial_mocks.rst	4286	0644	editdlrm
pass_by_reference_behaviours.rst	4322	0644	editdlrm
phpunit_integration.rst	4853	0644	editdlrm
protected_methods.rst	668	0644	editdlrm
public_properties.rst	821	0644	editdlrm
public_static_properties.rst	701	0644	editdlrm
spies.rst	4736	0644	editdlrm

.. index:: single: Mocking; Magic Methods PHP Magic Methods ================= PHP magic methods which are prefixed with a double underscore, e.g. ``__set()``, pose a particular problem in mocking and unit testing in general. It is strongly recommended that unit tests and mock objects do not directly refer to magic methods. Instead, refer only to the virtual methods and properties these magic methods simulate. Following this piece of advice will ensure we are testing the real API of classes and also ensures there is no conflict should Mockery override these magic methods, which it will inevitably do in order to support its role in intercepting method calls and properties.