Merge "Use GLES 3.0 by default" into devel/master

[platform/core/uifw/dali-core.git] / automated-tests / README.md

diff --git a/automated-tests/README.md b/automated-tests/README.md
index e7a8af7..8beb8b0 100644 (file)
--- a/automated-tests/README.md
+++ b/automated-tests/README.md
@@ -1,6 +1,4 @@
-%PageOutline
-
-Testing environment
+Testing environment   {#auto_testing}
 ===================
 
 The new test environment from Tizen is the Web-TCT test suite. This was written for testing web components, but can easily be used for testing Dali.
@@ -10,7 +8,7 @@ Each of the DALi repositories, **dali-core**, **dali-adaptor** and **dali-toolki
 Installation
 ------------
 
-There are usage instructions and installation instructions [here](http://download.tizen.org/tct/2.2.1/Manual/Web_TCT_2.2.1_User_Guide_v1.0.pdf)
+There are usage instructions and installation instructions on the Tizen.org website [here](http://download.tizen.org/tct/2.2.1/Manual/Web_TCT_2.2.1_User_Guide_v1.0.pdf)
 
 These are device specific instructions, however, installing the test suite will also provide the relevant packages for running tests on Ubuntu ( follow the first block of quickstart instructions below ).
 
@@ -82,29 +80,34 @@ Or without cleaning down the build area (Useful for fast build/run/debug cycles)
 Executing the tests
 -------------------
 
+To see a list of all of the options:
+
+    ./execute.sh -h
+
 To execute tests, cd into automated-tests and run
 
     ./execute.sh
 
 This will execute dali and dali-internal test sets. Note that the output summary for the first will be printed before running the second.
 
-By default the tests execute in parallel, which is faster but does not produce a single output file (summary.xml).  Use this to execute the tests in series:
+By default the tests execute in parallel, which is faster but does not produce any test case output files.  Use this to execute the tests in series and log test output to stdout/err
 
-    ./execute.sh -s
+    ./execute.sh -S
 
-To see the summary.xml results, execute the tests in series and open as follows:
+To use test kit lite, (which is very slow),
 
-    firefox --new-window summary.xml
+    ./execute.sh -s
 
-To see a list of all of the options:
+To see the test kit lite results, copy the style folder from web-tct_2.2.1_r1/tools/tct-mgr/style into automated-tests and run
 
-    ./execute.sh -h
+    firefox --new-window summary.xml
 
 To execute a subset of tests, you can run individual test sets, e.g.
 
     ./execute.sh dali
 
-To get coverage output, run
+To get coverage output (you need to first build dali libraries with
+--coverage), run
 
     ./coverage.sh
 
@@ -195,10 +198,10 @@ On desktop, you can debug the tests by running gdb on the test program:
 
 replace `<TestCase>` with the name of the failing testcase.
 
-For example, using testcase UtcDaliNinePatch01 from the dali-core test suite:
+For example, using testcase UtcDaliActorAddP from the dali-core test suite:
 
     $ gdb build/src/dali/tct-dali-core
-    gdb> r UtcDaliNinePatch01
+    gdb> r UtcDaliActorAddP
 
 
 On target, you can re-install the test RPM and associated debug RPMs manually using