X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=automated-tests%2FREADME.md;h=7d363fb42ea7ed9b89f478cc3a24b9e369182a36;hb=6bd7c97fb0d7506507a065a80406e429e0f7332f;hp=b2fc212f1f2e5f9317a7680d1a52f78163a312d7;hpb=e3bd390c475c47c71f5ee4b93406c1907e58a117;p=platform%2Fcore%2Fuifw%2Fdali-core.git diff --git a/automated-tests/README.md b/automated-tests/README.md index b2fc212..7d363fb 100644 --- a/automated-tests/README.md +++ b/automated-tests/README.md @@ -105,16 +105,35 @@ To execute a subset of tests, you can run individual test sets, e.g. ./execute.sh dali -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: @@ -226,14 +245,14 @@ Debugging On desktop, you can debug the tests by running gdb on the test program: $ cd automated-tests - $ gdb build/src/dali/tct-dali-core + $ ./execute.sh -d gdb> r replace `` with the name of the failing testcase. For example, using testcase UtcDaliActorAddP from the dali-core test suite: - $ gdb build/src/dali/tct-dali-core + $ ./execute.sh -d UtcDaliActorAddP gdb> r UtcDaliActorAddP