@@ -14,9 +14,9 @@ It comes with the following features:
1414By default any non-legacy-tagged or any non-@-silenced deprecation notices will
1515make tests fail.
1616This 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-verbose ` . This will make the bridge ignore
18+ deprecation notices and is useful to projects that must use deprecated interfaces
19+ for backward compatibility reasons.
2020
2121A summary of deprecation notices is displayed at the end of the test suite:
2222
@@ -53,8 +53,9 @@ You have to decide either to:
5353 forward compatibility;
5454 * or move them to the ** Legacy** section (by using one of the above way).
5555
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+ regular expression that matches this deprecation's message, encapsed between ` / ` .
59+ For example, ` SYMFONY_DEPRECATIONS_HELPER=/foobar/ phpunit ` will stop your test
60+ suite once a deprecation notice is triggered whose message contains the "foobar"
61+ string.
0 commit comments