aDriv4 website!

Linux premium294.web-hosting.com 4.18.0-553.45.1.lve.el8.x86_64 #1 SMP Wed Mar 26 12:08:09 UTC 2025 x86_64
LiteSpeed
66.29.137.213

File Name : not_calling_the_constructor.rst

.. index::
    single: Cookbook; Not Calling the Original Constructor

Not Calling the Original Constructor
====================================

When creating generated partial test doubles, Mockery mocks out only the method
which we specifically told it to. This means that the original constructor of
the class we are mocking will be called.

In some cases this is not a desired behavior, as the constructor might issue
calls to other methods, or other object collaborators, and as such, can create
undesired side-effects in the application's environment when running the tests.

If this happens, we need to use runtime partial test doubles, as they don't
call the original constructor.

.. code-block:: php

class MyClass
    {
        public function __construct()
        {
            echo "Original constructor called." . PHP_EOL;
            // Other side-effects can happen...
        }
    }

// This will print "Original constructor called."
    $mock = \Mockery::mock('MyClass[foo]');

A better approach is to use runtime partial doubles:

.. code-block:: php

class MyClass
    {
        public function __construct()
        {
            echo "Original constructor called." . PHP_EOL;
            // Other side-effects can happen...
        }
    }

// This will not print anything
    $mock = \Mockery::mock('MyClass')->makePartial();
    $mock->shouldReceive('foo');

This is one of the reason why we don't recommend using generated partial test
doubles, but if possible, always use the runtime partials.

Read more about :ref:`creating-test-doubles-partial-test-doubles`.

.. note::

The way generated partial test doubles work, is a BC break. If you use a
    really old version of Mockery, it might behave in a way that the constructor
    is not being called for these generated partials. In the case if you upgrade
    to a more recent version of Mockery, you'll probably have to change your
    tests to use runtime partials, instead of generated ones.

This change was introduced in early 2013, so it is highly unlikely that you
    are using a Mockery from before that, so this should not be an issue.

Name	Type	Size	Owner/Group	Permission	Last Modified	Actions
.	dir	-	tecnsujc/tecnsujc	0755	2025-06-12 02:34:08
..	dir	-	tecnsujc/tecnsujc	0755	2025-06-12 02:34:08
big_parent_class.rst	text/plain	1.63 KB	tecnsujc/tecnsujc	0644	2024-05-16 03:13:14
class_constants.rst	text/plain	4.57 KB	tecnsujc/tecnsujc	0644	2024-05-16 03:13:14
default_expectations.rst	text/plain	757 B	tecnsujc/tecnsujc	0644	2024-05-16 03:13:14
detecting_mock_objects.rst	text/plain	394 B	tecnsujc/tecnsujc	0644	2024-05-16 03:13:14
index.rst	text/plain	273 B	tecnsujc/tecnsujc	0644	2024-05-16 03:13:14
map.rst.inc	text/plain	275 B	tecnsujc/tecnsujc	0644	2024-05-16 03:13:14
mockery_on.rst	application/javascript	2.98 KB	tecnsujc/tecnsujc	0644	2024-05-16 03:13:14
mocking_class_within_class.rst	text/plain	4.31 KB	tecnsujc/tecnsujc	0644	2024-05-16 03:13:14
mocking_hard_dependencies.rst	text/plain	4.37 KB	tecnsujc/tecnsujc	0644	2024-05-16 03:13:14
not_calling_the_constructor.rst	text/plain	2.1 KB	tecnsujc/tecnsujc	0644	2024-05-16 03:13:14

For more Private tool come to me!

https://t.me/aDriv4vz