summaryrefslogtreecommitdiff
path: root/FreeRTOS-Plus/Test/CMock/vendor/unity/examples/example_3/readme.txt
diff options
context:
space:
mode:
Diffstat (limited to 'FreeRTOS-Plus/Test/CMock/vendor/unity/examples/example_3/readme.txt')
-rw-r--r--FreeRTOS-Plus/Test/CMock/vendor/unity/examples/example_3/readme.txt13
1 files changed, 13 insertions, 0 deletions
diff --git a/FreeRTOS-Plus/Test/CMock/vendor/unity/examples/example_3/readme.txt b/FreeRTOS-Plus/Test/CMock/vendor/unity/examples/example_3/readme.txt
new file mode 100644
index 000000000..7371fea05
--- /dev/null
+++ b/FreeRTOS-Plus/Test/CMock/vendor/unity/examples/example_3/readme.txt
@@ -0,0 +1,13 @@
+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.