Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

馃摑 Clarify testing documentation about checking stderr #335

Merged
merged 3 commits into from
Jul 2, 2022
Merged

馃摑 Clarify testing documentation about checking stderr #335

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
917f350
Update testing.md
cgabard Oct 8, 2021
ea65a0c
Merge branch 'master' into improve_testing_doc
tiangolo Jul 2, 2022
9d643ee
馃帹 [pre-commit.ci] Auto format from pre-commit.com hooks
pre-commit-ci[bot] Jul 2, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
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 @@ -70,7 +70,7 @@ Here we are checking that the exit code is 0, as it is for programs that exit wi
Then we check that the text printed to "standard output" contains the text that our CLI program prints.

!!! tip
You could also check `result.stderr` for "standard error".
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.

!!! info
If you need a refresher about what is "standard output" and "standard error" check the section in [Printing and Colors: "Standard Output" and "Standard Error"](printing.md#standard-output-and-standard-error){.internal-link target=_blank}.
Expand Down