From 25903e6eaaa0c068b9b51bdc93e659d257be6f4d Mon Sep 17 00:00:00 2001 From: Romain Forlot Date: Wed, 3 Oct 2018 15:28:03 +0200 Subject: Update documentation This adds some instructions to build test widget using SDK and basic instruction on how to test natively on your host as well as on a target board. Change-Id: I077fda253336883bec3cd0101e61467565d679ff Signed-off-by: Romain Forlot --- docs/WriteYourTests/2_LUATestFiles.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'docs/WriteYourTests/2_LUATestFiles.md') diff --git a/docs/WriteYourTests/2_LUATestFiles.md b/docs/WriteYourTests/2_LUATestFiles.md index 377b8f2..05752dd 100644 --- a/docs/WriteYourTests/2_LUATestFiles.md +++ b/docs/WriteYourTests/2_LUATestFiles.md @@ -1,7 +1,5 @@ # LUA Test files -First, ensure that you put your LUA tests files in the `lua.d` directory. - You have two differents things to take in account when you'll write your tests using this framework: *test* and *assertions*. @@ -14,4 +12,4 @@ several *assertions* which are all needed to succeed to valid the test. The framework came with several *test* and *assertion* functions to simply be able to test verb calls and events receiving. Use the simple one as often as possible and if you need more use the one that calls a callback. Specifying a -callback let you add assertions and enrich the test. \ No newline at end of file +callback let you add assertions and enrich the test. -- cgit 1.2.3-korg