diff --git a/unit_tests/readme.md b/unit_tests/readme.md
index 2cedd9d171..aad39d4fd0 100644
--- a/unit_tests/readme.md
+++ b/unit_tests/readme.md
@@ -1,11 +1,14 @@
-TL, DR: just follow [tests](tests) folder as examples
+TL, DR: just follow [tests](tests) folder as examples.
+
+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.
+1. To run only one test uncomment and modify [main.cpp](https://github.com/rusefi/rusefi/blob/master/unit_tests/main.cpp) line ``::testing::GTEST_FLAG(filter)``
 
 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.
+
 
 [Code Coverage Report](https://rusefi.com/docs/unit_tests_coverage/)
 
@@ -18,4 +21,4 @@ Trigger images generation is still a two-step manual process:
 Step 1: Invoke unit_tests. One of the unit_tests artifacts is triggers.txt
 
 Step 2: Once we have triggers.txt updated by unit_tests we can invoke firmware/gen_trigger_images.bat in order
-to generate actual trigger images.
\ No newline at end of file
+to generate actual trigger images.