Re:The internals of testing in Rust in 2018
by skolemtotem on Monday July 23, 2018 @07:32PM
(#17596913)
Rust takes a similar approach. For unit tests, you use the #[cfg(test)] attribute (/ pragma / directive) for conditional compilation, and #[test] to mark a function that is a unit test, which is run whenever you run the `cargo test` command. Also, any Rust code in Markdown fences in documentation is, by default, also run by `cargo test`, which you can disable for an individual code block by marking it as `rust,norun` instead of `rust`.
Re:The internals of testing in Rust in 2018
by erichdongubler on Tuesday July 24, 2018 @12:45AM
(#17598173)
Shameless plug: you can have D-ish testing blocks with a macro I published on https://crates.io as `adhesion`: https://github.com/erichdongubler/adhesion-rs
https://dlang.org/spec/unittest.html