Lines Matching full:unity

1 # Unity Configuration Guide
11 Unity is designed to run on almost anything that is targeted by a C compiler. It
17 All of Unity's configuration options are `#defines`. Most of these are simple
40 Unity will rely on `unity_config.h` for any further definitions it may need.
43 test itself. These defines need to take effect where ever unity.h is included.
45 unity.c when it's compiled.
57 certainly not every compiler you are likely to encounter. Therefore, Unity has a
64 The first thing that Unity does to guess your types is check `stdint.h`.
65 This file includes defines like `UINT_MAX` that Unity can use to
69 That way, Unity will know to skip the inclusion of this file and you won't
82 want Unity to check this file either, define this to make it skip the inclusion.
142 Unity will automatically include 64-bit support if it auto-detects it, or if
172 By default, Unity guesses that you will want single precision floating point
188 Unity aims for as small of a footprint as possible and avoids most standard
192 By default, Unity will print the actual results of floating point assertion
206 If enabled, Unity assumes you want your `FLOAT` asserts to compare standard C
218 If enabled, Unity assumes you want your `DOUBLE` asserts to compare standard C
235 documented in the big daddy Unity Assertion Guide, you will learn that they are
242 For further details on how this works, see the appendix of the Unity Assertion
255 Unity uses the `NULL` macro, which defines the value of a null pointer constant,
268 Unity provides a simple (and very basic) printf-like string output implementation,
307 which will come in handy to customize Unity's behavior for your specific
322 By default, Unity prints its results to `stdout` as it runs. This works
365 `near` or `far`. In these cases, you can give Unity a safe default for these by
376 By default, Unity outputs \n at the end of each line of output. This is easy
389 your system. Unity stores a set of internal scratchpads which are used to pass
421 exclude Unity's reliance on this by using this define. This dropped dependence
447 `TEST_ASSERT_NOT_EQUAL` shorthand assertions. Historically, Unity treated the
451 will allow you to specify how Unity will treat these assertions.
458   - AS_RAW - Unity assumes that you can compare the two values using `==` and `!=`
461   - AS_NONE - Unity will disallow the use of these shorthand macros altogether,
466 This will force Unity to support variadic macros when using its own built-in
467 RUN_TEST macro. This will rarely be necessary. Most often, Unity will automatically
480 must run your test suite on your target hardware, your Unity configuration will
540 So that's quite a macro, huh? It gives you a glimpse of what kind of stuff Unity
558 The defines and macros in this guide should help you port Unity to just about