diff options
Diffstat (limited to 'src/doc/guide-testing.md')
| -rw-r--r-- | src/doc/guide-testing.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/doc/guide-testing.md b/src/doc/guide-testing.md index 07813855d9b..9d15f55f33f 100644 --- a/src/doc/guide-testing.md +++ b/src/doc/guide-testing.md @@ -49,7 +49,7 @@ value. To run the tests in a crate, it must be compiled with the `--test` flag: `rustc myprogram.rs --test -o myprogram-tests`. Running the resulting executable will run all the tests in the crate. A test is considered successful if its function returns; if the task running -the test fails, through a call to `fail!`, a failed `assert`, or some +the test fails, through a call to `panic!`, a failed `assert`, or some other (`assert_eq`, ...) means, then the test fails. When compiling a crate with the `--test` flag `--cfg test` is also @@ -77,7 +77,7 @@ test on windows you can write `#[cfg_attr(windows, ignore)]`. Tests that are intended to fail can be annotated with the `should_fail` attribute. The test will be run, and if it causes its -task to fail then the test will be counted as successful; otherwise it +task to panic then the test will be counted as successful; otherwise it will be counted as a failure. For example: ~~~test_harness |