mirror/cJSON
1
0
Fork 0
mirror of https://github.com/DaveGamble/cJSON.git synced 2023-08-10 21:13:26 +03:00
Code Issues Projects Releases Wiki Activity
2c45ad7816
cJSON/examples/example_3
History
Max Bruckner 6b9b57be22 Squashed 'tests/unity/' content from commit 1782bab 
git-subtree-dir: tests/unity
git-subtree-split: 1782bab0bacd349a45bc215ff91f082912cd7a64
2017-02-07 21:30:57 +01:00
..
helper Squashed 'tests/unity/' content from commit 1782bab 2017-02-07 21:30:57 +01:00
src Squashed 'tests/unity/' content from commit 1782bab 2017-02-07 21:30:57 +01:00
test Squashed 'tests/unity/' content from commit 1782bab 2017-02-07 21:30:57 +01:00
rakefile_helper.rb Squashed 'tests/unity/' content from commit 1782bab 2017-02-07 21:30:57 +01:00
rakefile.rb Squashed 'tests/unity/' content from commit 1782bab 2017-02-07 21:30:57 +01:00
readme.txt Squashed 'tests/unity/' content from commit 1782bab 2017-02-07 21:30:57 +01:00
target_gcc_32.yml Squashed 'tests/unity/' content from commit 1782bab 2017-02-07 21:30:57 +01:00

readme.txt 

Example 3
=========

This example project gives an example of some passing, ignored, and failing tests.
It's simple and meant for you to look over and get an idea for what all of this stuff does.

You can build and test using rake. The rake version will let you test with gcc or a couple
versions of IAR.  You can tweak the yaml files to get those versions running.

Ruby is required if you're using the rake version (obviously).  This version shows off most of
Unity's advanced features (automatically creating test runners, fancy summaries, etc.)
Without ruby, you have to maintain your own test runners.  Do that for a while and you'll learn
why you really want to start using the Ruby tools.