From f4a5ee1befe9a756a3e45c5657d6007df3dbf487 Mon Sep 17 00:00:00 2001 From: Christophe Gabard Date: Sat, 2 Jul 2022 19:36:25 +0200 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D=20Clarify=20testing=20documentatio?= =?UTF-8?q?n=20about=20checking=20`stderr`=20(#335)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Sebastián Ramírez Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> --- docs/tutorial/testing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorial/testing.md b/docs/tutorial/testing.md index 108ffc3..c8b2b76 100644 --- a/docs/tutorial/testing.md +++ b/docs/tutorial/testing.md @@ -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}.