Skip to content

Commit 6bd619a

Browse files
committed
minor #18786 Clearer difference with max and quiet options (flohw)
This PR was squashed before being merged into the 5.4 branch. Discussion ---------- Clearer difference with max and quiet options Hello, First contribution here so I hope that I didn't made a mistake. Let me know if I need to change or point a process I missed. As discussed on the symfony/symfony#46497, the difference between `quiet` and `max` may be unclear. In addition the behavior existing before 5.4 might have been erroneous. As the change is hard to retrieve and impossible to fix now, we come to the conclusion that a doc update may help to fix end user issue with this change. Let me know if the added paragraph needs to be clearer or at another place or if it needs to be rephrased as English is not my first language. I also wanted to make a link to the section which talk about `max` and making tests fail. I hope this is the right way. Thanks for reading. :-) Commits ------- fa31e93 Clearer difference with max and quiet options
2 parents 8cbdc1b + fa31e93 commit 6bd619a

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

components/phpunit_bridge.rst

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -325,6 +325,10 @@ It's also possible to change verbosity per deprecation type. For example, using
325325
``quiet[]=indirect&quiet[]=other`` will hide details for deprecations of types
326326
"indirect" and "other".
327327

328+
Note that `quiet` hides details for the specified deprecation types, but will
329+
not change the outcome in terms of exit code. That's what :ref:`max <making-tests-fail>` is for, and both
330+
settings are orthogonal.
331+
328332
.. versionadded:: 5.1
329333

330334
The ``quiet`` option was introduced in Symfony 5.1.

0 commit comments

Comments
 (0)