Re: (not) testing Rust packages?!

[John Soo <jsoo1@asu.edu>]

Hey Andreas,

> `cargo test` will always build the crate a second time, even if `cargo
> build` already ran. This is due to the config attribute `test` being set
> (similar a to C preprocessor #define), and thus the actual code being
> compiled may be different.

Just to make sure, does that mean we can safely run tests without
having unwanted store outputs?
I can see that maybe the test compile step might not catch everything
or compile the whole package, but wouldn't you say that some testing
is better than none at all?

> In addition, `cargo test` will bring in the
> `dev-dependencies`, which can indeed be _much_ more massive than the
> regular `dependencies`.

Can you provide an example? The largest sets of test dependencies I
can find are using the insta library which we have packaged already.
Do you think the number of dependencies at the top level package was
due to the old style of hiding crates packages?
Also we have quickcheck and criterion packaged now which should also
reduce the required work to create a package now.

Thanks,

John