/home/techb158/dev.balacoffee.com/vendor/mockery/mockery/docs/cookbook
NameSizeModeActions
big_parent_class.rst16720644editdlrm
class_constants.rst46760644editdlrm
default_expectations.rst7570644editdlrm
detecting_mock_objects.rst3940644editdlrm
index.rst2730644editdlrm
map.rst.inc2750644editdlrm
mockery_on.rst30510644editdlrm
mocking_class_within_class.rst44130644editdlrm
mocking_hard_dependencies.rst44720644editdlrm
not_calling_the_constructor.rst21520644editdlrm
Edit: /home/techb158/dev.balacoffee.com/vendor/mockery/mockery/docs/cookbook/default_expectations.rst (757B)
.. index:: single: Cookbook; Default Mock Expectations Default Mock Expectations ========================= Often in unit testing, we end up with sets of tests which use the same object dependency over and over again. Rather than mocking this class/object within every single unit test (requiring a mountain of duplicate code), we can instead define reusable default mocks within the test case's ``setup()`` method. This even works where unit tests use varying expectations on the same or similar mock object. How this works, is that you can define mocks with default expectations. Then, in a later unit test, you can add or fine-tune expectations for that specific test. Any expectation can be set as a default using the ``byDefault()`` declaration.