2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-2dtransforms-css3-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-2dtransforms-css3-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-2dtransforms-css3-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-2dtransforms-css3-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-2dtransforms-css3-tests" -f /usr/share/tct-2dtransforms-css3-tests/tests.xml -o /tmp/tct-2dtransforms-css3-tests.results.xml -A
-5. Click the "Run" button of the manual harness. A test widget is downloaded. You need to install the widget in WRT, and then load the widget to continue with the tests(for example, the widget UI will show the test results). You also need to fill the result in manual tests harness for result collection.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to yugang.fan@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-2dtransforms-css3-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-2dtransforms-css3-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
-2. To enable more auto cases.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-2dtransforms-css3-tests/tests.xml -e "WRTLauncher" -o tct-2dtransforms-css3-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-3dtransforms-css3-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-3dtransforms-css3-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-3dtransforms-css3-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-3dtransforms-css3-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-3dtransforms-css3-tests" -f /usr/share/tct-3dtransforms-css3-tests/tests.xml -o /tmp/tct-3dtransforms-css3-tests.results.xml -A
-5. Click the "Run" button of the manual harness. A test widget is downloaded. You need to install the widget in WRT, and then load the widget to continue with the tests(for example, the widget UI will show the test results). You also need to fill the result in manual tests harness for result collection.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to yugang.fan@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-3dtransforms-css3-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-3dtransforms-css3-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
-2. To enable more auto cases.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-3dtransforms-css3-tests/tests.xml -e "WRTLauncher" -o tct-3dtransforms-css3-tests.results.xml
----------------------------------------------
Copyright (c) 2012 Intel Corporation.
-Redistribution and use in source and binary forms, with or without modification,
+Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
-* Redistributions of works must retain the original copyright notice, this list
+* Redistributions of works must retain the original copyright notice, this list
of conditions and the following disclaimer.
-* Redistributions in binary form must reproduce the original copyright notice,
- this list of conditions and the following disclaimer in the documentation
+* Redistributions in binary form must reproduce the original copyright notice,
+ this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
-* Neither the name of Intel Corporation nor the names of its contributors
- may be used to endorse or promote products derived from this work without
+* Neither the name of Intel Corporation nor the names of its contributors
+ may be used to endorse or promote products derived from this work without
specific prior written permission.
-THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION BE LIABLE FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
-OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
-EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
+EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Authors:
- Cao, Jenny <jenny.q.cao@intel.com>
+ Cao, Jenny <jenny.q.cao@intel.com>
+
----------------------------------------------
This test suite is for testing Tizen Alarm API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/alarm.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-alarm-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-alarm-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-alarm-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-alarm-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-alarm-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-alarm-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-alarm-tizen-tests" -f device:/usr/share/tct-alarm-tizen-tests/tests.xml -o /tmp/tct-alarm-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-alarm-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-alarm-tizen-tests/tests.xml -e "WRTLauncher" -o tct-alarm-tizen-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-animations-css3-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-animations-css3-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-animations-css3-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-animations-css3-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-animations-css3-tests" -f /usr/share/tct-animations-css3-tests/tests.xml -o /tmp/tct-animations-css3-tests.results.xml -A
-5. Click the "Run" button of the manual harness. A test widget is downloaded. You need to install the widget in WRT, and then load the widget to continue with the tests(for example, the widget UI will show the test results). You also need to fill the result in manual tests harness for result collection.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to yugang.fan@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-animations-css3-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-animations-css3-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
-2. To enable more auto cases.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-animations-css3-tests/tests.xml -e "WRTLauncher" -o tct-animations-css3-tests.results.xml
Han Ruijing <ruijingx.a.han@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
3. Run the cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only got the source code and Testkit-Lite set up on your host.
-If you have got tct-animationtiming-w3c-tests RPM packages on the test machine, you can directly go to step 3;
+If you have got tct-animationtiming-w3c-tests ZIP packages on the test machine, you can directly go to step 3;
if you have not installed Testkit-lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-animationtiming-w3c-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-animationtiming-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-animationtiming-w3c-tests" -f device:"/usr/share/tct-animationtiming-w3c-tests/tests.xml"
-5. Please make sure the network is connected when testing animationtiming.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-
-Note: If there is any defects in this test suite, please do not hesitate to contact us by the email ruijingx.a.han@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-animationtiming-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-animationtiming-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-animationtiming-w3c-tests/tests.xml -e "WRTLauncher" -o tct-animationtiming-w3c-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-appcache-html5-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-appcache-html5-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-appcache-html5-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-appcache-html5-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-appcache-html5-tests" -f /usr/share/tct-appcache-html5-tests/tests.xml -o /tmp/tct-appcache-html5-tests.appcache.results.xml
-Note:
-1. If you run appcache manual tests on Chromimum, follow the above description to complete the test cases.
-2. If you run appcache manual tests on Lunchbox, clear browser cache first.
+2. Build ZIP package by running the following command:
+ ./pack.sh
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-appcache-html5-tests-<version>.zip -d /opt/usr/media/tct
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to Fan Weiwei <weiwix.fan@intel.com>.
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-appcache-html5-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-appcache-html5-tests/tests.xml -e "WRTLauncher" -o tct-appcache-html5-tests.results.xml
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To format existing test cases.
-2. To design tests to cover all specifications P1,P2 and P3 testing.
+Note:
+1. If you run appcache manual tests on Chromimum, follow the above description to complete the test cases.
+2. If you run appcache manual tests on Lunchbox, clear browser cache first.
----------------------------------------------
Copyright (c) 2012 Intel Corporation.
-Redistribution and use in source and binary forms, with or without modification,
+Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
-* Redistributions of works must retain the original copyright notice, this list
+* Redistributions of works must retain the original copyright notice, this list
of conditions and the following disclaimer.
-* Redistributions in binary form must reproduce the original copyright notice,
- this list of conditions and the following disclaimer in the documentation
+* Redistributions in binary form must reproduce the original copyright notice,
+ this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
-* Neither the name of Intel Corporation nor the names of its contributors
- may be used to endorse or promote products derived from this work without
+* Neither the name of Intel Corporation nor the names of its contributors
+ may be used to endorse or promote products derived from this work without
specific prior written permission.
-THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION BE LIABLE FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
-OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
-EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
+EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Authors:
- Cao, Jenny <jenny.q.cao@intel.com>
+ Cao, Jenny <jenny.q.cao@intel.com>
+
----------------------------------------------
This test suite is for testing Tizen Application Control interface from:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/application.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-appcontrol-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-appcontrol-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-appcontrol-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-appcontrol-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-appcontrol-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-appcontrol-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-appcontrol-tizen-tests" -f device:/usr/share/tct-appcontrol-tizen-tests/tests.xml -o /tmp/tct-appcontrol-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-appcontrol-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-appcontrol-tizen-tests/tests.xml -e "WRTLauncher" -o tct-appcontrol-tizen-tests.results.xml
- ----------------------------------------------
+----------------------------------------------
License
----------------------------------------------
Copyright (c) 2012 Intel Corporation.
Mariusz Polasinski <m.polasinski@samsung.com>
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen Application API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/application.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Pre-conditions
----------------------------------------------
ApplicationManager_addAppInfoEventListener_onupdated
ApplicationInformationEventCallback_onupdated
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-application-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-application-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-application-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
+2. Build ZIP package by running the following command:
+ ./pack.sh
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-application-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-application-tizen-tests-<version>.zip -d /opt/usr/media/tct
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-application-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-application-tizen-tests/inst.sh
+
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-application-tizen-tests/tests.xml -e "WRTLauncher" -o tct-application-tizen-tests.results.xml
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-application-tizen-tests" -f device:/usr/share/tct-application-tizen-tests/tests.xml -o /tmp/tct-application-tizen-tests.results.xml
----------------------------------------------
Some special tests
3. ApplicationManager_addAppInfoEventListener_onupdated.html, ApplicationInformationEventCallback_onupdated.html - manual tests
Make sure that TCTAppInfoEventTest1 application is installed (you can install it from: My Files/Phone/Others).
Run the test and then install TCTAppInfoEventTest2.wgt application from: My Files/Phone/Others directory, finally look at the results.
-
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-audio-html5-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-audio-html5-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-audio-html5-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-audio-html5-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-audio-html5-tests" -f /usr/share/tct-audio-html5-tests/tests.xml -o /tmp/tct-audio-html5-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-1. Chromium browser is not enabled with H.264 or AAC codec because of license issue.
-
-Note: You can report the defects of this test suite to zhiqiang.zhang@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-audio-html5-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-audio-html5-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-audio-html5-tests/tests.xml -e "WRTLauncher" -o tct-audio-html5-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-backgrounds-css3-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-backgrounds-css3-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-backgrounds-css3-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-backgrounds-css3-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-backgrounds-css3-tests" -f /usr/share/tct-backgrounds-css3-tests/tests.xml -o /tmp/tct-backgrounds-css3-tests.results.xml -A
-5. Click the "Run" button of the manual harness. A test widget is downloaded. You need to install the widget in WRT, and then load the widget to continue with the tests(for example, the widget UI will show the test results). You also need to fill the result in manual tests harness for result collection.
+
+2. Build ZIP package by running the following command:
+ ./pack.sh
+
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-backgrounds-css3-tests-<version>.zip -d /opt/usr/media/tct
+
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-backgrounds-css3-tests/inst.sh
+
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-backgrounds-css3-tests/tests.xml -e "WRTLauncher" -o tct-backgrounds-css3-tests.results.xml
----------------------------------------------
(11) webkit/mixed-border-styles-radius2.html
=> https://trac.webkit.org/browser/trunk/LayoutTests/platform/mac/fast/borders/mixed-border-styles-radius2-expected.png
-
-
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to yugang.fan@intel.com.
-
-
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
-2. To enable more auto cases.
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-batterystatus-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-batterystatus-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-batterystatus-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-batterystatus-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-batterystatus-w3c-tests" -f /usr/share/tct-batterystatus-w3c-tests/tests.xml -o /tmp/tct-batterystatus-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-None
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-batterystatus-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-batterystatus-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-batterystatus-w3c-tests/tests.xml -e "WRTLauncher" -o tct-batterystatus-w3c-tests.results.xml
----------------------------------------------
Copyright (c) 2012 Intel Corporation.
-Redistribution and use in source and binary forms, with or without modification,
+Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
-* Redistributions of works must retain the original copyright notice, this list
+* Redistributions of works must retain the original copyright notice, this list
of conditions and the following disclaimer.
-* Redistributions in binary form must reproduce the original copyright notice,
- this list of conditions and the following disclaimer in the documentation
+* Redistributions in binary form must reproduce the original copyright notice,
+ this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
-* Neither the name of Intel Corporation nor the names of its contributors
- may be used to endorse or promote products derived from this work without
+* Neither the name of Intel Corporation nor the names of its contributors
+ may be used to endorse or promote products derived from this work without
specific prior written permission.
-THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION BE LIABLE FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
-OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
-EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
+EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Authors:
Lei, ZhanX <zhanx.lei@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen Bluetooth API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/bluetooth.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Pre-condition
----------------------------------------------
"REMOTE_DEVICE_NAME" : The name of the device on which tct-bt-helper will be run.
"REMOTE_HEALTH_DEVICE_TYPE" : The type of health device 4100 is for oximeter or blood pressure monitor 4103.
-
tct-bt-helper MUST be installed on the remote device whose address is REMOTE_DEVICE_ADDRESS.
tct-bt-helper is included in the RPM package of this test. So, you MUST install the RPM package both on the test device and the remote device.
In addition, the bluetooth of the remote device MUST be turned on and discoverable from other devices.
When you run the manual tests, you MUST register a service to the remote device by pushing "Register service" button on tct-bt-helper.
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-bluetooth-tizen-tests RPM, you can directly go to step 3 on the test machine;
+ If you have got tct-bluetooth-tizen-tests ZIP, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-bluetooth-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-bluetooth-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-bluetooth-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-bluetooth-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-bluetooth-tizen-tests" -f device:/usr/share/tct-bluetooth-tizen-tests/tests.xml -o /tmp/tct-bluetooth-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-bluetooth-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-bluetooth-tizen-tests/tests.xml -e "WRTLauncher" -o tct-bluetooth-tizen-tests.results.xml
- ----------------------------------------------
+----------------------------------------------
License
----------------------------------------------
Copyright (c) 2013 Samsung Electronics Co., Ltd.
Tomasz Paciorek <t.paciorek@samsung.com>
Andrzej Krolikowski <a.krolikowsk@samsung.com>
+
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen Bookmark API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/bookmark.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
-
+
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-bookmark-tizen-tests RPM, you can directly go to step 3 on the test machine;
+ If you have got tct-bookmark-tizen-tests ZIP, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-bookmark-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-bookmark-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-bookmark-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-bookmark-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-bookmark-tizen-tests" -f device:/usr/share/tct-bookmark-tizen-tests/tests.xml -o /tmp/tct-bookmark-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-bookmark-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-bookmark-tizen-tests/tests.xml -e "WRTLauncher" -o tct-bookmark-tizen-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-browserstate-html5-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-browserstate-html5-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-browserstate-html5-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-browserstate-html5-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-browserstate-html5-tests" -f /usr/share/tct-browserstate-html5-tests/tests.xml -o /tmp/tct-browserstate-html5-tests.results.xml -A
-5. Click the "Run" button of the manual harness. A test widget is downloaded. You need to install the widget in WRT, and then load the widget to continue with the tests(for example, the widget UI will show the test results). You also need to fill the result in manual tests harness for result collection.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to zhiqiang.zhang@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-browserstate-html5-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-browserstate-html5-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To format existing test cases.
-2. To design tests to cover all specifications P1/P2/P3 testing.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-browserstate-html5-tests/tests.xml -e "WRTLauncher" -o tct-browserstate-html5-tests.results.xml
Li, Cici <cici.x.li@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen Calendar API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/calendar.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
-
+
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-calendar-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-calendar-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-calendar-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-calendar-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-calendar-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-calendar-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-calendar-tizen-tests" -f device:/usr/share/tct-calendar-tizen-tests/tests.xml -o /tmp/tct-calendar-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-calendar-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-calendar-tizen-tests/tests.xml -e "WRTLauncher" -o tct-calendar-tizen-tests.results.xml
Guan,JingX <jingx.guan@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen Callhistory API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/callhistory.html
+
----------------------------------------------
Test Environment
----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Pre-condition
----------------------------------------------
CallHistory_removeAll_with_errorCallback.html
CallHistory_removeAll_with_successCallback.html
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-callhistory-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-callhistory-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-callhistory-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-callhistory-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-callhistory-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-callhistory-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-callhistory-tizen-tests" -f device:/usr/share/tct-callhistory-tizen-tests/tests.xml -o /tmp/tct-callhistory-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-callhistory-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-callhistory-tizen-tests/tests.xml -e "WRTLauncher" -o tct-callhistory-tizen-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Pre-conditions
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-canvas-html5-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-canvas-html5-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-canvas-html5-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-canvas-html5-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-canvas-html5-tests" -f /usr/share/tct-canvas-html5-tests/tests.xml -o /tmp/tct-canvas-html5-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-1. Chromium browser is not enabled with H.264 or AAC codec because of license issue.
-2. Chromium browser reports an error "out of memory" when all the test cases are executed at the same time.
-
-Note: You can report the defects of this test suite to zhiqiang.zhang@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-canvas-html5-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-canvas-html5-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-canvas-html5-tests/tests.xml -e "WRTLauncher" -o tct-canvas-html5-tests.results.xml
Zhang, Ge <gex.zhang@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
1. Pre-install Testkit-Lite package on Host(ubuntu12.04 and ubuntu12.10).
sudo apt-get install python-pip
sudo pip install requests
- sudo dpkg -i testkit-lite-<version>.deb
+ sudo dpkg -i testkit-lite-<version>.deb
2. Push "httpserver" into test machine.
sdb root on
sdb push httpserver /usr/bin
3. Run the cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only got the source code and Testkit-Lite set up on your host.
- If you have got tct-capability-tests RPM packages on the test machine, you can directly go to step 3;
+ If you have got tct-capability-tests ZIP packages on the test machine, you can directly go to step 3;
if you have not installed Testkit-lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-capability-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-capability-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-capability-tests" -f device:"/usr/share/tct-capability-tests/tests.xml"
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-
-Note: If there is any defects in this test suite, please do not hesitate to contact us by the email gex.zhang@intel.com.
-
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-capability-tests-<version>.zip -d /opt/usr/media/tct
-----------------------------------------------
-Todo
-----------------------------------------------
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-capability-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-capability-tests/tests.xml -e "WRTLauncher" -o tct-capability-tests.results.xml
This test suite is for testing CSS3 Colors specification:
http://www.w3.org/TR/2011/REC-css3-color-20110607
+
----------------------------------------------
Test Environment
----------------------------------------------
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-colors-css3-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-colors-css3-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-colors-css3-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-colors-css3-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-colors-css3-tests" -f /usr/share/tct-colors-css3-tests/tests.xml -o /tmp/tct-colors-css3-tests.results.xml -A
-5. Click the "Run" button of the manual harness. A test widget is downloaded. You need to install the widget in WRT, and then load the widget to continue with the tests(for example, the widget UI will show the test results). You also need to fill the result in manual tests harness for result collection.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
----------------------------------------------
-Note: You can report the defects of this test suite to yugang.fan@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-colors-css3-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-colors-css3-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
-2. To enable more auto cases.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-colors-css3-tests/tests.xml -e "WRTLauncher" -o tct-colors-css3-tests.results.xml
Tomasz Paciorek <t.paciorek@samsung.com>
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen Contact API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/contact.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-contact-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-contact-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-contact-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-contact-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-contact-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-contact-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-contact-tizen-tests" -f device:/usr/share/tct-contact-tizen-tests/tests.xml -o /tmp/tct-contact-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-contact-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-contact-tizen-tests/tests.xml -e "WRTLauncher" -o tct-contact-tizen-tests.results.xml
----------------------------------------------
Copyright (c) 2012 Intel Corporation.
-Redistribution and use in source and binary forms, with or without modification,
+Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
-* Redistributions of works must retain the original copyright notice, this list
+* Redistributions of works must retain the original copyright notice, this list
of conditions and the following disclaimer.
-* Redistributions in binary form must reproduce the original copyright notice,
- this list of conditions and the following disclaimer in the documentation
+* Redistributions in binary form must reproduce the original copyright notice,
+ this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
-* Neither the name of Intel Corporation nor the names of its contributors
- may be used to endorse or promote products derived from this work without
+* Neither the name of Intel Corporation nor the names of its contributors
+ may be used to endorse or promote products derived from this work without
specific prior written permission.
-THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION BE LIABLE FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
-OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
-EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
+EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Authors:
Guan,JingX <jingx.guan@intel.com>
Krzysztof Lachacz <k.lachacz@samsung.com>
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen Content API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/content.html
+
----------------------------------------------
Test Environment
----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-content-tizen-tests RPM, you can directly go to step 3 on the test machine;
+ If you have got tct-content-tizen-tests ZIP, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-content-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-content-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-content-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-content-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-content-tizen-tests" -f device:/usr/share/tct-content-tizen-tests/tests.xml -o /tmp/tct-content-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-content-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-content-tizen-tests/tests.xml -e "WRTLauncher" -o tct-content-tizen-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Pre-conditions
----------------------------------------------
Build and Run
----------------------------------------------
Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-cors-w3c-tests RPM packagess, you can directly go to step 3 on the test machine;
+ If you have obtained tct-cors-w3c-tests ZIP packagess, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-cors-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-cors-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-cors-w3c-tests" -f /usr/share/tct-cors-w3c-tests/tests.xml -o /tmp/tct-cors-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-1. Some test cases depend on operator servers which have NOT been set up.
-
-Note: You can report the defects of this test suite to <zhiqiang.zhang@intel.com>.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-cors-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-cors-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To set up operator servers for CORS testing.
-2. To add test cases for CORS module.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-cors-w3c-tests/tests.xml -e "WRTLauncher" -o tct-cors-w3c-tests.results.xml
Hao, Yunfei <yunfeix.hao@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
find /opt/home/app/opt/tct-csp-w3c-tests/csp -name "*.php" | xargs -I {} chmod a+x {}
3. Run the cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-csp-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-csp-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-csp-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-csp-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-csp-w3c-tests" -f device:"/usr/share/tct-csp-w3c-tests/tests.xml"
-5. Click the "Run" button of the manual harness. A test widget is downloaded. You need to install the widget in WRT, and then load the widget to continue with the tests(for example, the widget UI will show the test results). You also need to fill the result in manual tests harness for result collection.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: If there is any defects in this test suite, please do not hesitate to contact us by the email yunfeix.hao@intel.com.
-
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-csp-w3c-tests-<version>.zip -d /opt/usr/media/tct
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
-2. To enable more auto cases.
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-csp-w3c-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-csp-w3c-tests/tests.xml -e "WRTLauncher" -o tct-csp-w3c-tests.results.xml
Andrzej Krolikowski <a.krolikowsk@samsung.com>
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen DataControl API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/datacontrol.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
3. Pre-install DictionaryDataControlProvider native application.
4. Pre-run DictionaryDataControlProvider native application.
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-datacontrol-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-datacontrol-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-datacontrol-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-datacontrol-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-datacontrol-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-datacontrol-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-datacontrol-tizen-tests" -f device:/usr/share/tct-datacontrol-tizen-tests/tests.xml -o /tmp/tct-datacontrol-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-datacontrol-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-datacontrol-tizen-tests/tests.xml -e "WRTLauncher" -o tct-datacontrol-tizen-tests.results.xml
Authors:
Lukasz Bardeli <l.bardeli@samsung.com>
+
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen DataSynchronization API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/datasync.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-datasync-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-datasync-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-datasync-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-datasync-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-datasync-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-datasync-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-datasync-tizen-tests" -f device:/usr/share/tct-datasync-tizen-tests/tests.xml -o /tmp/tct-datasync-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-datasync-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-datasync-tizen-tests/tests.xml -e "WRTLauncher" -o tct-datasync-tizen-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-deviceorientation-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-deviceorientation-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-deviceorientation-w3c-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-deviceorientation-w3c-tests-<version>-<release>.<arch>.rpm --nodeps
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-deviceorientation-w3c-tests" -f /usr/share/tct-deviceorientation-w3c-tests/tests.xml -o /tmp/tct-deviceorientation-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-deviceorientation-w3c-tests-<version>.zip -d /opt/usr/media/tct
-----------------------------------------------
-Known Issues
-----------------------------------------------
-1. Acceleration attribute is not supported.
-Note: You can report the defects of these tests to <zhiqiang.zhang@intel.com>.
-
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-deviceorientation-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. Add test cases for device orientation event module.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-deviceorientation-w3c-tests/tests.xml -e "WRTLauncher" -o tct-deviceorientation-w3c-tests.results.xml
1. Pre-install Testkit-Lite package.
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-dnd-html5-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-dnd-html5-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-dnd-html5-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-dnd-html5-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-dnd-html5-tests" -f /usr/share/tct-dnd-html5-tests/tests.xml -o /tmp/tct-dnd-html5-tests.results.xml -A
-5. Click the "Run" button of the manual harness. A test widget is downloaded. You need to install the widget in WRT, and then load the widget to continue with the tests(for example, the widget UI will show the test results). You also need to fill the result in manual tests harness for result collection.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to zhiqiang.zhang@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-dnd-html5-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-dnd-html5-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-To design more tests to cover all web APIs in specs.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-dnd-html5-tests/tests.xml -e "WRTLauncher" -o tct-dnd-html5-tests.results.xml
Authors:
leizhan<zhanx.lei@intel.com>
+
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen Download API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/download.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
-
+
+
----------------------------------------------
Pre-condition
----------------------------------------------
A network connection capable of accessing the Internet MUST be established
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-download-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-download-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-download-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-download-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-download-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-download-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-download-tizen-tests" -f device:/usr/share/tct-download-tizen-tests/tests.xml -o /tmp/tct-download-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-download-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-download-tizen-tests/tests.xml -e "WRTLauncher" -o tct-download-tizen-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Pre-conditions
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-extra-html5-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-extra-html5-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-extra-html5-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-extra-html5-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-extra-html5-tests" -f /usr/share/tct-extra-html5-tests/tests.xml -o /tmp/tct-extra-html5-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to <zhiqiang.zhang@intel.com>
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-extra-html5-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-extra-html5-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-extra-html5-tests/tests.xml -e "WRTLauncher" -o tct-extra-html5-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Pre-conditions
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-fileapi-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-fileapi-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-fileapi-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-fileapi-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "chromium-browser --allow-file-access-from-files '/opt/testkit/web/index.html'" -f tests.xml -o result.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to Fan Weiwei <weiwix.fan@intel.com>.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-fileapi-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-fileapi-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To format existing test cases.
-2. To design tests to cover all specications P1, P2 and P3 testing.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-fileapi-w3c-tests/tests.xml -e "WRTLauncher" -o tct-fileapi-w3c-tests.results.xml
Li, kaiyu <kaiyux.li@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-filesystem-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-filesystem-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-filesystem-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-filesystem-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-filesystem-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-filesystem-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-filesystem-tizen-tests" -f device:/usr/share/tct-filesystem-tizen-tests/tests.xml -o /tmp/tct-filesystem-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-filesystem-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-filesystem-tizen-tests/tests.xml -e "WRTLauncher" -o tct-filesystem-tizen-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-filesystemapi-w3c-tests RPM package, you can directly go to step 3 on the test machine;
+ If you have obtained tct-filesystemapi-w3c-tests ZIP package, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-filesystemapi-w3c-tests
-2. Build RPM package by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-filesystemapi-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-filesystemapi-w3c-tests" -f /usr/share/tct-filesystemapi-w3c-tests/tests.xml -o /tmp/tct-filesystemapi-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-None
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-filesystemapi-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-filesystemapi-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-filesystemapi-w3c-tests/tests.xml -e "WRTLauncher" -o tct-filesystemapi-w3c-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-filewriterapi-w3c-tests RPM package, you can directly go to step 3 on the test machine;
+ If you have obtained tct-filewriterapi-w3c-tests ZIP package, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-filewriterapi-w3c-tests
-2. Build RPM package by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-filewriterapi-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-filewriterapi-w3c-tests" -f /usr/share/tct-filewriterapi-w3c-tests/tests.xml -o /tmp/tct-filewriterapi-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-None
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-filewriterapi-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-filewriterapi-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-filewriterapi-w3c-tests/tests.xml -e "WRTLauncher" -o tct-filewriterapi-w3c-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-flexiblebox-css3-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-flexiblebox-css3-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-flexiblebox-css3-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-flexiblebox-css3-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-flexiblebox-css3-tests" -f /usr/share/tct-flexiblebox-css3-tests/tests.xml -o /tmp/tct-flexiblebox-css3-tests.results.xml -A
-5. Click the "Run" button of the manual harness. A test widget is downloaded. You need to install the widget in WRT, and then load the widget to continue with the tests(for example, the widget UI will show the test results). You also need to fill the result in manual tests harness for result collection.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to yugang.fan@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-flexiblebox-css3-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-flexiblebox-css3-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
-2. To enable more auto cases.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-flexiblebox-css3-tests/tests.xml -e "WRTLauncher" -o tct-flexiblebox-css3-tests.results.xml
1. Pre-install Testkit-Lite package.
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
-----------------------------------------------
-Pre-conditions
-----------------------------------------------
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-fonts-css3-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-fonts-css3-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-fonts-css3-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-fonts-css3-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-fonts-css3-tests" -f /usr/share/tct-fonts-css3-tests/tests.xml -o /tmp/tct-fonts-css3-tests.results.xml -A
-5. Click the "Run" button of the manual harness. A test widget is downloaded. You need to install the widget in WRT, and then load the widget to continue with the tests(for example, the widget UI will show the test results). You also need to fill the result in manual tests harness for result collection.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to yugang.fan@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-fonts-css3-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-fonts-css3-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-fonts-css3-tests/tests.xml -e "WRTLauncher" -o tct-fonts-css3-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-forms-html5-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-forms-html5-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-forms-html5-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-forms-html5-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-forms-html5-tests" -f /usr/share/tct-forms-html5-tests/tests.xml -o /tmp/tct-forms-html5-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-1. Chromium browser is not enabled with H.264 or AAC codec because of license issue.
-2. Chromium browser reports an error "out of memory" when all the test cases are executed at the same time.
-
-Note: You can report the defects of this test suite to zhiqiang.zhang@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-forms-html5-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-forms-html5-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-forms-html5-tests/tests.xml -e "WRTLauncher" -o tct-forms-html5-tests.results.xml
2. Run the cases in the package as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-fullscreen-nonw3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-fullscreen-nonw3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-fullscreen-nonw3c-tests
-2. Build RPM package by running the following command:
- pack.sh -t all
-3. Install RPM on the machine as "root" user by running the following command:
- rpm -ivh tct-fullscreen-nonw3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-fullscreen-nonw3c-tests" -f /usr/share/tct-fullscreen-nonw3c-tests/tests.xml -o /tmp/tct-fullscreen-nonw3c-tests.results.xml -A
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Chromium browser does not support the ViewPort feature.
-
-Note: You can report the defects of this test suite to yugang.fan@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-fullscreen-nonw3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-fullscreen-nonw3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. Fix bugs.
-2. Enable more auto cases.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-fullscreen-nonw3c-tests/tests.xml -e "WRTLauncher" -o tct-fullscreen-nonw3c-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Pre-conditions
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-geoallow-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-geoallow-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-geoallow-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-geoallow-w3c-tests-xxx.noarch.rpm --nodeps
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Some special tests
-----------------------------------------------
-For the geoallow auto TCs testing on SLP:
-1. When a confirm dialog is popped up, please select "Don't ask again" and click "YES" button
- to allow the application requesting user current location.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-geoallow-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-geoallow-w3c-tests/inst.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-None
-
-
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-geoallow-w3c-tests/tests.xml -e "WRTLauncher" -o tct-geoallow-w3c-tests.results.xml
+----------------------------------------------
+License
+----------------------------------------------
+Copyright (c) 2012 Intel Corporation.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+* Redistributions of works must retain the original copyright notice, this list
+ of conditions and the following disclaimer.
+* Redistributions in binary form must reproduce the original copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+* Neither the name of Intel Corporation nor the names of its contributors
+ may be used to endorse or promote products derived from this work without
+ specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
+EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+Authors:
+ Lin, Wanming <wanmingx.lin@intel.com>
+
+
+
----------------------------------------------
Introduction
---------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and testkit-Lite has been set up on your test machine.
- If you have obtained tct-geodeny-w3c-tests RPM package, you can directly go to step 3 on the test machine;
+ If you have obtained tct-geodeny-w3c-tests ZIP package, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-geodeny-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-geodeny-w3c-tests-xxx.noarch.rpm --nodeps
+
+2. Build ZIP package by running the following command:
+ ./pack.sh
+
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-geodeny-w3c-tests-<version>.zip -d /opt/usr/media/tct
+
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-geodeny-w3c-tests/inst.sh
+
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-geodeny-w3c-tests/tests.xml -e "WRTLauncher" -o tct-geodeny-w3c-tests.results.xml
For the geodeny auto TCs' testing on SLP:
1. Please disenable GPS or disconnect to an available network;
2. When a confirm dialog is popped up, please select "Don't ask again" and click "No" button,
to deny the application requests user current location.
-
-----------------------------------------------
-Known Issues
-----------------------------------------------
-None
-
-----------------------------------------------
-Todo
-----------------------------------------------
-None
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-gumallow-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-gumallow-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-gumallow-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-gumallow-w3c-tests-1.1.2-1.noarch.rpm --nodeps
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-gumallow-w3c-tests" -f /usr/share/tct-gumallow-w3c-tests/tests.xml -o /tmp/tct-gumallow-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Some special tests
-----------------------------------------------
-For the gumallow auto TCs testing on SLP:
-When a confirm dialog is popped up, please select "Don't ask again" and click "YES" button,
-to allow the application requesting user media.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-gumallow-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-gumallow-w3c-tests/inst.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-gumallow-w3c-tests/tests.xml -e "WRTLauncher" -o tct-gumallow-w3c-tests.results.xml
----------------------------------------------
-Todo
+Some special tests
----------------------------------------------
-None
+For the gumallow auto TCs testing on SLP:
+When a confirm dialog is popped up, please select "Don't ask again" and click "YES" button,
+to allow the application requesting user media.
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
Steps:
1. Prepare for building by running the following command:
cd tct-indexeddb-w3c-tests
-2. Build RPM package by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-indexeddb-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-indexeddb-w3c-tests" -f /usr/share/tct-indexeddb-w3c-tests/tests.xml -o /tmp/tct-indexeddb-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to weiwix.fan@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-indexeddb-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-indexeddb-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
-2. To enable more auto cases.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-indexeddb-w3c-tests/tests.xml -e "WRTLauncher" -o tct-indexeddb-w3c-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-jsenhance-html5-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-jsenhance-html5-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-jsenhance-html5-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-jsenhance-html5-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-jsenhance-html5-tests" -f /usr/share/tct-jsenhance-html5-tests/tests.xml -o /tmp/tct-jsenhance-html5-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-1. Chromium browser is not enabled with H.264 or AAC codec because of license issue.
-2. Chromium browser reports an error "out of memory" when all the test cases are executed at the same time.
-
-Note: You can report the defects of this test suite to zhiqiang.zhang@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-jsenhance-html5-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-jsenhance-html5-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-jsenhance-html5-tests/tests.xml -e "WRTLauncher" -o tct-jsenhance-html5-tests.results.xml
Lin, Wanming <wanmingx.lin@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for W3C manual tests.
+
----------------------------------------------
Test Environment
----------------------------------------------
find /opt/home/app/opt/tct-manual-w3c-tests/csp -name "*.php" | xargs -I {} chmod a+x {}
4. Run the cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-manual-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-manual-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-manual-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-manual-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-manual-w3c-tests" -f device:"/usr/share/tct-manual-w3c-tests/tests.xml"
+
+2. Build ZIP package by running the following command:
+ ./pack.sh
+
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-manual-w3c-tests-<version>.zip -d /opt/usr/media/tct
+
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-manual-w3c-tests/inst.sh
+
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-manual-w3c-tests/tests.xml -e "WRTLauncher" -o tct-manual-w3c-tests.results.xml
For test TCs in widgetinterface(tct-manual-w3c-tests/widgetinterface), widgetpackaging(tct-manual-w3c-tests/widgetpackaging) and widgetpolicy(tct-manual-w3c-tests/widgetpolicy) need to do following extra steps:
wrt-launcher -s <wgt.id>
4. Uninstall WGT from the test machine as "root" user by running the following command:
wrt-installer -un <wgt.id>
-
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: If there is any defects in this test suite, please do not hesitate to contact us by the email wanmingx.lin@intel.com.
-
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
-2. To enable more auto cases.
-
2. Make sure the device you tested on has image, audio, video file.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-mediacapture-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-mediacapture-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-mediacapture-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-mediacapture-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-mediacapture-w3c-tests" -f /usr/share/tct-mediacapture-w3c-tests/tests.xml -o /tmp/tct-mediacapture-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-None
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-mediacapture-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-mediacapture-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-mediacapture-w3c-tests/tests.xml -e "WRTLauncher" -o tct-mediacapture-w3c-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-mediaqueries-css3-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-mediaqueries-css3-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-mediaqueries-css3-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-mediaqueries-css3-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-mediaqueries-css3-tests" -f /usr/share/tct-mediaqueries-css3-tests/tests.xml -o /tmp/tct-mediaqueries-css3-tests.results.xml -A
-5. Click the "Run" button of the manual harness. A test widget is downloaded. You need to install the widget in WRT, and then load the widget to continue with the tests(for example, the widget UI will show the test results). You also need to fill the result in manual tests harness for result collection.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to zhiqiang.zhang@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-mediaqueries-css3-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-mediaqueries-css3-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To format existing test cases.
-2. To design tests to cover all specifications P1/P2/P3 testing.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-mediaqueries-css3-tests/tests.xml -e "WRTLauncher" -o tct-mediaqueries-css3-tests.results.xml
Andrzej Krolikowski <a.krolikowsk@samsung.com>
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen MessagePort API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/messageport.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-messageport-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-messageport-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-messageport-tizen-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-messageport-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-messageport-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-messageport-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-messageport-tizen-tests" -f device:/usr/share/tct-messageport-tizen-tests/tests.xml -o /tmp/tct-messageport-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-messageport-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-messageport-tizen-tests/tests.xml -e "WRTLauncher" -o tct-messageport-tizen-tests.results.xml
Authors:
Zou, Zoe <yananx.xu@intel.com>
+
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen Messaging API, which covers the following specifications (only e-mail part):
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/messaging.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Pre-condition
----------------------------------------------
5. There MUST be exactly one email service configured on the device.
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and testkit-lite has been setup on your test machine
- if you have got tct-messaging-email-tizen-tests RPM packages, you can directly go to step 3 on testing machine;
+ if you have got tct-messaging-email-tizen-tests ZIP packages, you can directly go to step 3 on testing machine;
if you have not installed the testkit-lite, you need to install the latest version)
Steps:
1. Prepare for building by running the following command:
cd tct-messaging-email-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-messaging-email-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-messaging-email-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-messaging-email-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-messaging-email-tizen-tests" -f device:/usr/share/tct-messaging-email-tizen-tests/tests.xml -o /tmp/tct-messaging-email-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-messaging-email-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-messaging-email-tizen-tests/tests.xml -e "WRTLauncher" -o tct-messaging-email-tizen-tests.results.xml
Authors:
Zou, Zoe <yananx.xu@intel.com>
+
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen Messaging API, which covers the following specifications (only MMS part):
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/messaging.html
+
----------------------------------------------
Test Environment
----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Pre-condition
----------------------------------------------
(different from the device under test,
different from TEST_SMS_RECIPIENT and without country calling code)
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and testkit-lite has been setup on your test machine
- if you have got tct-messaging-mms-tizen-tests RPM packages, you can directly go to step 3 on testing machine;
+ if you have got tct-messaging-mms-tizen-tests ZIP packages, you can directly go to step 3 on testing machine;
if you have not installed the testkit-lite, you need to install the latest version)
Steps:
1. Prepare for building by running the following command:
cd tct-messaging-mms-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-messaging-mms-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-messaging-mms-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-messaging-mms-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-messaging-mms-tizen-tests" -f device:/usr/share/tct-messaging-mms-tizen-tests/tests.xml -o /tmp/tct-messaging-mms-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-messaging-mms-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-messaging-mms-tizen-tests/tests.xml -e "WRTLauncher" -o tct-messaging-mms-tizen-tests.results.xml
Authors:
Zou, Zoe <yananx.xu@intel.com>
+
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen Messaging API, which covers the following specifications (only SMS part):
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/messaging.html
+
----------------------------------------------
Test Environment
----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Pre-condition
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and testkit-lite has been setup on your test machine
- if you have got tct-messaging-sms-tizen-tests RPM packages, you can directly go to step 3 on testing machine;
+ if you have got tct-messaging-sms-tizen-tests ZIP packages, you can directly go to step 3 on testing machine;
if you have not installed the testkit-lite, you need to install the latest version)
Steps:
1. Prepare for building by running the following command:
cd tct-messaging-sms-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-messaging-sms-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-messaging-sms-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-messaging-sms-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-messaging-sms-tizen-tests" -f device:/usr/share/tct-messaging-sms-tizen-tests/tests.xml -o /tmp/tct-messaging-sms-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-messaging-sms-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-messaging-sms-tizen-tests/tests.xml -e "WRTLauncher" -o tct-messaging-sms-tizen-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-multicolumn-css3-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-multicolumn-css3-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-multicolumn-css3-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-multicolumn-css3-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-multicolumn-css3-tests" -f /usr/share/tct-multicolumn-css3-tests/tests.xml -o /tmp/tct-multicolumn-css3-tests.results.xml -A
-5. Click the "Run" button of the manual harness. A test widget is downloaded. You need to install the widget in WRT, and then load the widget to continue with the tests(for example, the widget UI will show the test results). You also need to fill the result in manual tests harness for result collection.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to yugang.fan@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-multicolumn-css3-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-multicolumn-css3-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
-2. To enable more auto cases.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-multicolumn-css3-tests/tests.xml -e "WRTLauncher" -o tct-multicolumn-css3-tests.results.xml
----------------------------------------------
Copyright (c) 2012 Intel Corporation.
-Redistribution and use in source and binary forms, with or without modification,
+Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
-* Redistributions of works must retain the original copyright notice, this list
+* Redistributions of works must retain the original copyright notice, this list
of conditions and the following disclaimer.
-* Redistributions in binary form must reproduce the original copyright notice,
- this list of conditions and the following disclaimer in the documentation
+* Redistributions in binary form must reproduce the original copyright notice,
+ this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
-* Neither the name of Intel Corporation nor the names of its contributors
- may be used to endorse or promote products derived from this work without
+* Neither the name of Intel Corporation nor the names of its contributors
+ may be used to endorse or promote products derived from this work without
specific prior written permission.
-THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION BE LIABLE FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
-OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
-EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
+EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Authors:
- Cao, Jenny <jenny.q.cao@intel.com>
+ Cao, Jenny <jenny.q.cao@intel.com>
----------------------------------------------
This test suite is for testing Tizen namespace.
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-namespace-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-namespace-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-namespace-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-namespace-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-namespace-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-namespace-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-namespace-tizen-tests" -f device:/usr/share/tct-namespace-tizen-tests/tests.xml -o /tmp/tct-namespace-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-namespace-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-namespace-tizen-tests/tests.xml -e "WRTLauncher" -o tct-namespace-tizen-tests.results.xml
Han Ruijing <ruijingx.a.han@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Pre-install Testkit-Lite package on Host(ubuntu12.04 and ubuntu12.10).
sudo apt-get install python-pip
sudo pip install requests
3. Run the cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only got the source code and Testkit-Lite set up on your host.
-If you have got tct-navigationtiming-w3c-tests RPM packages on the test machine, you can directly go to step 3;
+If you have got tct-navigationtiming-w3c-tests ZIP packages on the test machine, you can directly go to step 3;
if you have not installed Testkit-lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-navigationtiming-w3c-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-navigationtiming-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-navigationtiming-w3c-tests" -f device:"/usr/share/tct-navigationtiming-w3c-tests/tests.xml"
-5. Please make sure the network is connected when testing Navigation Timing.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-
-Note: If there is any defects in this test suite, please do not hesitate to contact us by the email ruijingx.a.han@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-navigationtiming-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-navigationtiming-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-navigationtiming-w3c-tests/tests.xml -e "WRTLauncher" -o tct-navigationtiming-w3c-tests.results.xml
2. Make sure the the device can be online and offline.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-netinfo-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-netinfo-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-netinfo-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-netinfo-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-netinfo-w3c-tests" -f /usr/share/tct-netinfo-w3c-tests/tests.xml -o /tmp/tct-netinfo-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-None
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-netinfo-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-netinfo-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-netinfo-w3c-tests/tests.xml -e "WRTLauncher" -o tct-netinfo-w3c-tests.results.xml
Krzysztof Lachacz <k.lachacz@samsung.com>
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen NetworkBearerSelection API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/networkbearerselection.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Pre-conditions
----------------------------------------------
NetworkBearerSelection tests requires cellular data service enabled.
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-networkbearerselection-tizen-tests RPM, you can directly go to step 3 on the test machine;
+ If you have got tct-networkbearerselection-tizen-tests ZIP, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-networkbearerselection-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-networkbearerselection-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-networkbearerselection-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-networkbearerselection-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-networkbearerselection-tizen-tests" -f device:/usr/share/tct-networkbearerselection-tizen-tests/tests.xml -o /tmp/tct-networkbearerselection-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-networkbearerselection-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-networkbearerselection-tizen-tests/tests.xml -e "WRTLauncher" -o tct-networkbearerselection-tizen-tests.results.xml
----------------------------------------------
Copyright (c) 2012 Intel Corporation.
-Redistribution and use in source and binary forms, with or without modification,
+Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
-* Redistributions of works must retain the original copyright notice, this list
+* Redistributions of works must retain the original copyright notice, this list
of conditions and the following disclaimer.
-* Redistributions in binary form must reproduce the original copyright notice,
- this list of conditions and the following disclaimer in the documentation
+* Redistributions in binary form must reproduce the original copyright notice,
+ this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
-* Neither the name of Intel Corporation nor the names of its contributors
- may be used to endorse or promote products derived from this work without
+* Neither the name of Intel Corporation nor the names of its contributors
+ may be used to endorse or promote products derived from this work without
specific prior written permission.
-THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION BE LIABLE FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
-OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
-EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
+EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Authors:
Han, GuangX <guangx.han@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Ensure that NFC is integrated.
2. Testkit-stub must be installed on target device.
3. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Pre-Conditions
----------------------------------------------
- touch the device with different NFC enabled device (NFCAdapter_setPeerListener*, NFCPeer* tests)
- touch the device with different NFC enabled device and send NFC data from it
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-nfc-tizen-tests RPM, you can directly go to step 3 on the test machine;
+ If you have got tct-nfc-tizen-tests ZIP, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-nfc-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-nfc-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-nfc-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-nfc-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-nfc-tizen-tests" -f device:/usr/share/tct-nfc-tizen-tests/tests.xml -o /tmp/tct-nfc-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-nfc-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-nfc-tizen-tests/tests.xml -e "WRTLauncher" -o tct-nfc-tizen-tests.results.xml
Authors:
leizhan<zhanx.lei@intel.com>
+
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen Notification API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/notification.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
-
+
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-notification-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-notification-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-notification-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-notification-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-notification-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-notification-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-notification-tizen-tests" -f device:/usr/share/tct-notification-tizen-tests/tests.xml -o /tmp/tct-notification-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-notification-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-notification-tizen-tests/tests.xml -e "WRTLauncher" -o tct-notification-tizen-tests.results.xml
2. Make sure the the device can be online and offline.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-notification-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-notification-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-notification-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-notification-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-notification-w3c-tests" -f /usr/share/tct-notification-w3c-tests/tests.xml -o /tmp/tct-notification-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-None
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-notification-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-notification-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-notification-w3c-tests/tests.xml -e "WRTLauncher" -o tct-notification-w3c-tests.results.xml
Andrzej Krolikowski <a.krolikowsk@samsung.com>
+
----------------------------------------------
Introduction
----------------------------------------------
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-package-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-package-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-package-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-package-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-package-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-package-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-package-tizen-tests" -f device:/usr/share/tct-package-tizen-tests/tests.xml -o /tmp/tct-package-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-package-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-package-tizen-tests/tests.xml -e "WRTLauncher" -o tct-package-tizen-tests.results.xml
Zhang, Ge <gex.zhang@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Pre-install Testkit-Lite package on Host(ubuntu12.04 and ubuntu12.10).
sudo apt-get install python-pip
sudo pip install requests
3. Run the cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only got the source code and Testkit-Lite set up on your test machine.
- If you have obtained tct-pagevisibility-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-pagevisibility-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-pagevisibility-w3c-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-pagevisibility-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-pagevisibility-w3c-tests" -f device:"/usr/share/tct-pagevisibility-w3c-tests/tests.xml"
-5. Please make sure the network is connected when testing Navigation Timing.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-
-Note: If there is any defects in this test suite, please do not hesitate to contact us by the email gex.zhang@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-pagevisibility-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-pagevisibility-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-pagevisibility-w3c-tests/tests.xml -e "WRTLauncher" -o tct-pagevisibility-w3c-tests.results.xml
leizhan<zhanx.lei@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen Power API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/power.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Pre-condition
----------------------------------------------
2. Set Backlight time to 15 seconds
'Settings' -> 'Display' -> 'Backlight time' -> choose 15 seconds
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-power-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-power-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-power-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-power-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-power-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-power-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-power-tizen-tests" -f device:/usr/share/tct-power-tizen-tests/tests.xml -o /tmp/tct-power-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-power-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-power-tizen-tests/tests.xml -e "WRTLauncher" -o tct-power-tizen-tests.results.xml
See the License for the specific language governing permissions and
limitations under the License.
-
-
Authors:
Piotr Szydelko <p.szydelko@samsung.com>
Tomasz Paciorek <t.paciorek@samsung.com>
Andrzej Krolikowski <a.krolikowsk@samsung.com>
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing privilege levels.
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-privilege-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-privilege-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-privilege-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-privilege-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-privilege-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-privilege-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-privilege-tizen-tests" -f device:/usr/share/tct-privilege-tizen-tests/tests.xml -o /tmp/tct-privilege-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-privilege-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-privilege-tizen-tests/tests.xml -e "WRTLauncher" -o tct-privilege-tizen-tests.results.xml
Andrzej Krolikowski <a.krolikowsk@samsung.com>
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen Push API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/push.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Pre-condition
----------------------------------------------
A network connection capable of accessing the Internet MUST be established
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-push-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-push-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-push-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-push-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-push-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-push-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-push-tizen-tests" -f device:/usr/share/tct-push-tizen-tests/tests.xml -o /tmp/tct-push-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-push-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-push-tizen-tests/tests.xml -e "WRTLauncher" -o tct-push-tizen-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Pre-conditions
----------------------------------------------
Note: Chromium does not support loading local files from local browser by default. If you want to load local files, you must add boot argument like 'chromium-browser --allow-file-access-from-files'.
For Test case:
- sandbox_002.htm
-
+ sandbox_002.htm
+
Test steps:
1. Install Apache server:
open terminal and type in this command: sudo apt-get install apache2;
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-sandbox-html5-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-sandbox-html5-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-sandbox-html5-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-sandbox-html5-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-sandbox-html5-tests" -f /usr/share/tct-sandbox-html5-tests/tests.xml -o /tmp/tct-sandbox-html5-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-1. Chromium browser is not enabled with H.264 or AAC codec because of license issue.
-
-Note: You can report the defects of this test suite to qingx.ge@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-sandbox-html5-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-sandbox-html5-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-sandbox-html5-tests/tests.xml -e "WRTLauncher" -o tct-sandbox-html5-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-screenorientation-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-screenorientation-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-screenorientation-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-screenorientation-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-screenorientation-w3c-tests" -f /usr/share/tct-screenorientation-w3c-tests/tests.xml -o /tmp/tct-screenorientation-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to zhiqiang.zhang@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-screenorientation-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-screenorientation-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To format existing test cases.
-2. To design tests to cover all specifications P1/P2/P3 testing.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-screenorientation-w3c-tests/tests.xml -e "WRTLauncher" -o tct-screenorientation-w3c-tests.results.xml
Andrzej Krolikowski <a.krolikowsk@samsung.com>
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen SecureElement API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/se.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-secureelement-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-secureelement-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-secureelement-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-secureelement-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-secureelement-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-secureelement-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-secureelement-tizen-tests" -f device:/usr/share/tct-secureelement-tizen-tests/tests.xml -o /tmp/tct-secureelement-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-secureelement-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-secureelement-tizen-tests/tests.xml -e "WRTLauncher" -o tct-secureelement-tizen-tests.results.xml
Leee <leee.lee@samsung.com>
+
----------------------------------------------
Introduction
----------------------------------------------
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Pre-install Testkit-Lite packages.
2. Run the cases in the package as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-security-tcs-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-security-tcs-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-security-tcs-tests
-2. Build RPM package by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-security-tcs-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-security-tcs-tests" -f /usr/share/tct-security-tcs-tests/tests.xml -o /tmp/tct-security-tcs-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-security-tcs-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-security-tcs-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-security-tcs-tests/tests.xml -e "WRTLauncher" -o tct-security-tcs-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-selectorslevel1-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-selectorslevel1-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-selectorslevel1-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-selectorslevel1-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-selectorslevel1-w3c-tests" -f /usr/share/tct-selectorslevel1-w3c-tests/tests.xml -o /tmp/tct-selectorslevel1-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-1. Chromium browser is not enabled with H.264 or AAC codec because of license issue.
-2. Chromium browser reports an error "out of memory" when all the test cases are executed at the same time.
-
-Note: You can report the defects of this test suite to zhiqiang.zhang@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-selectorslevel1-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-selectorslevel1-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-selectorslevel1-w3c-tests/tests.xml -e "WRTLauncher" -o tct-selectorslevel1-w3c-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-selectorslevel2-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-selectorslevel2-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-selectorslevel2-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-selectorslevel2-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-selectorslevel2-w3c-tests" -f /usr/share/tct-selectorslevel2-w3c-tests/tests.xml -o /tmp/tct-selectorslevel2-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-1. Chromium browser is not enabled with H.264 or AAC codec because of license issue.
-2. Chromium browser reports an error "out of memory" when all the test cases are executed at the same time.
-
-Note: You can report the defects of this test suite to zhiqiang.zhang@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-selectorslevel2-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-selectorslevel2-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-selectorslevel2-w3c-tests/tests.xml -e "WRTLauncher" -o tct-selectorslevel2-w3c-tests.results.xml
3. Chromium does not support loading local files from local browser by default. If you want to load local files, you must add boot argument like 'chromium-browser --allow-file-access-from-files'.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
----------------------------------------------
Pre-conditions
----------------------------------------------
6. Restart Apache:
open terminal and type in this command: sudo /etc/init.d/apache2 restart;
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-sessionhistory-html5-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-sessionhistory-html5-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-sessionhistory-html5-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-sessionhistory-html5-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-sessionhistory-html5-tests" -f /usr/share/tct-sessionhistory-html5-tests/tests.xml -o /tmp/tct-sessionhistory-html5-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-1. Chromium browser is not enabled with H.264 or AAC codec because of license issue.
-
-Note: You can report the defects of this test suite to qingx.ge@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-sessionhistory-html5-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-sessionhistory-html5-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-sessionhistory-html5-tests/tests.xml -e "WRTLauncher" -o tct-sessionhistory-html5-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Pre-conditions
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-sse-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-sse-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-sse-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-sse-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-sse-w3c-tests" -f /usr/share/tct-sse-w3c-tests/tests.xml -o /tmp/tct-sse-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-1. Some test cases depend on operator servers which have NOT been set up.
-
-Note: You can report the defects of this test suite to <zhiqiang.zhang@intel.com>.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-sse-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-sse-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To set up operator servers for SSE testing.
-2. To add test cases for SSE module.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-sse-w3c-tests/tests.xml -e "WRTLauncher" -o tct-sse-w3c-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-svg-html5-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-svg-html5-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-svg-html5-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-svg-html5-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-svg-html5-tests" -f /usr/share/tct-svg-html5-tests/tests.xml -o /tmp/tct-svg-html5-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-1. Chromium browser is not enabled with H.264 or AAC codec because of license issue.
-2. Chromium browser reports an error "out of memory" when all the test cases are executed at the same time.
-
-Note: You can report the defects of this test suite to zhiqiang.zhang@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-svg-html5-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-svg-html5-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-svg-html5-tests/tests.xml -e "WRTLauncher" -o tct-svg-html5-tests.results.xml
Authors:
Zou, Zoe <yananx.xu@intel.com>
+
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen SystemInfo API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/systeminfo.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
-
+
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-systeminfo-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-systeminfo-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-systeminfo-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-systeminfo-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-systeminfo-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-systeminfo-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-systeminfo-tizen-tests" -f device:/usr/share/tct-systeminfo-tizen-tests/tests.xml -o /tmp/tct-systeminfo-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-systeminfo-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-systeminfo-tizen-tests/tests.xml -e "WRTLauncher" -o tct-systeminfo-tizen-tests.results.xml
Authors:
leizhan<zhanx.lei@intel.com>
+
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen SystemSetting API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/systemsetting.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
-
+
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-systemsetting-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-systemsetting-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-systemsetting-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-systemsetting-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-systemsetting-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-systemsetting-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-systemsetting-tizen-tests" -f device:/usr/share/tct-systemsetting-tizen-tests/tests.xml -o /tmp/tct-systemsetting-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-systemsetting-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-systemsetting-tizen-tests/tests.xml -e "WRTLauncher" -o tct-systemsetting-tizen-tests.results.xml
----------------------------------------------
Copyright (c) 2012 Intel Corporation.
-Redistribution and use in source and binary forms, with or without modification,
+Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
-* Redistributions of works must retain the original copyright notice, this list
+* Redistributions of works must retain the original copyright notice, this list
of conditions and the following disclaimer.
-* Redistributions in binary form must reproduce the original copyright notice,
- this list of conditions and the following disclaimer in the documentation
+* Redistributions in binary form must reproduce the original copyright notice,
+ this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
-* Neither the name of Intel Corporation nor the names of its contributors
- may be used to endorse or promote products derived from this work without
+* Neither the name of Intel Corporation nor the names of its contributors
+ may be used to endorse or promote products derived from this work without
specific prior written permission.
-THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION BE LIABLE FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
-OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
-EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
+EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Authors:
- Fan, Yugang <yugang.fan@intel.com>
+ Fan, Yugang <yugang.fan@intel.com>
----------------------------------------------
This test suite is used for Tizen tct tests configurations, included:
1. Three steps for user config tests manually.
-2. One config script file for user config other tests which can set the configs automatically.
+2. One config script file for user config other tests which can set the configs automatically.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
----------------------------------------------
Build and Run
----------------------------------------------
-Suppose you only get the source code and Testkit-Lite has been set up on your test machine.If you have obtained tct-testconfig RPM packages, you can directly go to step 3 on the test machine; if you have not installed Testkit-Lite, you need to install the latest version.)
+Suppose you only get the source code and Testkit-Lite has been set up on your test machine.If you have obtained tct-testconfig ZIP packages, you can directly go to step 3 on the test machine; if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-testconfig
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-testconfig.*.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-testconfig" --status approved -f /usr/share/tct-testconfig/tests.xml -o /tmp/tct-testconfig.results.xml -A
-5. Pls check the output of 'tct-testconfig.sh' for the script usage.
-6. A config file template of the tct-testconfig.sh: tct-testconfig.ini for your reference.
+
+2. Build ZIP package by running the following command:
+ ./pack.sh
+
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-testconfig-<version>.zip -d /opt/usr/media/tct
+
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-testconfig/inst.sh
+
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-testconfig/tests.xml -e "WRTLauncher" -o tct-testconfig.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-text-css3-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-text-css3-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-text-css3-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-text-css3-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-text-css3-tests" -f /usr/share/tct-text-css3-tests/tests.xml -o /tmp/tct-text-css3-tests.results.xml -A
-5. Click the "Run" button of the manual harness. A test widget is downloaded. You need to install the widget in WRT, and then load the widget to continue with the tests(for example, the widget UI will show the test results). You also need to fill the result in manual tests harness for result collection.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to yugang.fan@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-text-css3-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-text-css3-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
-2. To enable more auto cases.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-text-css3-tests/tests.xml -e "WRTLauncher" -o tct-text-css3-tests.results.xml
+
+5. Click the "Run" button of the manual harness. A test widget is downloaded. You need to install the widget in WRT, and then load the widget to continue with the tests(for example, the widget UI will show the test results). You also need to fill the result in manual tests harness for result collection.
Authors:
Li, Cici <cici.x.li@intel.com>
+
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen Time API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/time.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Pre-Conditions
----------------------------------------------
Launch 'Settings' application -> Select 'Date and time'
-> Time format: Select AM/PM (12 hours)
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and testkit-lite has been setup on your test machine
- if you have got tct-time-tizen-tests RPM packages, you can directly go to step 3 on testing machine;
+ if you have got tct-time-tizen-tests ZIP packages, you can directly go to step 3 on testing machine;
if you have not installed the testkit-lite, you need to install the latest version)
Steps:
1. Prepare for building by running the following command:
cd tct-time-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-time-tizen-tests-<version>-<release>.<arch>.rpm /tmp
-
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-time-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+2. Build ZIP package by running the following command:
+ ./pack.sh
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-time-tizen-tests" -f device:/usr/share/tct-time-tizen-tests/tests.xml -o /tmp/tct-time-tizen-tests.results.xml
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-time-tizen-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-time-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-time-tizen-tests/tests.xml -e "WRTLauncher" -o tct-time-tizen-tests.results.xml
----------------------------------------------
Copyright (c) 2012 Intel Corporation.
-Redistribution and use in source and binary forms, with or without modification,
+Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
-* Redistributions of works must retain the original copyright notice, this list
+* Redistributions of works must retain the original copyright notice, this list
of conditions and the following disclaimer.
-* Redistributions in binary form must reproduce the original copyright notice,
- this list of conditions and the following disclaimer in the documentation
+* Redistributions in binary form must reproduce the original copyright notice,
+ this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
-* Neither the name of Intel Corporation nor the names of its contributors
- may be used to endorse or promote products derived from this work without
+* Neither the name of Intel Corporation nor the names of its contributors
+ may be used to endorse or promote products derived from this work without
specific prior written permission.
-THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION BE LIABLE FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
-OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
-EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+THIS SOFTWARE IS PROVIDED BY INTEL CORPORATION "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL INTEL CORPORATION BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
+OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
+EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Authors:
Wang, ChaoX <chaox.wang@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/tizen.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and testkit-lite has been setup on your test machine
- if you have got tct-tizen-tizen-tests RPM packages, you can directly go to step 3 on testing machine;
+ if you have got tct-tizen-tizen-tests ZIP packages, you can directly go to step 3 on testing machine;
if you have not installed the testkit-lite, you need to install the latest version)
Steps:
1. Prepare for building by running the following command:
cd tct-tizen-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-tizen-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+2. Build ZIP package by running the following command:
+ ./pack.sh
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-tizen-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-tizen-tizen-tests-<version>.zip -d /opt/usr/media/tct
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-tizen-tizen-tests" -f device:/usr/share/tct-tizen-tizen-tests/tests.xml -o /tmp/tct-tizen-tizen-tests.results.xml
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-tizen-tizen-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-tizen-tizen-tests/tests.xml -e "WRTLauncher" -o tct-tizen-tizen-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-touchevent-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-touchevent-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-touchevent-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-touchevent-w3c-tests-1.1.2-1.noarch.rpm --nodeps
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-touchevent-w3c-tests" -f /usr/share/tct-touchevent-w3c-tests/tests.xml -o /tmp/tct-touchevent-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-None
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-touchevent-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-touchevent-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-touchevent-w3c-tests/tests.xml -e "WRTLauncher" -o tct-touchevent-w3c-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-transitions-css3-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-transitions-css3-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-transitions-css3-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-transitions-css3-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-transitions-css3-tests" -f /usr/share/tct-transitions-css3-tests/tests.xml -o /tmp/tct-transitions-css3-tests.results.xml -A
-5. Click the "Run" button of the manual harness. A test widget is downloaded. You need to install the widget in WRT, and then load the widget to continue with the tests(for example, the widget UI will show the test results). You also need to fill the result in manual tests harness for result collection.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to yugang.fan@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-transitions-css3-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-transitions-css3-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
-2. To enable more auto cases.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-transitions-css3-tests/tests.xml -e "WRTLauncher" -o tct-transitions-css3-tests.results.xml
2. Run the cases in the package as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-typedarrays-nonw3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-typedarrays-nonw3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-typedarrays-nonw3c-tests
-2. Build RPM package by running the following command:
- pack.sh -t all
-3. Install RPM on the machine as "root" user by running the following command:
- rpm -ivh tct-typedarrays-nonw3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-typedarrays-nonw3c-tests" -f /usr/share/tct-typedarrays-nonw3c-tests/tests.xml -o /tmp/tct-typedarrays-nonw3c-tests.results.xml -A
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Chromium browser does not support the ViewPort feature.
-
-Note: You can report the defects of this test suite to yugang.fan@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-typedarrays-nonw3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-typedarrays-nonw3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. Fix bugs.
-2. Enable more auto cases.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-typedarrays-nonw3c-tests/tests.xml -e "WRTLauncher" -o tct-typedarrays-nonw3c-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-ui-css3-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-ui-css3-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-ui-css3-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-ui-css3-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-ui-css3-tests" -f /usr/share/tct-ui-css3-tests/tests.xml -o /tmp/tct-ui-css3-tests.results.xml -A
-5. Click the "Run" button of the manual harness. A test widget is downloaded. You need to install the widget in WRT, and then load the widget to continue with the tests(for example, the widget UI will show the test results). You also need to fill the result in manual tests harness for result collection.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to yugang.fan@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-ui-css3-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-ui-css3-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
-2. To enable more auto cases.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-ui-css3-tests/tests.xml -e "WRTLauncher" -o tct-ui-css3-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-vibration-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-vibration-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-vibration-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-vibration-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-vibration-w3c-tests" -f /usr/share/tct-vibration-w3c-tests/tests.xml -o /tmp/tct-vibration-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to zhiqiang.zhang@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-vibration-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-vibration-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To format existing test cases.
-2. To design tests to cover all specifications P1/P2/P3 testing.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-vibration-w3c-tests/tests.xml -e "WRTLauncher" -o tct-vibration-w3c-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-video-html5-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-video-html5-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-video-html5-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-video-html5-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-video-html5-tests" -f /usr/share/tct-video-html5-tests/tests.xml -o /tmp/tct-video-html5-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-1. Chromium browser is not enabled with H.264 or AAC codec because of license issue.
-
-Note: You can report the defects of this test suite to zhiqiang.zhang@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-video-html5-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-video-html5-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-video-html5-tests/tests.xml -e "WRTLauncher" -o tct-video-html5-tests.results.xml
Note: Chromium does not support loading local files from local browser by default. If you want to load local files, you must add boot argument like 'chromium-browser --allow-file-access-from-files'.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-webaudio-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-webaudio-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-webaudio-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-webaudio-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-webaudio-w3c-tests" -f /usr/share/tct-webaudio-w3c-tests/tests.xml -o /tmp/tct-webaudio-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-1. Chromium browser is not enabled with H.264 or AAC codec because of license issue.
-Note: You can report the defects of this test suite to qingx.ge@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-webaudio-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-webaudio-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-webaudio-w3c-tests/tests.xml -e "WRTLauncher" -o tct-webaudio-w3c-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-webdatabase-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-webdatabase-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-webdatabase-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-webdatabase-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-webdatabase-w3c-tests" -f /usr/share/tct-webdatabase-w3c-tests/tests.xml -o /tmp/tct-webdatabase-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to weiwix.fan@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-webdatabase-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-webdatabase-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs.
-2. To enable more auto cases.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-webdatabase-w3c-tests/tests.xml -e "WRTLauncher" -o tct-webdatabase-w3c-tests.results.xml
2. Run the cases in the package as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-webgl-nonw3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-webgl-nonw3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-webgl-nonw3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-webgl-nonw3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e “WRTLauncher tct-webgl-nonw3c-tests” -f /usr/share/tct-webgl-nonw3c-tests/tests.xml -o result.webgl.xml
-
-----------------------------------------------
-Known Issues
-----------------------------------------------
-1. Chromium browser is not enabled with WebGL by default. Therefore, if you want to test these cases on Ubuntu system, you must start up Chromium like this:
- chromium-browser --enable-webgl --ignore-gpu-blacklist --allow-file-access-from-files.
-
- --enable-webgl: enable webgl.
- --ignore-gpu-blacklist: Your graphics card may be too old to support webgl. So you must add this boot parameter to ignore the blacklist of graphics card.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-Note: You can report the defects of this test suite to junx.cao@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-webgl-nonw3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-webgl-nonw3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-webgl-nonw3c-tests/tests.xml -e "WRTLauncher" -o tct-webgl-nonw3c-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Pre-conditions
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-webmessaging-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-webmessaging-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-webmessaging-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-webmessaging-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-webmessaging-w3c-tests" -f /usr/share/tct-webmessaging-w3c-tests/tests.xml -o /tmp/tct-webmessaging-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-None
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-webmessaging-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-webmessaging-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-webmessaging-w3c-tests/tests.xml -e "WRTLauncher" -o tct-webmessaging-w3c-tests.results.xml
Authors:
SungHyun Min <shyun.min@samsung.com>
+
+
----------------------------------------------
Introduction
----------------------------------------------
This test suite is for testing Tizen WebSetting API, which covers the following specifications:
https://developer.tizen.org/help/topic/org.tizen.web.device.apireference/tizen/websetting.html
+
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Testkit-stub must be installed on target device.
2. Testkit-lite must be installed on test machine.
-
+
+
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-websetting-tizen-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-websetting-tizen-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-websetting-tizen-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
+2. Build ZIP package by running the following command:
+ ./pack.sh
-3. Copy RPM to the test machine by running the following command:
- sdb push tct-websetting-tizen-tests-<version>-<release>.<arch>.rpm /tmp
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-websetting-tizen-tests-<version>.zip -d /opt/usr/media/tct
-4. Install RPM on the test machine as "root" user by running the following commands:
- sdb root on
- sdb shell rpm -ih /tmp/tct-websetting-tizen-tests-<version>-<release>.<arch>.rpm
- sdb root off
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-websetting-tizen-tests/inst.sh
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-websetting-tizen-tests" -f device:/usr/share/tct-websetting-tizen-tests/tests.xml -o /tmp/tct-websetting-tizen-tests.results.xml
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-websetting-tizen-tests/tests.xml -e "WRTLauncher" -o tct-websetting-tizen-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Pre-conditions
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-websocket-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-websocket-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-websocket-w3c-tests
+
2. Modify tct-websocket-w3c-tests/tests.xml to change the est_script_entry node from 'http://127.0.0.1:8080'
to 'http://192.168.13.28:8080'(If the server IP address is 192.168.13.28);
-3. Build RPM packages by running the following command:
- pack.sh -t all
-4. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-websocket-w3c-tests-<version>-<release>.<arch>.rpm
-5. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-websocket-w3c-tests" -f /usr/share/tct-websocket-w3c-tests/tests.xml -o /tmp/tct-websocket-w3c-tests.results.xml
+3. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-None
+4. Unzip the package on the test machine by running the following command:
+ unzip -o tct-websocket-w3c-tests-<version>.zip -d /opt/usr/media/tct
+5. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-websocket-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+6. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-websocket-w3c-tests/tests.xml -e "WRTLauncher" -o tct-websocket-w3c-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have obtained tct-webstorage-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-webstorage-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-webstorage-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-webstorage-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-webstorage-w3c-tests" -f /usr/share/tct-webstorage-w3c-tests/tests.xml -o /tmp/tct-webstorage-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-Note: You can report the defects of this test suite to weiwix.fan@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-webstorage-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-webstorage-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-1. To fix bugs
-2. To enable more auto cases.
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-webstorage-w3c-tests/tests.xml -e "WRTLauncher" -o tct-webstorage-w3c-tests.results.xml
Zhang, GeX <gex.zhang@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
3. Run the cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only got the source code set up on your test machine.
- If you have obtained tct-wgtapi01-w3c-tests RPM packages on the test machine, you can directly go to step 3;
+ If you have obtained tct-wgtapi01-w3c-tests ZIP packages on the test machine, you can directly go to step 3;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-wgtapi01-w3c-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-wgtapi01-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-wgtapi01-w3c-tests" -f device:"/usr/share/tct-wgtapi01-w3c-tests/tests.xml"
-
-----------------------------------------------
-Known Issues
-----------------------------------------------
-
-Note: If there is any defects in this test suite, please do not hesitate to contact us by the email jianhuix.a.yue@intel.com.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Todo
-----------------------------------------------
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-wgtapi01-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-wgtapi01-w3c-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-wgtapi01-w3c-tests/tests.xml -e "WRTLauncher" -o tct-wgtapi01-w3c-tests.results.xml
Zhang, GeX <gex.zhang@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
1. Run the cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code which has been set up on your test machine.
- If you have obtained tct-wgtapi02-w3c-tests RPM packages, you can directly go to step 3 on the test machine)
+ If you have obtained tct-wgtapi02-w3c-tests ZIP packages, you can directly go to step 3 on the test machine)
Steps:
1. Prepare for building by running the following command:
cd tct-wgtapi02-w3c-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-wgtapi02-w3c-tests-<version>-<release>.<arch>.rpm
-4. Prepare to install widget application by running the following command:
- cd /opt/tct-wgtapi02-w3c-tests/widgetinterface/w3c
-5. Install WGT on the test machine as "root" user by running the following command:
- wrt-installer -i <wgt>
-6. Run test cases as "normal" user with the following command:
- wrt-launcher -s <wgt.id>
-7. Uninstall WGT from the test machine as "root" user by running the following command:
- wrt-installer -un <wgt.id>
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-wgtapi02-w3c-tests-<version>.zip -d /opt/usr/media/tct
-Note: If there is any defects in this test suite, please do not hesitate to contact us by the email jianhuix.a.yue@intel.com.
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-wgtapi02-w3c-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-wgtapi02-w3c-tests/tests.xml -e "WRTLauncher" -o tct-wgtapi02-w3c-tests.results.xml
-----------------------------------------------
-Todo
-----------------------------------------------
+6. Prepare to install widget application by running the following command:
+ cd /opt/usr/media/tct/opt/tct-wgtapi02-w3c-tests/widgetinterface/w3c
+7. Install WGT on the test machine by running the following command:
+ wrt-installer -i <wgt>
+
+8. Run test cases on the test machine with the following command:
+ wrt-launcher -s <wgt.id>
+9. Uninstall WGT from the test machine by running the following command:
+ wrt-installer -un <wgt.id>
Zhang, GeX <gex.zhang@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
3. Run the cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code which has been set up on your test machine.
- If you have obtained tct-widget01-w3c-tests RPM packages, you can directly go to step 3 on the test machine)
+ If you have obtained tct-widget01-w3c-tests ZIP packages, you can directly go to step 3 on the test machine)
Steps:
1. Prepare for building by running the following command:
cd tct-widget01-w3c-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-widget01-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-widget01-w3c-tests" -f device:"/usr/share/tct-widget01-w3c-tests/tests.xml"
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-
-Note: If there is any defects in this test suite, please do not hesitate to contact us by the email gex.zhang@intel.com.
-
-----------------------------------------------
-Todo
-----------------------------------------------
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-widget01-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-widget01-w3c-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-widget01-w3c-tests/tests.xml -e "WRTLauncher" -o tct-widget01-w3c-tests.results.xml
Zhang, GeX <gex.zhang@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
1. Run the cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code which has been set up on your test machine.
- If you have obtained tct-widget02-w3c-tests RPM packages, you can directly go to step 3 on the test machine)
+ If you have obtained tct-widget02-w3c-tests ZIP packages, you can directly go to step 3 on the test machine)
Steps:
1. Prepare for building by running the following command:
cd tct-widget02-w3c-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-widget02-w3c-tests-<version>-<release>.<arch>.rpm
-4. Prepare to install widget application by running the following command:
- cd /opt/tct-widget02-w3c-tests/WidgetPackaging/w3c
-5. Install WGT on the test machine as "root" user by running the following command:
- wrt-installer -i <wgt>
-6. Run test cases as "normal" user with the following command:
- wrt-launcher -s <wgt.id>
-7. Uninstall WGT from the test machine as "root" user by running the following command:
- wrt-installer -un <wgt.id>
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-widget02-w3c-tests-<version>.zip -d /opt/usr/media/tct
-Note: If there is any defects in this test suite, please do not hesitate to contact us by the email gex.zhang@intel.com.
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-widget02-w3c-tests/inst.sh
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-widget02-w3c-tests/tests.xml -e "WRTLauncher" -o tct-widget02-w3c-tests.results.xml
-----------------------------------------------
-Todo
-----------------------------------------------
+6. Prepare to install widget application by running the following command:
+ cd /opt/usr/media/tct/opt/tct-widget02-w3c-tests/WidgetPackaging/w3c
+7. Install WGT on the test machine by running the following command:
+ wrt-installer -i <wgt>
+
+8. Run test cases on the test machine with the following command:
+ wrt-launcher -s <wgt.id>
+9. Uninstall WGT from the test machine by running the following command:
+ wrt-installer -un <wgt.id>
Zhang, GeX <gex.zhang@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
2. Connect to Wi-Fi.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code which has been set up on your test machine.
- If you have obtained tct-widgetpolicy-w3c-tests RPM packages, you can directly go to step 3 on the test machine)
+ If you have obtained tct-widgetpolicy-w3c-tests ZIP packages, you can directly go to step 3 on the test machine)
Steps:
1. Prepare for building by running the following command:
cd tct-widgetpolicy-w3c-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-widgetpolicy-w3c-tests-<version>-<release>.<arch>.rpm
-4. Prepare to install widget application by running the following command:
- cd /opt/tct-widgetpolicy-w3c-tests/widgetpolicy/w3c
-5. Install WGT on the test machine as "root" user by running the following command:
- wrt-installer -i <wgt>
-6. Run test cases as "normal" user with the following command:
- wrt-launcher -s <wgt.id>
-7. Uninstall WGT from the test machine as "root" user by running the following command:
- wrt-installer -un <wgt.id>
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-widgetpolicy-w3c-tests-<version>.zip -d /opt/usr/media/tct
-Note: If there is any defects in this test suite, please do not hesitate to contact us by the email gex.zhang@intel.com.
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-widgetpolicy-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-widgetpolicy-w3c-tests/tests.xml -e "WRTLauncher" -o tct-widgetpolicy-w3c-tests.results.xml
+
+6. Prepare to install widget application by running the following command:
+ cd /opt/usr/media/tct/opt/tct-widgetpolicy-w3c-tests/widgetpolicy/w3c
+7. Install WGT on the test machine by running the following command:
+ wrt-installer -i <wgt>
+
+8. Run test cases on the test machine with the following command:
+ wrt-launcher -s <wgt.id>
+9. Uninstall WGT from the test machine by running the following command:
+ wrt-installer -un <wgt.id>
Zhang, Ge <gex.zhang@intel.com>
+
----------------------------------------------
Introduction
----------------------------------------------
----------------------------------------------
Test Environment
-----------------------------------------------
+----------------------------------------------
1. Pre-install Testkit-Lite package on Host(ubuntu12.04 and ubuntu12.10).
sudo apt-get install python-pip
sudo pip install requests
- sudo dpkg -i testkit-lite-<version>.deb
+ sudo dpkg -i testkit-lite-<version>.deb
2. Push "httpserver" into test machine.
sdb root on
sdb push httpserver /usr/bin
3. Run the cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite which has been set up on your test machine.
- If you have obtained tct-workers-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have obtained tct-workers-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-workers-w3c-tests
-2. Build RPM packages by running the following command:
- ./pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-workers-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-workers-w3c-tests" -f device:"/usr/share/tct-workers-w3c-tests/tests.xml"
-5. Please make sure the network is connected when testing the Web Workers.
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-
-Note: If there is any defects in this test suite, please do not hesitate to contact us by the email gex.zhang@intel.com.
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-workers-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-workers-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-workers-w3c-tests/tests.xml -e "WRTLauncher" -o tct-workers-w3c-tests.results.xml
2. Run these cases as "normal" user.
-----------------------------------------------
-Installation
-----------------------------------------------
-./autogen
-./configure prefix=/usr
-make && make install
-
-
----------------------------------------------
Pre-conditions
----------------------------------------------
Build and Run
----------------------------------------------
(Suppose you only get the source code and Testkit-Lite has been set up on your test machine.
- If you have got tct-xmlhttprequest-w3c-tests RPM packages, you can directly go to step 3 on the test machine;
+ If you have got tct-xmlhttprequest-w3c-tests ZIP packages, you can directly go to step 3 on the test machine;
if you have not installed Testkit-Lite, you need to install the latest version.)
Steps:
1. Prepare for building by running the following command:
cd tct-xmlhttprequest-w3c-tests
-2. Build RPM packages by running the following command:
- pack.sh -t all
-3. Install RPM on the test machine as "root" user by running the following command:
- rpm -ivh tct-xmlhttprequest-w3c-tests-<version>-<release>.<arch>.rpm
-4. Run test cases as "normal" user with the following command:
- testkit-lite -e "WRTLauncher tct-xmlhttprequest-w3c-tests" -f /usr/share/tct-xmlhttprequest-w3c-tests/tests.xml -o /tmp/tct-xmlhttprequest-w3c-tests.results.xml
+2. Build ZIP package by running the following command:
+ ./pack.sh
-----------------------------------------------
-Known Issues
-----------------------------------------------
-None
+3. Unzip the package on the test machine by running the following command:
+ unzip -o tct-xmlhttprequest-w3c-tests-<version>.zip -d /opt/usr/media/tct
+4. Install the package on the test machine by running the following command:
+ /opt/usr/media/tct/opt/tct-xmlhttprequest-w3c-tests/inst.sh
-----------------------------------------------
-Todo
-----------------------------------------------
-None
+5. Run test cases by running the following command on host:
+ testkit-lite -f device:/opt/usr/media/tct/opt/tct-xmlhttprequest-w3c-tests/tests.xml -e "WRTLauncher" -o tct-xmlhttprequest-w3c-tests.results.xml
projects / test / tct / web / api.git / commitdiff