Skip to content

📝 Clarify the need for mix_stderr when accessing the output of stderr in tests #1045

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

Merged
tiangolo merged 5 commits into from
Feb 27, 2025
+1 −1
Merged

📝 Clarify the need for mix_stderr when accessing the output of stderr in tests #1045

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
b25fa67
Clarify docs on testing contents of stderr
mrchrisadams Nov 8, 2024
fdbe59e
Make question more prominent with bold
mrchrisadams Nov 8, 2024
27e6c60
Further small rewording
svlandeg Feb 6, 2025
4644bd5
Merge branch 'master' into mrchrisadams/testing-documentation-385
svlandeg Feb 6, 2025
bda97d2
Merge branch 'master' into mrchrisadams/testing-documentation-385
svlandeg Feb 20, 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
2 changes: 1 addition & 1 deletion docs/tutorial/testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ Then we check that the text printed to "standard output" contains the text that

/// tip

You could also check `result.stderr` for "standard error" independently from "standard output" if your `CliRunner` instance is created with the `mix_stderr=False` argument.
You could also check output sent to "standard error" (`stderr`) instead of "standard output" (`stdout`). To do so, make sure your `CliRunner` instance is created with the `mix_stderr=False` argument. You need this setting to be able to access `result.stderr` in tests.

///

Expand Down