apostolof-ece-auth-gr
/
authRTESFinalAssignment
1
0
Fork 0
Code Releases Activity
Final assignment for the course "Real Time and Embedded Systems" of THMMY in AUTH university.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
10 Commits
2 Branches
0 Tags
405 MiB
 
 
 
 
 
Tree: 1a33ea4c39
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '1a33ea4c39'
${ noResults }
authRTESFinalAssignment/unity/examples/example_3
Apostolos Fanakis 987a54b31f
Init unit testing using Unity 		6 years ago
..
helper Init unit testing using Unity 6 years ago
src Init unit testing using Unity 6 years ago
test Init unit testing using Unity 6 years ago
rakefile.rb Init unit testing using Unity 6 years ago
rakefile_helper.rb Init unit testing using Unity 6 years ago
readme.txt Init unit testing using Unity 6 years ago
target_gcc_32.yml Init unit testing using Unity 6 years ago

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.