Jonathan Reichelt Gjertsen
27ef0eb44e
Fix some formatting errors in the assertions reference
2021-05-24 14:52:24 +02:00
Alari Õis
ec31dfacad
Fixed typos in documentation
2020-04-25 07:14:21 +03:00
mvandervoord
99199515fd
Update documentation.
...
Add UNITY_PRINT_TEST_CONTEXT (thanks @jlindgren90 !)
Replaces PR #473
2020-03-17 15:01:46 -04:00
mvandervoord
71e77ce6fb
Added NOT-EQUAL int variants.
...
Organized Unit Tests
2020-03-16 18:45:40 -04:00
mvandervoord
bad429428d
Add assertion for checking empty null-terminated arrays. This is particularly useful for check c strings.
2020-03-16 15:04:40 -04:00
mvandervoord
354e2b4da6
Added set of assertions for checking CHAR's and CHAR arrays (not as strings)
2019-10-28 16:54:32 -04:00
Jason Heeris
86b19304ed
Added num_elements parameter to docs for TEST_ASSERT_INTn_ARRAY_WITHIN().
2019-10-25 14:37:00 +11:00
Mark VanderVoord
0000f1e6d2
Add TEST_MESSAGE for outputting messages without aborting a test and _MESSAGE variant to TEST_PASS collection.
2019-07-06 11:02:32 -04:00
Mark VanderVoord
f2d826c7c5
- Added options for how to handle TEST_ASSERT_EQUAL shorthand
...
- Tweak a couple style problems with Ruby scripts.
2019-07-03 15:03:03 -04:00
Dom Postorivo
9340582797
ARRAY_WITHIN in unity
2019-04-20 14:10:56 -04:00
Deryew
e72dfafd44
Fixed some grammar errors on docs
...
Fixed grammar errors and some sentences to make it easier to understand
2018-07-30 10:53:02 +08:00
Roland Stahn
ac3cde30f5
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 )
2018-07-21 16:57:53 +02:00
Dom Postorivo
f2fdf1a133
Added Greater than and Less than asserts from other PR
2017-05-13 15:59:51 -04:00
Mark VanderVoord
2c7629a0ae
Documentation Updates
2017-04-07 13:14:32 -04:00
toby
1e4396745c
Add EACH_EQUAL changes
2017-03-29 15:09:01 +01:00
toby
e2cc67918d
Add newlines after headings for best practice, trim trailing spaces & convert sneaky incorrectly coded chars
...
blank newline after headins is apparently best practice according to http://stackoverflow.com/q/42953462/1292918
2017-03-29 15:01:23 +01:00
toby
c48f6c9420
Add Github Markdown versions of documents
...
Add GFM version of getting started guide PDF
Add GFM version of configuration guide PDF
Add GFM version of helper scripts guide PDF
Add GFM version of coding standard PDF
Add GFM version of assertions reference PDF
Change markdown used to italicise line. Switched to use asterisk markdown instead
2017-03-29 14:46:31 +01:00
