That's a good point, I guess what you want is that the build artifacts are produced and archived (or at least made read-only) before the test suite runs, to avo

That's a good point, I guess what you want is that the build artifacts are produced and archived (or at least made read-only) before the test suite runs, to avoid output cross-contamination from the test phase. I have only a cursory experience with rpm builds, but with the normal debhelper process that should be quite easy: just switch the order of the dh_install and dh_auto_test targets, and then make sure the debian/ directory is read-only before running the tests.