@@ -438,6 +438,36 @@ This will rarely be necessary. Most often, Unity will automatically detect if th
438438In the event that the compiler supports variadic macros, but is primarily C89 (ANSI), defining this option will allow you to use them.
439439This option is also not necessary when using Ceedling or the test runner generator script.
440440
441+ #### ` UNITY_SUPPORT_TEST_CASES `
442+
443+ Unity can automatically define all supported parameterized tests macros.
444+ That feature is disabled by default.
445+ To enable it, use the following example:
446+
447+ ``` C
448+ #define UNITY_SUPPORT_TEST_CASES
449+ ```
450+
451+ You can manually provide required ` TEST_CASE ` or ` TEST_RANGE ` macro definitions
452+ before including ` unity.h ` , and they won't be redefined.
453+ If you provide one of the following macros, some of default definitions will not be
454+ defined:
455+ | User defines macro | Unity will _ not_ define following macro |
456+ | ---| ---|
457+ | ` UNITY_EXCLUDE_TEST_CASE ` | ` TEST_CASE ` |
458+ | ` UNITY_EXCLUDE_TEST_RANGE ` | ` TEST_RANGE ` |
459+ | ` TEST_CASE ` | ` TEST_CASE ` |
460+ | ` TEST_RANGE ` | ` TEST_RANGE ` |
461+
462+ ` UNITY_EXCLUDE_TEST_* ` defines is not processed by test runner generator script.
463+ If you exclude one of them from definition, you should provide your own definition
464+ for them or avoid using undefined ` TEST_* ` macro as a test generator.
465+ Otherwise, compiler cannot build source code file with provided call.
466+
467+ _ Note:_
468+ That feature requires variadic macro support by compiler. If required feature
469+ is not detected, it will not be enabled, even though preprocessor macro is defined.
470+
441471## Getting Into The Guts
442472
443473There will be cases where the options above aren't quite going to get everything perfect.
0 commit comments