Max Bruckner ab77a80e9b Squashed 'tests/unity/' changes from 1f52255..f96c055 8 năm trước cách đây
..
helper 6b9b57be22 Squashed 'tests/unity/' content from commit 1782bab 8 năm trước cách đây
src 6b9b57be22 Squashed 'tests/unity/' content from commit 1782bab 8 năm trước cách đây
test 6b9b57be22 Squashed 'tests/unity/' content from commit 1782bab 8 năm trước cách đây
rakefile.rb ab77a80e9b Squashed 'tests/unity/' changes from 1f52255..f96c055 8 năm trước cách đây
rakefile_helper.rb ab77a80e9b Squashed 'tests/unity/' changes from 1f52255..f96c055 8 năm trước cách đây
readme.txt 6b9b57be22 Squashed 'tests/unity/' content from commit 1782bab 8 năm trước cách đây
target_gcc_32.yml 6b9b57be22 Squashed 'tests/unity/' content from commit 1782bab 8 năm trước cách đây

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.