Mark panicking tests as `should_panic` instead of `no_run`.

1 files changed, 2 insertions, 2 deletions

diff --git a/src/doc/book/macros.md b/src/doc/book/macros.md
index 9f40829f423..78fe07ec1be 100644
--- a/src/doc/book/macros.md
+++ b/src/doc/book/macros.md
@@ -662,7 +662,7 @@ Here are some common macros you’ll see in Rust code.
 This macro causes the current thread to panic. You can give it a message
 to panic with:
 
-```rust,no_run
+```rust,should_panic
 panic!("oh no!");
 ```
 
@@ -688,7 +688,7 @@ These two macros are used in tests. `assert!` takes a boolean. `assert_eq!`
 takes two values and checks them for equality. `true` passes, `false` `panic!`s.
 Like this:
 
-```rust,no_run
+```rust,should_panic
 // A-ok!
 
 assert!(true);