From a89d27229c1ec61732797066dd942ee15d0ee983 Mon Sep 17 00:00:00 2001 From: Nabil Bendafi Date: Sun, 13 Sep 2015 20:18:59 +0200 Subject: [PATCH] Fix typo in documentation --- docs/TESTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/TESTING.md b/docs/TESTING.md index f9fae89e27..dfbd5c0d2e 100644 --- a/docs/TESTING.md +++ b/docs/TESTING.md @@ -767,7 +767,7 @@ TEST(BusOut_digitalout_write, led_1_nc_2_nc_nc_3) ``` ## Example -In below example we will run two example unit tests that are now available. tests ```UT_1``` and ```UT_2``` are unit tests used for now only to check if mbed SDK works with CppUTest library and if tests are being executed. In future number of unit tests will increase, nothing is also stoping you from writing and executing your own unit tests! +In below example we will run two example unit tests that are now available. tests ```UT_1``` and ```UT_2``` are unit tests used for now only to check if mbed SDK works with CppUTest library and if tests are being executed. In future number of unit tests will increase, nothing is also stopping you from writing and executing your own unit tests! ### Example configuration By default unit tests ```UT_1``` and ```UT_2``` are not automated - simply test suite will ignore them. Also we do not want to create dependency to CppUTest library each time someone executes automation.