about summary refs log tree commit diff
path: root/src/libstd/sys/unix/stack_overflow.rs
diff options
context:
space:
mode:
authorSteven Fackler <sfackler@gmail.com>2014-12-04 23:02:36 -0800
committerSteven Fackler <sfackler@gmail.com>2014-12-06 15:13:48 -0800
commit616af6eb83630b76bb3a9bde57a00f5ebe5dbd6c (patch)
tree494380149d05abc6c6954b1b6bcbee856563d163 /src/libstd/sys/unix/stack_overflow.rs
parentde83d7dd191bf5564855057a29f9b5d9dcfcb201 (diff)
downloadrust-616af6eb83630b76bb3a9bde57a00f5ebe5dbd6c.tar.gz
rust-616af6eb83630b76bb3a9bde57a00f5ebe5dbd6c.zip
Allow message specification for should_fail
The test harness will make sure that the panic message contains the
specified string. This is useful to help make `#[should_fail]` tests a
bit less brittle by decreasing the chance that the test isn't
"accidentally" passing due to a panic occurring earlier than expected.
The behavior is in some ways similar to JUnit's `expected` feature:
`@Test(expected=NullPointerException.class)`.

Without the message assertion, this test would pass even though it's not
actually reaching the intended part of the code:
```rust
 #[test]
 #[should_fail(message = "out of bounds")]
fn test_oob_array_access() {
    let idx: uint = from_str("13o").unwrap(); // oops, this will panic
    [1i32, 2, 3][idx];
}
```
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions