From 2eb922ef8c8d595c9288dc15e74adc6fff31b14b Mon Sep 17 00:00:00 2001 From: 0x766F6964 <157990748+0x766F6964@users.noreply.github.com> Date: Sat, 21 Jun 2025 02:36:58 +0200 Subject: [PATCH] fix ch11-01-writing-tests: remove duplicate paragraph --- src/ch11-01-writing-tests.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/src/ch11-01-writing-tests.md b/src/ch11-01-writing-tests.md index 5c17a7844a..6edcf23734 100644 --- a/src/ch11-01-writing-tests.md +++ b/src/ch11-01-writing-tests.md @@ -96,11 +96,7 @@ passed; 0 failed` totals the number of tests that passed or failed. It’s possible to mark a test as ignored so it doesn’t run in a particular instance; we’ll cover that in the [“Ignoring Some Tests Unless Specifically Requested”][ignoring] section later in this chapter. Because we -haven’t done that here, the summary shows `0 ignored`. We can also pass an -argument to the `cargo test` command to run only tests whose name matches a -string; this is called _filtering_ and we’ll cover that in the [“Running a -Subset of Tests by Name”][subset] section. Here we haven’t -filtered the tests being run, so the end of the summary shows `0 filtered out`. +haven’t done that here, the summary shows `0 ignored`. The `0 measured` statistic is for benchmark tests that measure performance. Benchmark tests are, as of this writing, only available in nightly Rust. See