Skip to content

Commit 09fe616

Browse files
📝 Clarify the need for mix_stderr when accessing the output of stderr in tests (#1045)
Co-authored-by: Sofie Van Landeghem <svlandeg@users.noreply.github.com>
1 parent ece5536 commit 09fe616

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎docs/tutorial/testing.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ Then we check that the text printed to "standard output" contains the text that
7171

7272
/// tip
7373

74-
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.
74+
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.
7575

7676
///
7777

0 commit comments

Comments
 (0)