Fix documentation.
authorbatt <batt@38d2e660-2303-0410-9eaa-f027e97ec537>
Fri, 29 Aug 2008 20:32:50 +0000 (20:32 +0000)
committerbatt <batt@38d2e660-2303-0410-9eaa-f027e97ec537>
Fri, 29 Aug 2008 20:32:50 +0000 (20:32 +0000)
git-svn-id: https://src.develer.com/svnoss/bertos/trunk@1758 38d2e660-2303-0410-9eaa-f027e97ec537

bertos/cfg/test.h

index 374250269fa0a54c073bc10800c2e8dc78c32ebb..048ff57b8855b3de2192f10f90e0399ec5869474 100644 (file)
  *
  * Then, at the end of your module_test you can write:
  * \code
- * #include TEST_ONLY(whatuneed.h)
- * #include TEST_ONLY(whatuneed.c)
- * #include TEST_ONLY(...)
+ * #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.