Skip to content

Resolving Issue #13902 #14017

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Resolving Issue #13902 #14017

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
11022e1
Fix subtests documentation highlighting: remove misleading all-green …
emilymamcarz Nov 30, 2025
8224036
docs: restore accidentally removed subtest output explanation
emilymamcarz Nov 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions AUTHORS
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -151,6 +151,7 @@ Eli Boyarski
Elizaveta Shashkova
Éloi Rivard
Emil Hjelm
Emily Mamcarz
Endre Galaczi
Eric Hunsberger
Eric Liu
Expand Down
4 changes: 2 additions & 2 deletions doc/en/how-to/subtests.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,10 +26,10 @@ 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:: console

$ pytest -q test_subtest.py
uuuuuF [100%]
u u u u uF [100%]
Copy link
Member

@RonnyPfannschmidt RonnyPfannschmidt Nov 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the next doc regen would undo this change
additionally the code block should lint as "pytest" theres a extra linter in pygments for that

the pygments linter may need updates

Copy link
Author

@emilymamcarz emilymamcarz Dec 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the clarification. That makes sense.

I’ll revert the documentation changes and move the fix to the correct location. I’ll investigate the Pygments pytest lexer and open an issue/PR there so that the highlighting is corrected at the source. Once Pygments updates the lexer, pytest’s documentation can regenerate with the correct output.

Thanks for the guidance, I’ll follow up with the Pygments-side fix.

================================= FAILURES =================================
_______________________ test [custom message] (i=1) ________________________

Expand Down