You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the documentation, the @group time-sensitive annotation is the preferred way to use the ClockMock in unittests.
However, this does not work out of the box, without registering Symfony\Bridge\PhpUnit\SymfonyTestsListener or using simple-phpunit. This should probably be explained in the documentation. (The 3.2 documentation doesn't mention it's required for using the ClockMock feature, and the 2.8 documentation doesn't even mention simple-phpunit at all, and I can't find it in vendor/bin)
…viereguiluz)
This PR was merged into the 2.8 branch.
Discussion
----------
Explain better how to enable the ClockMock annotation
This fixes#7500.
Commits
-------
13baa4d Explain better how to enable the ClockMock annotation
According to the documentation, the
@group time-sensitive
annotation is the preferred way to use theClockMock
in unittests.However, this does not work out of the box, without registering
Symfony\Bridge\PhpUnit\SymfonyTestsListener
or usingsimple-phpunit
. This should probably be explained in the documentation. (The 3.2 documentation doesn't mention it's required for using theClockMock
feature, and the 2.8 documentation doesn't even mentionsimple-phpunit
at all, and I can't find it invendor/bin
)See https://github.com/ComaVN/symfony-phpunit-bridge-clockmock for a test case
See also symfony/symfony#21612
The text was updated successfully, but these errors were encountered: