Name	Size	Mode	Actions
alternative_should_receive_syntax.rst	2381	0644	editdlrm
argument_validation.rst	10743	0644	editdlrm
creating_test_doubles.rst	14461	0644	editdlrm
demeter_chains.rst	1639	0644	editdlrm
expectations.rst	15126	0644	editdlrm
final_methods_classes.rst	1319	0644	editdlrm
index.rst	400	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	5005	0644	editdlrm
protected_methods.rst	668	0644	editdlrm
public_properties.rst	821	0644	editdlrm
public_static_properties.rst	701	0644	editdlrm
spies.rst	4737	0644	editdlrm

.. index:: single: Mocking; Final Classes/Methods Dealing with Final Classes/Methods ================================== One of the primary restrictions of mock objects in PHP, is that mocking classes or methods marked final is hard. The final keyword prevents methods so marked from being replaced in subclasses (subclassing is how mock objects can inherit the type of the class or object being mocked). The simplest solution is to not mark classes or methods as final! However, in a compromise between mocking functionality and type safety, Mockery does allow creating "proxy mocks" from classes marked final, or from classes with methods marked final. This offers all the usual mock object goodness but the resulting mock will not inherit the class type of the object being mocked, i.e. it will not pass any instanceof comparison. Methods marked as final will be proxied to the original method, i.e., final methods can't be mocked. We can create a proxy mock by passing the instantiated object we wish to mock into ``\Mockery::mock()``, i.e. Mockery will then generate a Proxy to the real object and selectively intercept method calls for the purposes of setting and meeting expectations. See the :ref:`creating-test-doubles-partial-test-doubles` chapter, the subsection about proxied partial test doubles.