|
Name |
|
Date |
Size |
#Lines |
LOC |
| .. | | - | - |
| src/ | | 22-Mar-2025 | - | 468 | 375 |
| test/ | | 22-Mar-2025 | - | 413 | 320 |
| readme.md | D | 22-Mar-2025 | 1.5 KiB | 27 | 18 |
readme.md
1# Unity Fixtures
2
3This Framework is an optional add-on to Unity.
4By including unity_fixture.h in place of unity.h, you may now work with Unity in a manner similar to CppUTest.
5This framework adds the concepts of test groups and gives finer control of your tests over the command line.
6
7This framework is primarily supplied for those working through James Grenning's book on Embedded Test Driven Development, or those coming to Unity from CppUTest.
8We should note that using this framework glosses over some of the features of Unity, and makes it more difficult to integrate with other testing tools like Ceedling and CMock.
9
10## Dependency Notification
11
12Fixtures, by default, uses the Memory addon as well.
13This is to make it simple for those trying to follow along with James' book.
14Using them together is completely optional.
15You may choose to use Fixtures without Memory handling by defining `UNITY_FIXTURE_NO_EXTRAS`.
16It will then stop automatically pulling in extras and leave you to do it as desired.
17
18## Usage information
19
20By default the test executables produced by Unity Fixtures run all tests once, but the behavior can be configured with command-line flags.
21Run the test executable with the `--help` flag for more information.
22
23It's possible to add a custom line at the end of the help message, typically to point to project-specific or company-specific unit test documentation.
24Define `UNITY_CUSTOM_HELP_MSG` to provide a custom message, e.g.:
25
26 #define UNITY_CUSTOM_HELP_MSG "If any test fails see https://example.com/troubleshooting"
27