3 ms·

I love the idea of using other open source projects and their test suites to test the tool. It feels like this approach could be useful for other projects as we

I love the idea of using other open source projects and their test suites to test the tool. It feels like this approach could be useful for other projects as well. For example, what if you could test changes in your library by running the test suite of a couple of projects that depend on it?

TAForObvReasons 9y ago
Rust does this with cargobomb: https://brson.github.io/2017/07/10/how-rust-is-tested https://brson.github.io/2017/07/10/how-rust-is-tested > Rust has a standard testing facility that most Rust crates use, and Rust has a standard repository of Rust crates in crates.io. GitHub further contains repositories of Rust crates that are not published to crates.io. > These factors allow us to treat the entire world of open source Rust code as our test suite. > As new nightlies and betas are published, we use the cargobomb tool to test this corpus of Rust code (as of 2017/07/10 over 13,000 crates) against both the stable release and a nightly or beta release, comparing the results for regressions.