Including Class .h and .cpp file in src folder and in test environment

[dvdnwk]

@jojos1220

I already saw that kind of workaround solution to put the project specific .h and .cpp file into the lib folder…actually i am not a fan of it, because it is actually not a lib at all. It is project specific stuff which should be accessable during Unit-Testing and its environment

That was (is) the first thing I’ve been asking here ;p

@jojos1220

Well, as i already said, the src folder is for esp32 environment and test_build_src will never-ever work on that. Maybe spamming all product specific files by #define / #ifndef would work of course but I think it is still a totally workaround on that…

I am currently thinking about, how big projects are solving this kind of issue…

Not a big project, learning experience mostly, but I also wanted to test as much as I can: GitHub - MacDada/DnWiFiDoorLock – In general I separated code into 3 sections: unit testable “raw” code, mockable Arduino lib layer code and untestable code.