Added notes on _MESSAGE assertions (#331)

Added notes, why _MESSAGE assertions do not support printf style formatting and how users can work around this limitation (see #331)
This commit is contained in:
Roland Stahn
2018-07-21 16:57:53 +02:00
committed by GitHub
parent 1f6c782040
commit ac3cde30f5

View File

@ -104,6 +104,15 @@ becomes messageified like thus...
TEST_ASSERT_X_MESSAGE( {modifiers}, {expected}, actual, {size/count}, message )
Notes:
- The `_MESSAGE` variants intentionally do not support `printf` style formatting
since many embedded projects don't support or avoid `printf` for various reasons.
It is possible to use `sprintf` before the assertion to assemble a complex fail
message, if necessary.
- If you want to output a counter value within an assertion fail message (e.g. from
a loop) , building up an array of results and then using one of the `_ARRAY`
assertions (see below) might be a handy alternative to `sprintf`.
#### TEST_ASSERT_X_ARRAY Variants