#assert #test #testing #compare #asserts

dev all_asserts

A crate for multiple types of asserts that don’t exist in the standard library

8 stable releases

2.3.1 Mar 2, 2022
2.3.0 Sep 13, 2021
2.2.0 Nov 10, 2020
2.1.0 Jun 25, 2020
0.1.4 Mar 19, 2019

#53 in Development tools

Download history 381/week @ 2022-01-24 387/week @ 2022-01-31 417/week @ 2022-02-07 337/week @ 2022-02-14 263/week @ 2022-02-21 480/week @ 2022-02-28 386/week @ 2022-03-07 298/week @ 2022-03-14 321/week @ 2022-03-21 364/week @ 2022-03-28 293/week @ 2022-04-04 444/week @ 2022-04-11 602/week @ 2022-04-18 359/week @ 2022-04-25 394/week @ 2022-05-02 353/week @ 2022-05-09

1,715 downloads per month
Used in less than 6 crates

Apache-2.0

17KB
250 lines

all_asserts Build Status all_asserts crate Crates.io license

A crate for multiple types of asserts that don't exist in the standard library

Rationale

There are several kinds of problems that I had faced while writing tests, especially when writing comparator tests. The output from the existing macros, were providing vague outputs while debugging which made me write this crate. I had created an RFC, but neverthless it was rejected as there were not enough use cases. I am not too sure about others, but I find myself writing multiple tests that frequently make use of these assert macros.

Importing and using

Add this to your Cargo.toml :

all_asserts = "*"

And now you can use the asserts wherever you like! If you want to make it available all across your crate, in your lib.rs or main.rs, add the following:

#[macro_use]
extern crate all_asserts;

Examples

An example using assert_range! :

use all_asserts::assert_range;
fn main() {
  assert_range!(10..20, 20);
}

This outputs something like:

thread 'main' panicked at 'assertion failed:
`20 is not in range of 10..20` - it should have been in this range, src/main.rs:292:5

Another example:

use all_asserts::{assert_range, assert_nrange};
fn main() {
  assert_range!(1.0..=2.0, 1.5);
  // You can also add a debug message if the assertion fails
  assert_nrange!(
    1.0..=2.0, 1.5, "Oops! 1.5 is in the interval [1.0,2.0]"
  );
}

This outputs:

thread 'main' panicked at 'assertion failed: `1.5 is in range of 1.0..2.0` - it should not have been in this range: Oops! 1.5 is in the interval [1.0,2.0]', src/main.rs:295:5

An example using assert_lt! :

thread 'main' panicked at 'assertion failed: `(left < right) but here (left >= right)`
  left: `100` ,
 right: `200` ', src/main.rs:79:5

Isn't that much better than what the current macros provide? Well, I'll leave you to decide!

Available macros

The name of the assert pretty much tells you everything:

  • assert_gt!(a, b) -> Will panic if a is not greater than b
  • assert_ge!(a, b) -> Will panic if a is not greater than or equal to b
  • assert_lt!(a, b) -> Will panic if a is not less than b
  • assert_le!(a, b) -> Will panic if a is not greater than or equal to b
  • assert_range!((x..y), b) -> Will panic if b is not within the range [x, y)
  • assert_nrange!((x..y), b) -> Will panic if b is within the range [x, y)
  • assert_near!(a, b, e) -> Will panic if b is not within +/- e of a; i.e. b is within the range [a - e, a + e]
  • assert_true!(a) -> Will panic if a is not true
  • assert_false!(a) -> Will panic if a is not false

debug_* variants of the macros are also available, which only work on builds with debug assertions enabled (usually builds produced by running cargo build or cargo test ).

Building

Simply run:

$ git clone https://github.com/ohsayan/all_asserts.git
$ cd all_asserts
$ cargo build

And for testing:

$ cargo test

Contributing

Your welcome to!

"No man is an island!"

And I always stick to that belief! Please help me out in better formatting the output to make debugging easier. If you find an issue, go ahead a create one! (All doubts, questions and ideas are welcome)

License

This project is licensed under the Apache-2.0 License.

No runtime deps