From: György Straub Date: Thu, 16 Jan 2020 11:21:22 +0000 (+0000) Subject: Updated automated-tests' README.md with more specific instructions / caveats. X-Git-Tag: dali_1.4.54~1 X-Git-Url: http://review.tizen.org/git/?p=platform%2Fcore%2Fuifw%2Fdali-toolkit.git;a=commitdiff_plain;h=f2a9888ac28a4ec42b89f02048762a2eea26f067;hp=f0297c0a6b916f97737e3e1b46b6368cfb59b997 Updated automated-tests' README.md with more specific instructions / caveats. Change-Id: Ia1f6863a516cbb4e8325fd1bb61af60b1bfd629e Signed-off-by: György Straub --- diff --git a/automated-tests/README.md b/automated-tests/README.md index e719dda..c062b8a 100644 --- a/automated-tests/README.md +++ b/automated-tests/README.md @@ -69,6 +69,8 @@ Building dali toolkit: Note, you __must__ use a local build and not a distributed build, and you __must__ also build with debug enabled to allow *DALI_ASSERT_DEBUG* to trigger on wrong behaviour ( Which should always be a test case failure! ) +Further note that, for the following, your gcov version must match the version of the compiler. + Building the tests ------------------ @@ -192,7 +194,7 @@ If you are adding test cases to existing files, then all you need to do is creat END_TEST; } -Note that **there must be no extra whitespace in the method signature** (i.e., it must violate our coding convention and follow __exactly__ this pattern: `int UtcDaliMyTestcaseName(void)`), as it's parsed by an awk script to auto-generate the testcase arrays in the main header file. +Note that **the parentheses in the method signature must not be empty** (i.e., it must violate our coding convention and follow __exactly__ this pattern: `int UtcDaliMyTestcaseName(void)`), as it's parsed by an awk script to auto-generate the testcase arrays in the main header file. Neither may any comments on the same line contain empty parentheses. You can contine to use the TET api, e.g. `tet_infoline`, `tet_result` and our test check methods `DALI_TEST_CHECK`, `DALI_TEST_EQUALS`, etc.