Lines Matching +full:find +full:- +full:up

1 # Unity - Getting Started
13 These team up to provide functions and macros to make testing easier.
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.
87 If your compiler complains that it can't find setUp or tearDown when it links, you'll know you need…
111     // set stuff up here
115     // clean stuff up here
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 …
182 The first `TEST_PROTECT` sets up the feature, and handles emergency abort cases.
213 This is the single biggest challenge to picking up a new unit testing framework, at least in a lang…
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.
228 Native apps have the advantages of being faster and easier to set up.
239 *Find The Latest of This And More at [ThrowTheSwitch.org][]*