Linux unitednationsplay.com 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64
nginx/1.20.1
Server IP : 188.130.139.92 & Your IP : 18.222.227.24
Domains :
Cant Read [ /etc/named.conf ]
User : web
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
home /
www /
3 /
mockery /
mockery /
docs /
mockery /
Delete
Unzip
Name
Size
Permission
Date
Action
configuration.rst
3.05
KB
-rw-r--r--
2018-10-02 09:00
exceptions.rst
2.61
KB
-rw-r--r--
2018-10-02 09:00
gotchas.rst
2.6
KB
-rw-r--r--
2018-10-02 09:00
index.rst
141
B
-rw-r--r--
2018-10-02 09:00
map.rst.inc
127
B
-rw-r--r--
2018-10-02 09:00
reserved_method_names.rst
795
B
-rw-r--r--
2018-10-02 09:00
Save
Rename
.. 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()`` * ``shouldBeStrict()`` 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_``.