Should be final writing_tests commit

Author: blyxyas

book/src/development/writing_tests.md

@@ -88,13 +88,13 @@ As we gradually implement our lint logic, we will keep running this UI test comm
 Clippy will begin outputting information that allows us to check if the output is
 turning into what we want it to be.
 
+blyxyas marked this conversation as resolved.
 ### Example output
 
 As our `foo_functions` lint is tested, the output would look something like this:
 
 ```
 failures:
-
 ---- compile_test stdout ----
 normalized stderr:
 error: function called "foo"
@@ -104,19 +104,16 @@ LL |     pub fn foo(&self) {}
    |            ^^^
    |
    = note: `-D clippy::foo-functions` implied by `-D warnings`
-
 error: function called "foo"
   --> $DIR/foo_functions.rs:13:8
    |
 LL |     fn foo(&self) {}
    |        ^^^
-
 error: function called "foo"
   --> $DIR/foo_functions.rs:19:4
    |
 LL | fn foo() {}
    |    ^^^
-
 error: aborting due to 3 previous errors
 ```
 
@@ -191,23 +188,23 @@ and prepending the `TESTNAME` variable to `cargo uitest` works for Cargo lints t
 
 ## Rustfix Tests
 
-If the lint you are working on is making use of structured suggestions, the test
-file should include a `// run-rustfix` comment at the top.
+If the lint you are working on is making use of structured suggestions,
+`rustfix` will apply the suggestions from the lint to the test file code and
+compare that to the contents of a `.fixed` file.
 
 Structured suggestions tell a user how to fix or re-write certain code that has
 been linted with [`span_lint_and_sugg`].
 
-The `// run-rustfix` comment will additionally run [rustfix] for our test.
-Rustfix will apply the suggestions from the lint to the test file code and
-compare that to the contents of a `.fixed` file.
+Should `span_lint_and_sugg` be used to generate a suggestion, but not all
+suggestions lead to valid code, you can use the `//@no-rustfix` comment on top
+of the test file, to not run `rustfix` on that file.
 
 We'll talk about suggestions more in depth in a later chapter.
 <!-- FIXME: (blyxyas) Link to "Emitting lints" when that gets merged -->
 
 Use `cargo bless` to automatically generate the `.fixed` file after running
 the tests.
 
-[rustfix]: https://github.com/rust-lang/rustfix
 [`span_lint_and_sugg`]: https://doc.rust-lang.org/beta/nightly-rustc/clippy_utils/diagnostics/fn.span_lint_and_sugg.html
 
 ## Testing Manually