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.

By default, any non-legacy-tagged or any non-`@-silenced`_ deprecation notices

willmake tests fail. Alternatively, setting ``SYMFONY_DEPRECATIONS_HELPER`` to

anarbitrary value (ex: ``320``) will make the tests fails only if a higher

numberof deprecation notices is reached (``0`` is the default value). You can

also setthe value ``"weak"`` which will make the bridge ignore any deprecation

notices.This is useful to projects that must use deprecated interfaces for

backwardcompatibility reasons.

Time-sensitive Tests

``ClockMock::withClockMock(true)`` before the test and

``ClockMock::withClockMock(false)`` after the test.

As a result, the following isguarenteed to work and is no longer a transient

As a result, the following isguaranteed to work and is no longer a transient

test::

advances the internal clock the given number of seconds without actually

waiting that time, so your test will execute 10 seconds faster.

DNS-sensitive Tests

..versionadded::3.1

The mocks for DNS related functions were introduced in Symfony 3.1.

Tests that make network connections, for example to check the validity of a DNS

record, can be slow to execute and unreliable due to the conditions of the

network. For that reason, this component also provides mocks for these PHP

functions:

*:phpfunction:`checkdnsrr()`

*:phpfunction:`dns_check_record()`

*:phpfunction:`getmxrr()`

*:phpfunction:`dns_get_mx()`

*:phpfunction:`gethostbyaddr()`

*:phpfunction:`gethostbyname()`

*:phpfunction:`gethostbynamel()`

*:phpfunction:`dns_get_record()`

Use Case

Consider the following example that uses the ``checkMX`` option of the ``Email``

constraint to test the validity of the email domain::

In order to avoid making a real network connection, add the ``@dns-sensitive``

annotation to the class and use the ``DnsMock::withMockedHosts()`` to configure

the data you expect to get for the given hosts::

The ``withMockedHosts()`` method can return any number of hosts with different

configuration, so you can simulate diverse network conditions::

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 FQCN is ``App\Watch\DummyWatch``.

The ``@group time-sensitive`` and ``@group dns-sensitive`` annotations work

"by convention" and assume that the namespace of the tested class can be

obtained just by removing the ``\Tests\`` part from the test namespace. For

example, if your test case fully-qualified class name (FQCN) is

``App\Tests\Watch\DummyWatchTest``, it assumes the tested class FQCN is

``App\Watch\DummyWatch``.

If this convention doesn't work for your application,you can also configure

the mockednamespaces in the ``phpunit.xml`` file, as done for example in the

If this convention doesn't work for your application,configure the mocked

namespaces in the ``phpunit.xml`` file, as done for example in the

:doc:`HttpKernel Component</components/http_kernel/introduction>`:

..code-block::xml