rs-pbrt-test-scenes VS mutagen

So, I started working on a library to deal with reading data from Blender‘s binary .blend files. In the past I was able to render some Blender v2.79 files, now I abstracted the library to deal (in theory) with all Blender versions (using the DNA information). I tested with two scenes for Blender 2.79 and Blender 3.0 (which should be quiet different from the GUI perspective). With v2.79 I got away with a naming convention and mis-using the old material settings (pre Cycles renderer). Blender 3.0 forced me to get some material settings from shader nodes and the library allows to follow pointers from one data structure to the next. Prove of concept: Both, the Cornell box, as well as the Radiance Conference Room, render with both Blender scene versions. Get the latest Blender scenes here: https://gitlab.com/jdb-walter/rs-pbrt-test-scenes/-/tree/master/blend

There are two testing techniques you didn't mention: Snapshot tests (which are greatly simplified using the insta crate and mutation testing (which can be done on nightly with my mutagen crate.

How does this compare to mutagen?

Do you mean as part of build.rs? Yes, that's certainly doable, and has been done in the past. You can use env!("OUT_DIR") for that. Examples you may want to refer to include my mutagen crate and criterion.

Would be great if this could include mutation testing.

I wrote a good number of macros though, both macro_rules! and various proc_macros. The latest iteration of overflower has both, for example. mutagen is a mutation testing tool built as a proc macro, and it's helper library has a bunch of macros, too. compact_arena uses macros to tie unique lifetime tags to arenas.

Also there are far more mutation testing frameworks. I maintain the rust-based mutagen one. There are also LLVM-based ones (etc. mull) that can cover multiple languages (but may yield mutations not expressible in your preferred one).

Cargo (and Rust) makes it so easy to write test cases that you should really use it to find these kinds of bugs. And there are other good test crates available: mutagen, quickcheck, etc.

I had a student completely reachitecture my mutagen tool, and saw some working on various clippy contributions.