After reading Tracing inside of unit tests
I started using this, and it works fine for native/desktop unit tests, but it is not available for target unit tests, at least not in my setup.
Checking on which unity.h files are used in both scenarios, I’ve found some differences:
on my Windows10 this is the path for unity.h
and here is the definition for TEST_MESSAGE
on the target (ESP32 in my case) this is the path
and there is no definition of TEST_MESSAGE
I have Espressif32 platform updated to V3.5.0
Does anyone have a solution for this ?
Frameworks which have include their own copy of Unity are problematic, because really PlatformIO wants that its own Unity version is included. I’ve already reported an issue related to this in Unit testing impossible for frameworks including Unity themselves · Issue #3980 · platformio/platformio-core · GitHub, which occurs when there’s pre-definition / precompiled version of the Unity functions. Your problem seems to be slightly different however (otherwise you would have run into this linking error long before), in regards to that a #include <unity.h> picks up the wrong version. I think this shoud be reported as a seperate issue in Issues · platformio/platformio-core · GitHub (the core because it can potentially occur not only in platform-espressif32 but also other frameworks).