X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=automated-tests%2FREADME.md;h=59a7ca788e414c472688759c5efd3b53001e91e2;hb=d5aaf2ca7cb8f09d1a63d8eacf7c3cc5f732519e;hp=7a8e73381a1b2831d1b035ffa7920c8fcec5502d;hpb=9fad6395467277e82ac131d0b86b49ceeec259bd;p=platform%2Fcore%2Fuifw%2Fdali-adaptor.git diff --git a/automated-tests/README.md b/automated-tests/README.md index 7a8e733..59a7ca7 100644 --- a/automated-tests/README.md +++ b/automated-tests/README.md @@ -51,6 +51,8 @@ Building dali adaptor: 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 ------------------ @@ -103,16 +105,34 @@ To execute a subset of tests, you can run individual test sets, e.g. ./execute.sh dali-adaptor -To get coverage output (you need to first build dali libraries with +To get full coverage output (you need to first build dali libraries with --coverage), run ./coverage.sh +To check the coverage of your patch, (the build server uses its own copy +of these scripts), you can use + + ./patch-coverage.pl -q [diff-spec] + +to get a summary, or + + ./patch-coverage.pl [diff-spec] + +to get textual output, or + + ./patch-coverage.pl -o out.html [diff-spec] + +to get HTML output (used by build server). + +diff-spec is any refspec accepted by git-diff. If it's left out, it creates +a refspec to the latest commit, or uses the index/working tree. + Testing on target ================= -To build for target, first build and install dali-core, dali-adaptor and dali-toolkit, then build dali-capi without --keep-packs option. +To build for target, first build and install dali-core, dali-adaptor and dali-toolkit. You will need to install libconfig-tiny-perl: @@ -169,7 +189,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.