|
Home | Libraries | People | FAQ | More |
auto_start_dbgbuild_infocatch_system_errorscolor_outputdetect_fp_exceptionsdetect_memory_leakshelplist_contentlist_labelslog_formatlog_levellog_sinkloggeroutput_formatrandomreport_formatreport_levelreport_memory_leaks_toreport_sinkresult_coderun_testsave_patternshow_progressuse_alt_stackusagewait_for_debuggerFollowing sections provide detailed specification for all Unit Test Framework runtime parameters. Each parameter specification includes:
<prefix><name>[<separator><value>]. For example: --param=<value>.
[] around separator and
value indicate that argument value is optional. For example: -q[ <value>].
![[Note]](../../../../../../doc/src/images/note.png) |
Note |
|---|---|
|
All command line argument formats support parameter name guessing. What this means is that is if command like format is like this: --long_parameter_name=<value> you can in fact use any unambiguous prefix of the parameter name to specify the argument. For example: --long_param=123 or --long_p=123. If parameter name prefix you chose is ambiguous the framework lets you know which parameters match specified prefix. For example, try --log=all |
The Unit Test Framework runtime parameters take value of the following types: string, boolean, enumeration, unsigned, long. Formats required for values of these types are following:
Values of these types are expected in the same format they are represented in C++.
Values of these types are options with yes/no or true/false meaning. True values are represented by case insensitive strings: "Y", "YES", "TRUE", "1". False values are represented by case insensitive strings: "N", "NO", "FALSE", "0".
Values of an enumeration type are expected as case sensitive strings representing enumeration value names. Each parameter with an enumeration value lists all valid names in a parameter`s description.