From 24b6f089791f73119724400a17fabd99be251338 Mon Sep 17 00:00:00 2001 From: rusefi Date: Sun, 25 Aug 2019 23:31:39 -0400 Subject: [PATCH] unit tests code coverage #653 --- firmware/readme.md | 6 ++++++ unit_tests/readme.md | 4 +++- unit_tests/run_clean_gcov.sh | 1 + 3 files changed, 10 insertions(+), 1 deletion(-) create mode 100644 firmware/readme.md diff --git a/firmware/readme.md b/firmware/readme.md new file mode 100644 index 0000000000..65e8ac09e5 --- /dev/null +++ b/firmware/readme.md @@ -0,0 +1,6 @@ + +[Doxygen](https://rusefi.com/docs/html/) + +[Q&A on source code](https://rusefi.com/forum/viewtopic.php?f=5&t=10) + +See also [../unit_tests](../unit_tests) \ No newline at end of file diff --git a/unit_tests/readme.md b/unit_tests/readme.md index 20075422e3..084cade80a 100644 --- a/unit_tests/readme.md +++ b/unit_tests/readme.md @@ -3,4 +3,6 @@ In this folder we have rusEfi unit tests using https://github.com/google/googlet 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 +1. Execute rusefi_test binary on your PC/Mac, it's expected to say SUCCESS and not fail :) Googletest will also print results summary. + +[Code Coverage Report](https://rusefi.com/docs/unit_tests_coverage/) \ No newline at end of file diff --git a/unit_tests/run_clean_gcov.sh b/unit_tests/run_clean_gcov.sh index 594a84469e..3816a48cd2 100644 --- a/unit_tests/run_clean_gcov.sh +++ b/unit_tests/run_clean_gcov.sh @@ -3,3 +3,4 @@ make clean make -j4 build/rusefi_test +./run_gcov.sh \ No newline at end of file