From 839a71670ffdb76439fc483dcf01e68e5fca7dda Mon Sep 17 00:00:00 2001 From: 1Utkarsh1 <121078149+1Utkarsh1@users.noreply.github.com> Date: Wed, 13 May 2026 00:02:30 +1000 Subject: [PATCH] docs: clarify subtests progress output (#14467) Co-authored-by: OpenAI Codex (cherry picked from commit 7df5d80ff3a98714a1d3cdbe82941229e511f4b3) --- changelog/13902.doc.rst | 1 + doc/en/how-to/subtests.rst | 4 +++- 2 files changed, 4 insertions(+), 1 deletion(-) create mode 100644 changelog/13902.doc.rst diff --git a/changelog/13902.doc.rst b/changelog/13902.doc.rst new file mode 100644 index 00000000000..f11a1936051 --- /dev/null +++ b/changelog/13902.doc.rst @@ -0,0 +1 @@ +Clarified how subtest progress markers are shown in the documentation. diff --git a/doc/en/how-to/subtests.rst b/doc/en/how-to/subtests.rst index 93b9d052afd..c71f1bbe1ad 100644 --- a/doc/en/how-to/subtests.rst +++ b/doc/en/how-to/subtests.rst @@ -26,7 +26,7 @@ Subtests are an alternative to parametrization, particularly useful when the exa Each assertion failure or error is caught by the context manager and reported individually: -.. code-block:: pytest +.. code-block:: text $ pytest -q test_subtest.py uuuuuF [100%] @@ -63,6 +63,8 @@ Each assertion failure or error is caught by the context manager and reported in In the output above: +* The compact progress output uses ``u`` for both passed and failed subtests; + see the short test summary for each failed subtest. * Subtest failures are reported as ``SUBFAILED``. * Subtests are reported first and the "top-level" test is reported at the end on its own.