The PHPUnit Bridge
Warning: You are browsing the documentation for Symfony 2.x, which is no longer maintained.
Read the updated version of this page for Symfony 7.1 (the current stable version).
The PHPUnit Bridge provides utilities to report legacy tests and usage of deprecated code and a helper for time-sensitive tests.
It comes with the following features:
- Forces the tests to use a consistent locale (
C
); - Auto-register
class_exists
to load Doctrine annotations (when used); - It displays the whole list of deprecated features used in the application;
- Displays the stack trace of a deprecation on-demand;
- Provides a
ClockMock
helper class for time-sensitive tests.
2.7
The PHPUnit Bridge was introduced in Symfony 2.7. It is however possible to install the bridge in any Symfony application (even 2.3).
Installation
1
$ composer require --dev "symfony/phpunit-bridge:*"
Alternatively, you can clone the https://github.com/symfony/phpunit-bridge repository.
Note
If you install this component outside of a Symfony application, you must
require the vendor/autoload.php
file in your code to enable the class
autoloading mechanism provided by Composer. Read
this article for more details.
Note
The PHPUnit bridge is designed to work with all maintained versions of Symfony components, even across different major versions of them. You should always use its very latest stable major version to get the most accurate deprecation report.
Usage
See also
This article explains how to use the PhpUnitBridge features as an independent component in any PHP application. Read the Testing article to learn about how to use it in Symfony applications.
Once the component is installed, a simple-phpunit
script is created in the
vendor/
directory to run tests. This script wraps the original PHPUnit binary
to provide more features:
1 2
$ cd my-project/
$ ./vendor/bin/simple-phpunit
After running your PHPUnit tests, you will get a report similar to this one:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
$ phpunit -c app
PHPUnit by Sebastian Bergmann.
Configuration read from <your-project>/app/phpunit.xml.dist
.................
Time: 1.77 seconds, Memory: 5.75Mb
OK (17 tests, 21 assertions)
Remaining deprecation notices (2)
getEntityManager is deprecated since Symfony 2.1. Use getManager instead: 2x
1x in DefaultControllerTest::testPublicUrls from AppBundle\Tests\Controller
1x in BlogControllerTest::testIndex from AppBundle\Tests\Controller
The summary includes:
- Unsilenced
- Reports deprecation notices that were triggered without the recommended @-silencing operator.
- Legacy
- Deprecation notices denote tests that explicitly test some legacy features.
- Remaining/Other
- Deprecation notices are all other (non-legacy) notices, grouped by message, test class and method.
Note
If you don't want to use the simple-phpunit
script, register the following
PHPUnit event listener in your PHPUnit configuration file to get the same
report about deprecations (which is created by a PHP error handler
called DeprecationErrorHandler):
1 2 3 4 5
<!-- phpunit.xml.dist -->
<!-- ... -->
<listeners>
<listener class="Symfony\Bridge\PhpUnit\SymfonyTestsListener" />
</listeners>
Trigger Deprecation Notices
Deprecation notices can be triggered by using:
1
@trigger_error('Your deprecation message', E_USER_DEPRECATED);
Without the @-silencing operator, users would need to opt-out from deprecation notices. Silencing by default swaps this behavior and allows users to opt-in when they are ready to cope with them (by adding a custom error handler like the one provided by this bridge). When not silenced, deprecation notices will appear in the Unsilenced section of the deprecation report.
Mark Tests as Legacy
There are three ways to mark a test as legacy:
- (Recommended) Add the
@group legacy
annotation to its class or method; - Make its class name start with the
Legacy
prefix; - Make its method name start with
testLegacy*()
instead oftest*()
.
Note
If your data provider calls code that would usually trigger a deprecation,
you can prefix its name with provideLegacy
or getLegacy
to silence
these deprecations. If your data provider does not execute deprecated
code, it is not required to choose a special naming just because the
test being fed by the data provider is marked as legacy.
Also be aware that choosing one of the two legacy prefixes will not mark tests as legacy that make use of this data provider. You still have to mark them as legacy tests explicitly.
Configuration
In case you need to inspect the stack trace of a particular deprecation
triggered by your unit tests, you can set the SYMFONY_DEPRECATIONS_HELPER
environment variable to a regular expression that matches this deprecation's
message, enclosed with /
. For example, with:
1 2 3 4 5 6 7 8 9 10 11 12
<!-- http://phpunit.de/manual/4.1/en/appendixes.configuration.html -->
<phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://schema.phpunit.de/4.1/phpunit.xsd"
>
<!-- ... -->
<php>
<server name="KERNEL_DIR" value="app/" />
<env name="SYMFONY_DEPRECATIONS_HELPER" value="/foobar/" />
</php>
</phpunit>
PHPUnit will stop your test suite once a deprecation notice is triggered whose
message contains the "foobar"
string.
Making Tests Fail
By default, any non-legacy-tagged or any non-`@-silenced`_ deprecation notices will
make tests fail. Alternatively, setting SYMFONY_DEPRECATIONS_HELPER
to an
arbitrary value (ex: 320
) will make the tests fails only if a higher number
of deprecation notices is reached (0
is the default value). You can also set
the value "weak"
which will make the bridge ignore any deprecation notices.
This is useful to projects that must use deprecated interfaces for backward
compatibility reasons.
Display the Full Stack Trace
By default, the PHPUnit Bridge displays only deprecation messages.
To show the full stack trace related to a deprecation, set the value of SYMFONY_DEPRECATIONS_HELPER
to a regular expression matching the deprecation message.
For example, if the following deprecation notice is thrown:
1 2
1x: Doctrine\Common\ClassLoader is deprecated.
1x in EntityTypeTest::setUp from Symfony\Bridge\Doctrine\Tests\Form\Type
Running the following command will display the full stack trace:
1
$ SYMFONY_DEPRECATIONS_HELPER='/Doctrine\\Common\\ClassLoader is deprecated\./' ./vendor/bin/simple-phpunit
Time-sensitive Tests
2.8
Support for clock mocking was introduced in Symfony 2.8.
Use Case
If you have this kind of time-related tests:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
use PHPUnit\Framework\TestCase;
use Symfony\Component\Stopwatch\Stopwatch;
class MyTest extends TestCase
{
public function testSomething()
{
$stopwatch = new Stopwatch();
$stopwatch->start('event_name');
sleep(10);
$duration = $stopwatch->stop('event_name')->getDuration();
$this->assertEquals(10000, $duration);
}
}
You used the Symfony Stopwatch Component to
calculate the duration time of your process, here 10 seconds. However, depending
on the load of the server or the processes running on your local machine, the
$duration
could for example be 10.000023s
instead of 10s
.
This kind of tests are called transient tests: they are failing randomly depending on spurious and external circumstances. They are often cause trouble when using public continuous integration services like Travis CI.
Clock Mocking
The ClockMock class provided by this bridge
allows you to mock the PHP's built-in time functions time()
,
microtime()
, sleep()
and usleep()
.
To use the ClockMock
class in your test, add the @group time-sensitive
annotation to its class or methods. This annotation only works when executing
PHPUnit using the vendor/bin/simple-phpunit
script or when registering the
following listener in your PHPUnit configuration:
1 2 3 4 5
<!-- phpunit.xml.dist -->
<!-- ... -->
<listeners>
<listener class="\Symfony\Bridge\PhpUnit\SymfonyTestsListener" />
</listeners>
Note
If you don't want to use the @group time-sensitive
annotation, you can
register the ClockMock
class manually by calling
ClockMock::register(__CLASS__)
and ClockMock::withClockMock(true)
before the test and ClockMock::withClockMock(false)
after the test.
As a result, the following is guaranteed to work and is no longer a transient test:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
use PHPUnit\Framework\TestCase;
use Symfony\Component\Stopwatch\Stopwatch;
/**
* @group time-sensitive
*/
class MyTest extends TestCase
{
public function testSomething()
{
$stopwatch = new Stopwatch();
$stopwatch->start('event_name');
sleep(10);
$duration = $stopwatch->stop('event_name')->getDuration();
$this->assertEquals(10000, $duration);
}
}
And that's all!
Caution
Time-based function mocking follows the PHP namespace resolutions rules
so "fully qualified function calls" (e.g \time()
) cannot be mocked.
The @group time-sensitive
annotation is equivalent to calling
ClockMock::register(MyTest::class)
. If you want to mock a function used in a
different class, do it explicitly using ClockMock::register(MyClass::class)
:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
// the class that uses the time() function to be mocked
namespace App;
class MyClass
{
public function getTimeInHours()
{
return time() / 3600;
}
}
// the test that mocks the external time() function explicitly
namespace App\Tests;
use App\MyClass;
use PHPUnit\Framework\TestCase;
/**
* @group time-sensitive
*/
class MyTest extends TestCase
{
public function testGetTimeInHours()
{
ClockMock::register(MyClass::class);
$my = new MyClass();
$result = $my->getTimeInHours();
$this->assertEquals(time() / 3600, $result);
}
}
Tip
An added bonus of using the ClockMock
class is that time passes
instantly. Using PHP's sleep(10)
will make your test wait for 10
actual seconds (more or less). In contrast, the ClockMock
class
advances the internal clock the given number of seconds without actually
waiting that time, so your test will execute 10 seconds faster.
Troubleshooting
The @group time-sensitive
works "by convention" and assumes that the
namespace of the tested class can be obtained just by removing the Tests\
part from the test namespace. I.e. that if the your test case fully-qualified
class name (FQCN) is App\Tests\Watch\DummyWatchTest
, it assumes the tested
class namespace is App\Watch
.
If this convention doesn't work for your application, you can also configure
the mocked namespaces in the phpunit.xml
file, as done for example in the
HttpKernel Component:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
<!-- http://phpunit.de/manual/4.1/en/appendixes.configuration.html -->
<phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://schema.phpunit.de/4.1/phpunit.xsd"
>
<!-- ... -->
<listeners>
<listener class="Symfony\Bridge\PhpUnit\SymfonyTestsListener">
<arguments>
<array>
<element key="time-sensitive"><string>Symfony\Component\HttpFoundation</string></element>
</array>
</arguments>
</listener>
</listeners>
</phpunit>