User Tools

Site Tools


execution_and_report

Execute Testcase

*Note:To run test runner on Windows platform download mtee a win32 console application “https://ritchielawrence.github.io/mtee/” and python3.

Go to <iotivity_root>/test/test_manager folder. For Linux and Windows testcases run test_runner.py, for Android testcases run android_test_runner.py and for Tizen testcases run tizen_test_runner.py. Each script accept parameter(s) to filter testcases. Some common parameters are:

  • - m for module_name
  • - f for name or sub string of test_binary
  • - x for transport name
  • - n for network name
  • - u for specific test suite
  • - c for specific test case
  • - d for android or tizen device Id
  • - t for Ubuntu version and Linux bit (applicable only for Linux testcase)
  • - o for to run each testcase once (applicable only for Linux testcase)
  • - a for to run each testcase standalone mode (applicable only for Linux testcase)

Example:

./test_runner.py -m sm -a -o -t 14.04.32bit

./test_runner.py -f ca_ip_test -a -o 14.04.32 bit

./android_test_runner.py -m pm

./tizen_test_runner.py -m re

Report Generation

After completion of testcase execution, again go to <iotivity_root>/test/test_manager folder and run result_reporter.script.

Result folder will be generated in <iotivity_root>/test/TestReport/Result folder. Folder name will be in TestResult_timestring format. In that folder, an excel report will generated where summary of execution will be found.

Run CA Testcase

CA testcases executes for multiple transport in multiple platform. For IP and TCP transport in Linux platform, testcases needed to run in both ethernet and wifi network. CA Simulator needs to be run before running testcases. For IP and TCP transport, simulator can run on same device or in separate device. But for BT/BLE transport simulator must be run in separate device.

Linux command

Go to <iotivity_root>/test/test_manager folder and run “./test_runner.py -f ca_test -a -o”

Go to <iotivity_root>/test/bin/linux folder and run “./iotivity_ca_simulator 0 <ethernet-ip-address-of-tc-device> eq”. Go to <iotivity_root>/test/test_manager folder and run “./test_runner.py -f ca_ip_test -a -o -x ip -n eth”

Go to <iotivity_root>/test/bin/linux folder and run “./iotivity_ca_simulator 0 <wifi-ip-address-of-tc-device> eq”. Go to <iotivity_root>/test/test_manager folder and run “./test_runner.py -f ca_ip_test -a -o -x ip -n wifi”

Go to <iotivity_root>/test/bin/linux folder and run “./iotivity_ca_simulator 4 <ethernet-ip-address-of-tc-device> eq”. Go to <iotivity_root>/test/test_manager folder and run “./test_runner.py -f ca_tcp_test -a -o -x ip -n eth”

Go to <iotivity_root>/test/bin/linux folder and run “./iotivity_ca_simulator 4 <wifi-ip-address-of-tc-device> eq”. Go to <iotivity_root>/test/test_manager folder and run “./test_runner.py -f ca_tcp_test -a -o -x ip -n wifi”

Android command

Go to <iotivity_root>/test/test_manager folder and run “./android_test_runner.py -f ca_test”

Go to /data/local/tmp folder in android simulator device using adb and run “./iotivity_ca_simulator 0. Go to <iotivity_root>/test/test_manager folder and run ”./android_test_runner.py -f ca_ip_test -x ip -w gtest“

Go to /data/local/tmp folder in android simulator device using adb and run ”./iotivity_ca_simulator 4. Go to <iotivity_root>/test/test_manager folder and run “./android_test_runner.py -f ca_tcp_test -x tcp -w gtest”

Run “adb shell am start -a android.intent.action.VIEW -n org.iotivity.ca.simulator/.MainActivity -e transport 2” command for android simulator device. Update config.ini file using configuration CA_IP=0 CA_LE=0 CA_EDR=1 CA_TCP=0 in /data/local/tmp folder in android tc device. Go to <iotivity_root>/test/test_manager folder and run “./android_test_runner.py -m ca -x bt”

Run “adb shell am start -a android.intent.action.VIEW -n org.iotivity.ca.simulator/.MainActivity -e transport 1” command for android simulator device. Update config.ini file using configuration CA_IP=0 CA_LE=1 CA_EDR=0 CA_TCP=0 in /data/local/tmp folder in android tc device. Go to <iotivity_root>/test/test_manager folder and run “./android_test_runner.py -m ca -x ble”

Tizen command

./tizen_test_runner.py -f ca_test

Go to /usr/opt/media/bin folder in tizen simulator device using sdb and run “./iotivity_ca_simulator 0”. Go to <iotivity_root>/test/test_manager folder and run “./tizen_test_runner.py -f ca_ip_test -x ip”

Go to /usr/opt/media/bin folder in tizen simulator device using sdb and run “./iotivity_ca_simulator 4”. Go to <iotivity_root>/test/test_manager folder and run “./tizen_test_runner.py -f ca_ip_test -x tcp”

Go to /usr/opt/media/bin folder in tizen simulator device using sdb and run “./iotivity_ca_simulator 2”. Go to <iotivity_root>/test/test_manager folder and run “./tizen_test_runner.py -f ca_ip_test -x bt”

Go to /usr/opt/media/bin folder in tizen simulator device using sdb and run “./iotivity_ca_simulator 1”. Go to <iotivity_root>/test/test_manager folder and run “./tizen_test_runner.py -f ca_ip_test -x ble”

Windows command

Go to <iotivity_root>/test/test_manager folder and run “test_runner.py -f ca_test -a -o”

Go to <iotivity_root>/test/bin/windows folder and run “iotivity_ca_simulator 0 <ethernet-ip-address-of-tc-device> eq”. Go to <iotivity_root>/test/test_manager folder and run “test_runner.py -f ca_ip_test -a -o -x ip -n eth”

Go to <iotivity_root>/test/bin/windows folder and run “iotivity_ca_simulator 0 <wifi-ip-address-of-tc-device> eq”. Go to <iotivity_root>/test/test_manager folder and run “test_runner.py -f ca_ip_test -a -o -x ip -n wifi”

Go to <iotivity_root>/test/bin/windows folder and run “iotivity_ca_simulator 4 <ethernet-ip-address-of-tc-device> eq”. Go to <iotivity_root>/test/test_manager folder and run “test_runner.py -f ca_tcp_test -a -o -x ip -n eth”

Go to <iotivity_root>/test/bin/windows folder and run “iotivity_ca_simulator 4 <wifi-ip-address-of-tc-device> eq”. Go to <iotivity_root>/test/test_manager folder and run “test_runner.py -f ca_tcp_test -a -o -x ip -n wifi”

execution_and_report.txt · Last modified: 2017/08/09 11:40 by Kousthubha M N