Lines Matching +full:runner +full:- +full:before +full:- +full:script

1 # Unity - Getting Started
15 Unity was designed to be cross-platform.
59 - `src` - This is the code you care about! This folder contains a C file and two header files.
61 - `docs` - You're reading this document, so it's possible you have found your way into this folder …
63 - `examples` - This contains a few examples of using Unity.
64 - `extras` - These are optional add ons to Unity that are not part of the core project.
66 - `test` - This is how Unity and its scripts are all tested.
69 - `auto` - Here you will find helpful Ruby scripts for simplifying your test workflow.
79 The setUp function can contain anything you would like to run before each test.
84 If you're using Ceedling or the test runner generator script, you may leave these off completely.
100 … your build process, you might consider making use of our handy [generate_test_runner.rb][] script.
141 When writing your own `main()` functions, for a test-runner.
156 These macros perform the necessary setup before the test is called and handles clean-up and result …
221 - On hardware, you have too many constraints (processing power, memory, etc),
222 - On hardware, you don't have complete control over all registers,
223 - On hardware, unit testing is more challenging,
224 - Unit testing isn't System testing. Keep them separate.