cJSON/tests/unity/examples/example_3
Max Bruckner 18b4e2f941 Update Unity to release 2.4.1 2017-04-27 02:55:04 +02:00
..
helper Merge commit '6b9b57be226a505a9c9cdd9ed029f22495ce04ec' as 'tests/unity' 2017-02-07 21:30:57 +01:00
src Merge commit '6b9b57be226a505a9c9cdd9ed029f22495ce04ec' as 'tests/unity' 2017-02-07 21:30:57 +01:00
test Merge commit '6b9b57be226a505a9c9cdd9ed029f22495ce04ec' as 'tests/unity' 2017-02-07 21:30:57 +01:00
rakefile.rb Update Unity to release 2.4.1 2017-04-27 02:55:04 +02:00
rakefile_helper.rb Update Unity to release 2.4.1 2017-04-27 02:55:04 +02:00
readme.txt Merge commit '6b9b57be226a505a9c9cdd9ed029f22495ce04ec' as 'tests/unity' 2017-02-07 21:30:57 +01:00
target_gcc_32.yml Merge commit '6b9b57be226a505a9c9cdd9ed029f22495ce04ec' as 'tests/unity' 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.