File Manager Lite
Dir:
/home/codewavebd/public_html/vendor/mockery/mockery/docs/reference
Upload
[..]
alternative_should_receive_syntax.rst (2.33 KB)
Edit
Rename
Del
argument_validation.rst (10.49 KB)
Edit
Rename
Del
creating_test_doubles.rst (14.12 KB)
Edit
Rename
Del
demeter_chains.rst (1.6 KB)
Edit
Rename
Del
expectations.rst (15.57 KB)
Edit
Rename
Del
index.rst (421 B)
Edit
Rename
Del
magic_methods.rst (687 B)
Edit
Rename
Del
map.rst.inc (550 B)
Edit
Rename
Del
partial_mocks.rst (4.19 KB)
Edit
Rename
Del
pass_by_reference_behaviours.rst (4.22 KB)
Edit
Rename
Del
public_properties.rst (821 B)
Edit
Rename
Del
public_static_properties.rst (701 B)
Edit
Rename
Del
spies.rst (4.63 KB)
Edit
Rename
Del
Edit: magic_methods.rst
.. 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.
Simpan