nextest VS cargo-deny

cargo-nextest describes itself as a “next-generation Rust test runner”. To install, you need to run cargo install cargo-nextest.

> On my work I make 1-15 commits a day. If I have to spend thought cycles on the commit message, that is time that goes from other productive endeavours.

I make roughly that many commits a day as well. If something's easy to understand I'll put in a simple commit message (e.g. [1]), but I do put in the effort for more complicated ones.

[1] https://github.com/nextest-rs/nextest/commit/efd194b2e1d8d61...

[2] https://github.com/oxidecomputer/omicron/commit/b07a8f593325...

If you need fancier testing than what's built into Rust, cargo-nextest is becoming quite popular.

https://nexte.st/ is what is getting all the attention as a replacement test harness/framework these days.

I believe cargo-nextest supports running separate binaries concurrently.

Do you already use nextest or something else? That really leans into test parallelism and sounds like a perfect fit for how you structure the tests.

I built it for cargo-nextest, in service of a new feature where some tests can be marked as heavier than others.

IMO 100% worth checking out: https://nexte.st/

For me, most of my needs are covered with next-test(https://nexte.st/), not that I have ever used any of the things you mentioned 😅

Tip: You can check the licenses of all your dependencies (recursively) using cargo-deny: https://github.com/EmbarkStudios/cargo-deny

cargo-deny

cargo-deny can help block specified versions of a crate and even has some advisory features that can probably used to block crate with reported vulnerabilities

cargo deny for fetching crates only from trusted sources, blacklisting crates, etc.

Use cargo audit or cargo deny to check the crates in your Cargo.lock to ensure they don't contain any vulnerabilities.

> Explain the crate scanner thing?

I assume a reference to tools that help manage potential issues around dependencies, e.g.:

* https://github.com/rustsec/rustsec/tree/main/cargo-audit

* https://github.com/EmbarkStudios/cargo-deny

"[cargo-audit] Audit Cargo.lock files for crates with security vulnerabilities reported to the RustSec Advisory Database."

"cargo-deny is a cargo plugin that lets you lint your project's dependency graph to ensure all your dependencies conform to your expectations and requirements." e.g. license, security advisories, source.

cargo-deny does license and security advisory checking, and cargo-geiger does unsafe checking.

cargo-deny

OpenSSL has been banned in our project for a variety of reasons via cargo-deny for around a year and half, it was actually one of the reasons we created it in the first place.