From 9d3805eafccd728241668d46caca1c1a5cb40239 Mon Sep 17 00:00:00 2001 From: rusefi Date: Sun, 25 Aug 2019 02:49:11 -0400 Subject: [PATCH] readme --- unit_tests/readme.md | 6 ++++++ unit_tests/readme.txt | 7 ------- 2 files changed, 6 insertions(+), 7 deletions(-) create mode 100644 unit_tests/readme.md delete mode 100644 unit_tests/readme.txt diff --git a/unit_tests/readme.md b/unit_tests/readme.md new file mode 100644 index 0000000000..20075422e3 --- /dev/null +++ b/unit_tests/readme.md @@ -0,0 +1,6 @@ +In this folder we have rusEfi unit tests using https://github.com/google/googletest + +Unit tests are not aware of ChibiOS or ARM or else, they are just plain C/C++ which you build for your desktop, not your MCU. + +1. Run 'make' to build desktop binary. +1. Execute rusefi_test binary on your PC/Mac, it's expected to say SUCCESS and not fail :) Googletest will also print results summary. \ No newline at end of file diff --git a/unit_tests/readme.txt b/unit_tests/readme.txt deleted file mode 100644 index 3d42bce8d1..0000000000 --- a/unit_tests/readme.txt +++ /dev/null @@ -1,7 +0,0 @@ -In this folder we have a naive test suite. - -I am not sure what is the best approach to tests in C (someone can educate me), but my approach is: - -Unit tests are not aware of ChibiOS or ARM or else, they are just plain C/C++ which you build for your desktop, not your MCU. - -Run 'make' to build desktop binary & run it on your PC/Mac, it's expected to say SUCCESS and not fail :) \ No newline at end of file