Move tests that disable redaction into a separate crate

This is neccessary because rust runs all tests in the same process,
leading to tests failing randomly, because of other tests modifying the
global state. There is some proposal on the rust compiler-team github
repo but until that gets stabilized we have to use this hack instead
rust-lang/compiler-team#508

Cargo.toml

@@ -7,7 +7,12 @@ license = "MIT"
 repository = "https://github.com/primait/veil"
 
 [workspace]
-members = ["veil-macros", "veil-tests"]
+members = ["veil-macros", "veil-tests"
+# Because those tests deal with global state we need to run them in a separate process. 
+# The easiest/only way to do this with the standard rust test harness is to put them in a
+# separate crate
+,"veil-tests/disable-redaction-test"
+]
 
 [dependencies]
 veil-macros = { path = "veil-macros" }

veil-tests/disable-redaction-test/Cargo.toml

@@ -0,0 +1,10 @@
+[package]
+name = "disable-redaction-test"
+version = "0.1.0"
+edition = "2021"
+
+# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
+
+[dependencies]
+veil = { path = "../../" }
+veil-tests = { path = "../" }

veil-tests/disable-redaction-test/src/lib.rs

@@ -0,0 +1,12 @@
+#![cfg_attr(not(test), allow(unused))]
+/// Simple test that ensures veil can actually be disabled
+
+use veil::Redact;
+use veil_tests::{SENSITIVE_DATA, assert_has_sensitive_data};
+#[test]
+fn test_veil_can_be_disabled() {
+    #[derive(Redact)]
+    struct SensitiveWrapper(#[redact] String);
+    veil::set_debug_format(veil::DebugFormat::Plaintext).ok();
+    assert_has_sensitive_data(SensitiveWrapper(SENSITIVE_DATA[0].to_string()));
+}

veil-tests/src/redaction_tests.rs

@@ -147,11 +147,3 @@ fn test_sensitive_tuple_structs() {
         SENSITIVE_DATA[3],
     ));
 }
-
-#[test]
-fn test_veil_can_be_disabled() {
-    #[derive(Redact)]
-    struct SensitiveWrapper(#[redact] String);
-    veil::set_debug_format(veil::DebugFormat::Plaintext).ok();
-    assert_has_sensitive_data(SensitiveWrapper(SENSITIVE_DATA[0].to_string()));
-}