From 0193d0c7c77eee525517ef518de070b280275d0d Mon Sep 17 00:00:00 2001 From: Peter Thedens <pthedens@iastate.edu> Date: Mon, 13 Nov 2017 20:23:30 -0600 Subject: [PATCH] fix links in readme --- quad/doc/Unity_notes.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/quad/doc/Unity_notes.md b/quad/doc/Unity_notes.md index 5313622a0..a9c915498 100644 --- a/quad/doc/Unity_notes.md +++ b/quad/doc/Unity_notes.md @@ -2,15 +2,15 @@ - When using Unity, be sure to define `UNITY_INCLUDE_CONFIG_H` to use the [`unity_config.h`](/Unity/src/unity_config.h). (Details on why are in the -[Unity Configuration Guide](/Unity/doc/UnityConfigurationGuide.md).) +[Unity Configuration Guide](/Unity/docs/UnityConfigurationGuide.md).) - For the quad directory, this is done at compile-time of the Unity library [_here_](/Unity/src/Makefile#L4) and at compile-time of the test runner [_here_](/quad/library.mk#L58). Both rely on the flag defined [_here_](/quad/library.mk#L19). - Follow the examples in the [`Unity/examples`](/Unity/examples) for a guide, as well as the documentation in [`Unity/docs`](/Unity/docs) - - The [Unity Getting Started guide](/Unity/doc/UnityGettingStartedGuide.md) and the + - The [Unity Getting Started guide](/Unity/docs/UnityGettingStartedGuide.md) and the [Unity Assertions Cheat Sheet Suitable for Printing and Possibly Framing] -(/Unity/doc/UnityAssertionsCheatSheetSuitableforPrintingandPossiblyFraming.pdf) +(/Unity/docs/UnityAssertionsCheatSheetSuitableforPrintingandPossiblyFraming.pdf) are nice references - Generally, the format is to start `main()` with `UNITY_BEGIN()`, followed by calls to `RUN_TEST(test_function)` where `test_function` is a test to run, ended with -- GitLab