1 Testing environment {#auto_testing}
4 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.
6 Each of the DALi repositories, **dali-core**, **dali-adaptor** and **dali-toolkit**, have their own test suites under the `automated-tests` folder. Within the src folder are a number of secondary folders - these correspond to 'managed' tests (for testing the frozen API for products), unmanaged tests (tests for other APIs) and internal (for desktop testing only)
11 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)
13 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 ).
15 If you are planning on running tests on device, then flash your handset with latest image, or turn off ssh: `set_usb_debug.sh --mtp-sdb` and plug it in, then follow the quickstart instructions repeated below.
20 For target or desktop testing:
23 wget http://download.tizen.org/tct/2.2.1/2.2.1_r1/web-tct_2.2.1_r1.tar.gz
24 sudo tar xzf web-tct_2.2.1_r1.tar.gz
25 cd web-tct_2.2.1_r1/tools
26 sudo -E ./tct-config-host.sh
29 If you are planning on running tests on device, then plug in your freshly flashed device and run the following commands:
31 sudo apt-get install sdb
32 ./tct-config-device.sh
34 **NOTE:** After flashing a handset, you will need to run this step of the installation again.
39 Building libraries with coverage options
40 ----------------------------------------
42 Building dali adaptor:
44 cd dali-adaptor # the location of your dali-adaptor repository
48 git clean -fxd . # Only do this in the build folder
50 CXXFLAGS='-g -O0 --coverage' LDFLAGS='--coverage' ./configure --prefix=$DESKTOP_PREFIX --enable-debug
53 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! )
58 Run the following commands:
63 This will build dali-adaptor, dali-adaptor-internal and dali-platform-abstraction test sets.
65 Test sets can be built individually:
67 ./build.sh dali-adaptor
69 They can also be built without regenerating test case scripts (Useful for quicker rebuilds)
71 ./build.sh -n dali-adaptor
73 Or without cleaning down the build area (Useful for fast build/run/debug cycles)
75 ./build.sh -n -r dali-adaptor
81 To execute tests, cd into automated-tests and run
85 This will execute dali, dali-unmanaged and dali-internal test sets. Note that the output summary for the first will be printed before running the second.
87 To execute a subset of tests, you can run individual test sets, e.g.
89 ./execute.sh dali-adaptor
91 or for finer granularity, specify a test source file:
93 ./execute.sh dali-adaptor-internal utc-Dali-GifLoader.cpp
95 To see the results, you can open the summary.xml in firefox.
97 firefox --new-window summary.xml
99 To get coverage output, run
107 To build for target, first build and install dali-core, dali-adaptor and dali-toolkit, then build dali-capi without --keep-packs option.
109 You will need to install libconfig-tiny-perl:
111 sudo apt-get install libconfig-tiny-perl
113 If you use a non-standard `GBS_ROOT` then you will need to edit the tcbuild script to match your configuration - change line 96 and add a -B option with your GBS-ROOT path (line 96 = `gbs build -A armv7l --spec core-$1-tests.spec --include-all --keep-packs` ).
114 To install on device from a non-standard GBS_ROOT, also modify line 28 (`RPM_DIR="$HOME/GBS-ROOT/local/repos/$PROFILE/armv7l/RPMS"`).
116 For Dali Adaptor, cd into automated-tests, and use:
118 sudo ./tcbuild build dali-adaptor
119 sudo ./tcbuild build dali-adaptor-internal
120 sudo ./tcbuild build dali-platform-abstraction
121 ./tcbuild install dali-adaptor
122 ./tcbuild install dali-adaptor-internal
123 ./tcbuild install dali-platform-abstraction
125 Ensure your handset's filesystem is writable:
127 sdb shell su -c "change-booting-mode.sh --update"
129 To execute tests, cd into automated-tests and run
133 This will bring up the java test suite program. You should see the Plan pane with a list of all tests in. Select the tct-dali-core-tests and tct-dali-unmanaged-tests. and you will be offered a dialog to choose a test plan: either create a new one or use temp.
134 Select dali test suite, and click Run, then "Create a new plan", and call it "Dali-Core" or some such. It will now run the dali-test suite.
136 You can find the output files under /opt/tct/manager/result/
145 If you are adding test cases for new or existing managed API (CAPI), you need to add your changes to the src/dali mirror, and copy your change to the managed test suite in core-api. You need to inform HQ of your update.
150 If you are adding test cases for unmanaged API, you need to add your changes to the src/dali-adaptor-unmanaged test suite.
155 If you are adding tests for internal API, then this will only work on desktop, and you should add your tests to the src/dali-adaptor-internal test suite.
160 If you are adding test cases to existing files, then all you need to do is create functions with the method signature
162 int UtcTestcase(void)
164 TestApplication application;
170 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.
172 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.
174 If you need any non-test methods or variables, ensure they are wrapped in an anonymous namespace.
176 If you are adding new test files, then you need to add the filename to the SET(TC_SOURCES...
177 section of CMakeLists.txt (this is also parsed by an awk script prior to building)
182 On desktop, you can debug the tests by running gdb on the test program:
185 $ gdb build/src/dali/tct-dali-core
188 replace `<TestCase>` with the name of the failing testcase.
190 For example, using testcase UtcDaliLoadCompletion from the dali-platform-abstraction test suite:
192 $ gdb build/src/dali-platform-abstraction/tct-dali-platform-abstraction-core
193 gdb> r UtcDaliLoadCompletion
196 On target, you can re-install the test RPM and associated debug RPMs manually using
198 sdb push <test-package>.rpm /tmp
200 After installing the rpm and it's debug RPMs, you can find the executable in /opt/usr/bin/tct-dali-core. First ensure you have smack permissions set:
202 chsmack -e "^" /usr/bin/gdb
203 chsmack -e "^" /opt/usr/bin/tct-dali-adaptor-core/tct-dali-adaptor-core
205 then run it under gdb as above.
211 If when running tct-mgr tests, if "Health-Check get" fails and leaves a white screen on the device, you will need to run `tct-config-device.sh` from your `web-tct/tools` directory (wherever you untarred it) and power cycle your handset. If that still fails, you can work-around the issue by running "`mkdir –p /opt/usr/media/Documents/tct/`" on target – you may also need to kill the getCapabilities app from App Manager on the handset)
213 If the test results show that the test cases fail with "Undefined reference to XXX", it means you have probably failed to update the dali packages on target.
215 If all the tests are failing then make sure that you have enabled the engineering mode on the target with the 'change-booting-mode.sh --update' command in sdb shell, as the tests may not have installed correctly.