Oxidize Conference

Most Rust developers are familiar with “cargo test” and the default cargo test runner. It’s straight-forward API let’s developers write unit tests quickly and easily, because who wants to write tests if it feels like a chore? But what to do if the default test harness isn’t compatible with your specific build setup? In real-world scenarios like mixed Rust and C/C++ code bases this can often be the case, especially if CMake or another C/C++ toolchain drive the build.

Player unavailable or embedding blocked? Use the YouTube link above.