"Hi Manuel,..." <- > <@t-moe:matrix.org> Hi Manuel, > embedded-test author here. > What about creating a own test macro (similar to tokio::test), that when run on x86 does nothing special, and otherwise flashes the device, runs the test, and reports the result back? Surely this is beyond the current scope of embedded-test or defmt-test but I think this could work as as a workaround, without modifying cargo/rustc ? you mean a custom proc-macro per test function? How does this work together with running `cargo test`? In embedded-test you flash the binary with all tests included and use probe-rs to selectively execute the test fns if I understood that correctly. For now, I only created my own cargo runner that takes the binary, flashes it and receives defmt logs via OpenOCD using RTT. Memory access to the target while testing won't be possible for many chips from Infineon, but it is planned to use UART instead of RTT in these cases, so defmt should still work.