Where to place testing only shared code?

[zapta]

The documentation explains how to structure the tests in a tree under the test/ directory (good). let’s say that I have a few .h and .cpp testing utility files (not tests) which are used by the various tests. Where should I place them in the tree? For example, will test/src and test/include do the trick? How should I #include them?

https://docs.platformio.org/en/stable/advanced/unit-testing/structure/hierarchy.html

[dvdnwk]

I’ve had the same problem, no great solution…

• DnWiFiDoorLock/test/_common at master · MacDada/DnWiFiDoorLock · GitHub – /tests/_common/ contains some code that I use between multiple test files
• DnWiFiDoorLock/NullLoggerTest.cpp at master · MacDada/DnWiFiDoorLock · GitHub – example of a test using it (yep, ugly include, no idea how to do it better)
• DnWiFiDoorLock/asserts.h at master · MacDada/DnWiFiDoorLock · GitHub – some other testing–related code, but under an umbrella of the term “library”
• DnWiFiDoorLock/PrinterLoggerTest.cpp at master · MacDada/DnWiFiDoorLock · GitHub – example of a test using it, much better
• DnWiFiDoorLock/assertsTest.cpp at master · MacDada/DnWiFiDoorLock · GitHub – and the code for tests can also be tested

[zapta]

Thanks @dvdnwk, this is very useful. I think I will go with the test/common approach because it provides better separation between production and testing code.

[zapta]

… in my case test/common also contain a .cpp file and platformio wouldn’t build it as part of the test which breaks the build. As a workaround I reflect it in each test directory with a wrapper file:

test_utils.cpp

#include "../common/packet_data_test_utils.cpp"

I hope that this feature request will be accepted. It will simplify many things.

Please support multiple test_xxxx test cases in a single directory