Na}{

Server IP: 162.55.243.250

Your IP: 216.73.216.133

Web Server: LiteSpeed

System: Linux sys09.prosuperservers.com 4.18.0-553.5.1.lve.1.el8.x86_64 #1 SMP Fri Jun 14 15:38:45 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

User: rituserver

PHP Version: 8.1.33

Disable Function: mail

MySQL: OFF

cURL: ON

WGET: ON

Perl: ON

Python: OFF

Sudo: OFF

Pkexec: OFF

File Content: `reserved_method_names.rst`

.. index::
    single: Reserved Method Names

Reserved Method Names
=====================

As you may have noticed, Mockery uses a number of methods called directly on
all mock objects, for example ``shouldReceive()``. Such methods are necessary
in order to setup expectations on the given mock, and so they cannot be
implemented on the classes or objects being mocked without creating a method
name collision (reported as a PHP fatal error). The methods reserved by
Mockery are:

* ``shouldReceive()``
* ``shouldNotReceive()``
* ``allows()``
* ``expects()``
* ``shouldAllowMockingMethod()``
* ``shouldIgnoreMissing()``
* ``asUndefined()``
* ``shouldAllowMockingProtectedMethods()``
* ``makePartial()``
* ``byDefault()``
* ``shouldHaveReceived()``
* ``shouldHaveBeenCalled()``
* ``shouldNotHaveReceived()``
* ``shouldNotHaveBeenCalled()``


In addition, all mocks utilise a set of added methods and protected properties
which cannot exist on the class or object being mocked. These are far less
likely to cause collisions. All properties are prefixed with ``_mockery`` and
all method names with ``mockery_``.

Name	Size	Permission
configuration.rst	3998 bytes	0644
exceptions.rst	2671 bytes	0644
gotchas.rst	2463 bytes	0644
index.rst	141 bytes	0644
map.rst.inc	127 bytes	0644
reserved_method_names.rst	1109 bytes	0644

Command Bosku:

File Content: reserved_method_names.rst

Login

File Content: `reserved_method_names.rst`