@@ -14,9 +14,9 @@ It comes with the following features:
14
14
By default any non-legacy-tagged or any non-@-silenced deprecation notices will
15
15
make tests fail.
16
16
This can be changed by setting the ` SYMFONY_DEPRECATIONS_HELPER ` environment
17
- variable to ` weak ` . This will make the bridge ignore deprecation notices and
18
- is useful to projects that must use deprecated interfaces for backward
19
- compatibility reasons.
17
+ variable to ` weak ` or ` weak-versose ` . This will make the bridge ignore
18
+ deprecation notices and is useful to projects that must use deprecated interfaces
19
+ for backward compatibility reasons.
20
20
21
21
A summary of deprecation notices is displayed at the end of the test suite:
22
22
@@ -53,8 +53,8 @@ You have to decide either to:
53
53
forward compatibility;
54
54
* or move them to the ** Legacy** section (by using one of the above way).
55
55
56
- In case you need to inspect the stack trace of a particular deprecation triggered by
57
- one of your unit tests, you can set the ` SYMFONY_DEPRECATIONS_HELPER ` env var to
58
- a regexp that matches this test case 's ` class::method ` name . For example,
59
- ` SYMFONY_DEPRECATIONS_HELPER=/^MyTest::testMethod$ / phpunit ` will stop your test
60
- suite once a deprecation is triggered by the ` MyTest::testMethod ` test .
56
+ In case you need to inspect the stack trace of a particular deprecation triggered
57
+ by your unit tests, you can set the ` SYMFONY_DEPRECATIONS_HELPER ` env var to a
58
+ regexp that matches this depreaction 's message . For example,
59
+ ` SYMFONY_DEPRECATIONS_HELPER=/foobar / phpunit ` will stop your test suite once a
60
+ deprecation message is triggered and contains the "foobar" string .
0 commit comments