I’m not sure I really get the point of the macro: is it to disable unit tests for the framework, or disable using unit test related classes and functionality altogether?
Right now, with that macro set to a disabled state, I haven’t access to the unit test categories.
#if JUCE_UNIT_TESTS #include "unit_tests/juce_UnitTestCategories.h" #endif
Thing is, I don’t care to build and run JUCE’s unit tests - I only care about my own.
In my opinion it would be useful to open the header up for public use.