* platforms, these macros come in handy.
* Your module_test should supply three basic functions:
*
+ * \code
* int module_testSetup(void)
* int module_testRun(void)
* int module_testTearDown(void)
+ * \endcode
*
* All of these should return 0 if ok or a value != 0 on errors.
*
* Then, at the end of your module_test you can write:
- * #include TEST_ONLY(whatuneed.h)
- * #include TEST_ONLY(whatuneed.c)
- * #include TEST_ONLY(...)
+ * \code
+ * #if UNIT_TEST
+ * #include <whatuneed.h>
+ * #include <whatuneed.c>
+ * #include <...>
*
- * TEST_MAIN(module);
+ * TEST_MAIN(module);
+ * #endif
+ * \endcode
*
- * The macro TEST_ONLY expand to nothing in non-TEST mode or to
- * the specified filename if _TEST is defined.
* Including directly into your module the file.c you need to
* run the test allows you to build and run the test compiling
* only one file.
#ifndef CFG_TEST_H
#define CFG_TEST_H
-#ifdef _TEST
+#include "cfg/cfg_arch.h"
+
+#if defined(ARCH_UNITTEST) && (ARCH & ARCH_UNITTEST)
+ #define UNIT_TEST 1
/**
* Macro used to generate a main() for a test to be compiled
return 3; \
return 0; \
}
+#else /* !TEST */
+ #define UNIT_TEST 0
- /** This macro will include the specified file only in test-mode */
- #define TEST_ONLY(file) PP_STRINGIZE(file)
-
-#else /* !_TEST */
-
- #define TEST_MAIN(module) /* nothing */
- #define TEST_ONLY(file) <cfg/nothing.h>
+ #define TEST_MAIN(module) /* nothing */
+#endif /* TEST */
-#endif /* _TEST */
/**
* Silent an assert in a test.