Serialization of mocked objects in PHP 7.4

[okdewit]

This snippet of code:

serialize(Mockery::mock(User::class))

works with Mockery 1.3.1, using PHP 7.3.
Using PHP 7.4, keeping all else equal, it gives the exception:

Exception : Serialization of 'ReflectionClass' is not allowed

I suspect it's because of the changes merged into 7.4 after this RFC:
https://wiki.php.net/rfc/custom_object_serialization
However, that RFC claims to not have any BC-breaking changes.

Is there something that can be done to remedy this from the side of Mockery, or should this be considered a core PHP bug?

[okdewit]

I see this has been "fixed" in 7.4 RC1:
php/php-src@96da1fe

So I think this means mocks can not be serialized anymore.

[GrahamCampbell]

Mockery could, if it really wanted, make its mocks serializable, at least naively, by making sure the mocks own usage of reflection stuff was restored using custom code. However, serializing of partial mocks or mocks that have reflection stuff as expected return values, etc, will need more care (and maybe should not be supported).

[lcaliani]

I having the same issue here when trying to execute some tests

Serialization of 'Reflection Class' is not allowed

Any leads?

[ITPL-Krunal]

Serialization of 'TYPO3\CMS\Extbase\Reflection\MethodReflection' is not allowed in typo3 8.7.8 with php 7.4

This error not come when we use php 7.2 so why come in php 7.4.

Any solution?

[over-engineer]

Any updates on this?

[olsona-hologram]

Any updates on this?

[udidol]

Any updates on this?

[alinpop]

For me it happens with \Exception used inside the test and only when

• there is an error in the test
• and combined with the usage of
  -- @runTestsInSeparateProcesses and
  -- @preserveGlobalState disabled.

If the test is correct, the error will not show.

If there is something wrong in the test, I disable @runTestsInSeparateProcesses / @preserveGlobalState disabled, I fix the tests and then enable those again.

[ciltocruz]

For me it happens with \Exception used inside the test and only when

• there is an error in the test
• and combined with the usage of
  -- @runTestsInSeparateProcesses and
  -- @preserveGlobalState disabled.

If the test is correct, the error will not show.

If there is something wrong in the test, I disable @runTestsInSeparateProcesses / @preserveGlobalState disabled, I fix the tests and then enable those again.

Same conditions for me

[Chi-teck]

Exception stacktrace may contain unseralizable objects like Closure or Reflection. Since PHP 7.4 you need to enable zend.exception_ignore_args setting in php.ini when running tests.