test: split CI test environment:

Currently CI test environment is complicated, usually includes NIC, AP.
These devices are not used for a lot test cases. Therefore we split the
test environment, remove unnecessary devices. Then it will be easier to
create CI runners.
This commit is contained in:
He Yin Ling 2018-08-26 12:15:51 +08:00 committed by bot
parent 6d865c6104
commit b9f7e0a1a2
21 changed files with 3181 additions and 713 deletions

View file

@ -885,7 +885,7 @@ UT_001_25:
tags:
- ESP32_IDF
- UT_T1_1
UT_001_26:
<<: *unit_test_template
tags:
@ -921,7 +921,7 @@ UT_001_31:
tags:
- ESP32_IDF
- UT_T1_1
UT_001_32:
<<: *unit_test_template
tags:
@ -933,7 +933,7 @@ UT_001_33:
tags:
- ESP32_IDF
- UT_T1_1
UT_001_34:
<<: *unit_test_template
tags:
@ -1057,14 +1057,14 @@ UT_004_10:
- ESP32_IDF
- UT_T1_1
- psram
UT_004_11:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
- psram
UT_005_01:
<<: *unit_test_template
tags:
@ -1207,55 +1207,19 @@ IT_001_01:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_1
- SSC_T1_4
IT_001_02:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_1
- SSC_T1_4
IT_001_03:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_1
IT_001_04:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_1
IT_001_05:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_1
IT_001_06:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_1
IT_001_07:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_1
IT_001_08:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_1
IT_001_09:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_1
- SSC_T1_4
IT_002_01:
<<: *test_template
@ -1267,85 +1231,79 @@ IT_003_01:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_1
- SSC_T2_5
IT_003_02:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_1
- SSC_T2_5
IT_003_03:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_1
- SSC_T2_5
IT_003_04:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_1
- SSC_T2_5
IT_003_05:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_1
- SSC_T2_5
IT_003_06:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_1
- SSC_T2_5
IT_003_07:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_1
- SSC_T2_5
IT_003_08:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_1
- SSC_T2_5
IT_003_09:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_1
- SSC_T2_5
IT_003_10:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_1
- SSC_T2_5
IT_003_11:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_1
- SSC_T2_5
IT_003_12:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_1
- SSC_T2_5
IT_003_13:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_1
IT_003_14:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_1
- SSC_T2_5
IT_004_01:
<<: *test_template
@ -1357,7 +1315,61 @@ IT_005_01:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_WEP
- SSC_T1_5
IT_005_02:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_5
IT_006_01:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_6
IT_006_02:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_6
IT_006_03:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_6
IT_006_04:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_6
IT_006_05:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_6
IT_007_01:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_7
IT_007_02:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_7
IT_008_01:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_8
IT_009_01:
<<: *test_template
@ -1377,58 +1389,32 @@ IT_011_01:
- ESP32_IDF
- SSC_T50_1
IT_501_01:
IT_012_01:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_1
- stress_test
- SSC_T1_9
IT_501_02:
IT_013_01:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_1
- stress_test
- SSC_T2_2
IT_501_03:
IT_013_02:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_1
- stress_test
- SSC_T2_2
IT_502_01:
IT_014_01:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_1
- stress_test
- SSC_T2_3
IT_502_02:
IT_015_01:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_1
- stress_test
IT_503_01:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T5_1
- stress_test
IT_503_02:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T5_1
- stress_test
IT_503_03:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T5_1
- stress_test
- SSC_T2_4

View file

@ -0,0 +1,182 @@
.MESH_INIT_COND: &MESH_INIT_COND
test script: InitCondMesh
restore post cmd set:
- ''
- - 'MSSC SSC[1-<node_num>] mesh -F -o 4 -a 1'
- ['P SSC[1-<node_num>] C +MESHFLAG:OK']
- - 'MSSC SSC[1-<node_num>] mesh -F -o 5 -a 1'
- ['P SSC[1-<node_num>] C +MESHFLAG:OK']
- - 'MSSC SSC[1-<node_num>] mesh -Q -o 1'
- ['P SSC[1-<node_num>] C MESH_NETWORK']
- - 'MSSC SSC[1-<node_num>] mesh -Q -o 3'
- ['P SSC[1-<node_num>] C +MESH_CONFIG:ALL']
- - 'MSSC SSC[1-<node_num>] ram'
- ['P SSC[1-<node_num>] C +FREEHEAP:']
.mesh_get_device_mac: &mesh_get_device_mac
LIST_MERGE:
- - 'MSSC SSC[1-<node_num>] mac'
- ['R SSC[1-<node_num>] A <device_mac>:\+STAMAC:(.+)\r\n']
.mesh_check_get_tree: &mesh_check_get_tree
LIST_MERGE:
- - 'MSSC SSC[1-<node_num>] mac'
- ['P SSC[1-<node_num>] A <device_mac>:\+STAMAC:(.+)\r\n']
- - 'MSSC SSC[1-<node_num>] mesh -Q -o 2'
- ['P SSC[1-<node_num>] T <node_num>']
- - 'MESHTREE'
- ['P PC_COM RE "MESHTREE:%%s%20nodes"%%(<node_num>)']
.mesh_check_tree_stable: &mesh_check_tree_stable
LIST_MERGE:
- - 'DELAY 10'
- ['']
- - 'SSC MNODE(0) mesh -Q -o 1 -t 10'
- ['R MNODE(0) C MESH_STABLE_CHECK:PASS']
.reboot_all: &reboot_all
LIST_MERGE:
- - 'MSSC SSC[1-<node_num>] reboot'
- ['P SSC[1-<node_num>] C !!!ready!!!']
.force_reboot: &force_reboot
LIST_MERGE:
- - 'FPOWERON SSC[1-<node_num>]'
- ['']
- - 'DELAY 1'
- ['']
- - 'MSSC SSC[1-<node_num>] restore'
- ['P SSC[1-<node_num>] C !!!ready!!!']
.all_nodes_mesh_config: &all_nodes_mesh_config
LIST_MERGE:
- - 'MSSC SSC[1-<node_num>] mesh -I'
- ['P SSC[1-<node_num>] C +MESH:INITED']
- - 'MSSC SSC[1-<node_num>] mesh -A -o 12 -t <duration_ms> -c <cnx_rssi> -l <select_rssi> -f <switch_rssi> -b <backoff_rssi>'
- ['P SSC[1-<node_num>] C +MESH_SET_PARENT_SWITCH:OK']
- - 'MSSC SSC[1-<node_num>] mesh -A -o 14 -t <threshold_high> -c <threshold_medium> -l <threshold_low>'
- ['P SSC[1-<node_num>] C +MESH_RSSI_THRESHOLD:OK']
- - 'MSSC SSC[1-<node_num>] mesh -A -o 9 -t <auth_mode> -s <map_password>'
- ['P SSC[1-<node_num>] C +MESH_SET_AP_AUTH_MODE:OK']
- - 'MSSC SSC[1-<node_num>] mesh -P -g <mesh_id> -s <ap_ssid> -p <ap_password> -n <ap_channel> -m <max_connect> -y <max_layer>'
- ['P SSC[1-<node_num>] C +MESH:CONFIG,OK']
.root_do_connect: &root_do_connect
LIST_MERGE:
- - 'SOC SOC1 LISTEN <test_tcp_port1> <pc_ip>'
- ['R SOC_COM L OK']
- - 'SSC MNODE(0) mesh -S -o 0 -i <pc_ip> -t <test_tcp_port1>'
- ['P MNODE(0) C +CONNECT,OK']
- ['P SOC1 C +ACCEPT']
- - 'SOC SOC1 MACCEPT GSOC1'
- ['R SOC_COM L OK']
initial condition:
- tag: ENABLED_1
<<: *MESH_INIT_COND
initial condition detail: if mesh tree not exist, start one node first, then start others, after mesh network
established, root connect server
check cmd set:
- ''
- *mesh_check_get_tree
- *mesh_check_tree_stable
- *root_do_connect
restore cmd set:
- ''
- *reboot_all
- *all_nodes_mesh_config
- - SSC SSC1 mesh -T
- - P SSC1 C +MESH:START,OK
- - DELAY 10
- - P SSC1 C MESH_EVENT_CONNECTED
- - SSC SSC[2-<node_num>] mesh -T
- - P SSC[2-<node_num>] C +MESH:START,OK
- - DELAY <delay_time>
- - ''
- *mesh_check_get_tree
- *mesh_check_tree_stable
- *root_do_connect
force restore cmd set:
- ''
- *force_reboot
- *all_nodes_mesh_config
- - SSC SSC1 mesh -T
- - P SSC1 C +MESH:START,OK
- - DELAY 10
- - P SSC1 C MESH_EVENT_CONNECTED
- - SSC SSC[2-<node_num>] mesh -T
- - P SSC[2-<node_num>] C +MESH:START,OK
- - DELAY <delay_time>
- - ''
- *mesh_check_get_tree
- *mesh_check_tree_stable
- *root_do_connect
- tag: ENABLED_2
<<: *MESH_INIT_COND
initial condition detail: if mesh tree not exist, start all nodes together
check cmd set:
- ''
- *mesh_check_get_tree
- *mesh_check_tree_stable
restore cmd set:
- ''
- *reboot_all
- *all_nodes_mesh_config
- - MSSC SSC[1-<node_num>] mesh -T
- - P SSC[1-<node_num>] C +MESH:START,OK
- - DELAY <delay_time>
- - ''
- *mesh_check_get_tree
- *mesh_check_tree_stable
force restore cmd set:
- ''
- *force_reboot
- *all_nodes_mesh_config
- - MSSC SSC[1-<node_num>] mesh -T
- - P SSC[1-<node_num>] C +MESH:START,OK
- - DELAY <delay_time>
- - ''
- *mesh_check_get_tree
- *mesh_check_tree_stable
- tag: ENABLED_3
<<: *MESH_INIT_COND
initial condition detail: all mesh nodes configed but not started
check cmd set:
- ''
- - ASSERT
- - ''
restore cmd set:
- ''
- *reboot_all
- *all_nodes_mesh_config
- *mesh_get_device_mac
force restore cmd set:
- ''
- *force_reboot
- *all_nodes_mesh_config
- *mesh_get_device_mac
- tag: DISABLED_1
<<: *MESH_INIT_COND
initial condition detail: all mesh node in softap+sta mode, disable all mesh node
restore post cmd set:
- ''
check cmd set:
- ''
- - ASSERT
- - ''
restore cmd set:
- ''
- *reboot_all
- - MSSC SSC[1-<node_num>] op -S -o 3
- - P SSC[1-<node_num>] C +MODE:OK
- - MSSC SSC[1-<node_num>] sta -D
- - P SSC[1-<node_num>] C +QAP:OK
- *mesh_get_device_mac
force restore cmd set:
- ''
- *force_reboot
- - MSSC SSC[1-<node_num>] op -S -o 3
- - P SSC[1-<node_num>] C +MODE:OK
- - MSSC SSC[1-<node_num>] sta -D
- - P SSC[1-<node_num>] C +QAP:OK
- *mesh_get_device_mac

View file

@ -7,16 +7,12 @@
- - SSC SSC1 ram
- - 'R SSC1 C +FREEHEAP:'
.MESH_INIT_COND: &MESH_INIT_COND
test script: InitCondBase
restore post cmd set:
- ''
- - SSC SSC[1-<node_num>] mesh -Q -o 1
- - R SSC[1-<node_num>] C MESH_NETWORK
- - SSC SSC[1-<node_num>] mesh -Q -o 3
- - R SSC[1-<node_num>] C +MESH_CONFIG:ALL
- - SSC SSC[1-<node_num>] ram
- - R SSC[1-<node_num>] A <heap_size>:(\d+)
.dut1_start_wifi: &dut1_start_wifi
LIST_MERGE:
- - SSC SSC1 op -W -a init
- - R SSC1 C +MODE
- - SSC SSC1 op -W -a start
- - R SSC1 C +MODE
initial condition:
- tag: APM1
@ -25,6 +21,7 @@ initial condition:
APSTA1
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC1 op -Q
- - R SSC1 C +CURMODE:2
- - SSC SSC1 ap -Q
@ -61,6 +58,7 @@ initial condition:
condition APSTA2
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC1 op -Q
- - R SSC1 C +CURMODE:2
- - SSC SSC1 ap -Q
@ -105,6 +103,7 @@ initial condition:
APSTA1
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC1 op -Q
- - R SSC1 C +CURMODE:2
- - SSC SSC1 ap -Q
@ -141,6 +140,7 @@ initial condition:
APSTA2
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC1 op -Q
- - R SSC1 C +CURMODE:2
- - SSC SSC1 ap -Q
@ -182,6 +182,7 @@ initial condition:
- <<: *SSC_INIT_COND
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC1 upgrade -Q -t 1
- - R SSC1 C BIN_ID,0
- - SSC SSC1 upgrade -Q -t 2 -b 0
@ -225,6 +226,7 @@ initial condition:
initial condition detail: testing ap on sta + ap mode (autogen by APM1)
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC1 op -Q
- - R SSC1 C +CURMODE:3
- - SSC SSC1 ap -Q
@ -260,6 +262,7 @@ initial condition:
initial condition detail: testing ap on sta + ap mode, PC join AP (autogen by APM2)
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC1 op -Q
- - R SSC1 C +CURMODE:3
- - SSC SSC1 ap -Q
@ -978,7 +981,7 @@ initial condition:
- tag: BLE_INIT2
<<: *SSC_INIT_COND
initial condition detail: 2 DUT which BLE is enabled, no active connection, DUT2
start adv
load service 0xA0 and start adv
check cmd set:
- ''
- - SSC SSC[1-2] bt -Q
@ -1018,6 +1021,49 @@ initial condition:
- - R SSC2 C +BLEADV:SetAdv,OK
- - SSC SSC2 bleadv -D -z start
- - R SSC2 C +BLEADV:OK
- - SSC SSC1 ram
- - R SSC1 A <heap_size>:(\d+)
- tag: BLE_INIT3
<<: *SSC_INIT_COND
initial condition detail: 2 DUT which BLE is enabled, no active connection, DUT2
load service 0xA2 and start adv
check cmd set:
- ''
- - SSC SSC[1-2] bt -Q
- - R SSC[1-2] C +BT:status,ENABLE
restore cmd set:
- ''
- - SSC SSC[1-2] bt -D -z init
- - 'R SSC[1-2] C +BT:'
- - SSC SSC[1-2] bt -D -z enable
- - 'R SSC[1-2] C +BT:'
force restore cmd set:
- ''
- - SSC SSC[1-2] reboot
- - R SSC[1-2] C !!!ready!!!
- - SSC SSC[1-2] bt -D -z init
- - 'R SSC[1-2] C +BT:'
- - SSC SSC[1-2] bt -D -z enable
- - 'R SSC[1-2] C +BT:'
restore post cmd set:
- ''
- - SSC SSC[1-2] ble -R
- - 'R SSC[1-2] C +BLE:'
- - SSC SSC[1-2] bleconn -D -z all
- - 'R SSC[1-2] C +BLECONN:'
- - SSC SSC[1-2] gatts -S -z delete
- - 'R SSC[1-2] C +GATTS:'
- - SSC SSC[1-2] gattc -U -z all
- - R SSC[1-2] C +GATTC:OK
- - SSC SSC2 gatts -S -z load -p 0xA2
- - R SSC2 C +GATTS:StartService,OK,A002
- - SSC SSC[1-2] bleadv -D -z stop
- - R SSC[1-2] C +BLEADV:OK
- - SSC SSC2 bleadv -L -c 0 -t 3
- - R SSC2 C +BLEADV:SetAdv,OK
- - SSC SSC2 bleadv -D -z start
- - R SSC2 C +BLEADV:OK
- - SSC SSC1 ram
- - R SSC1 A <heap_size>:(\d+)
- tag: BLE_INIT5
@ -1065,7 +1111,7 @@ initial condition:
- tag: BLE_INIT_SMP
<<: *SSC_INIT_COND
initial condition detail: 2 DUT which BLE is enabled, no active connection, DUT2
create GATT service 0xA000, DUT2 start adv, SMP enabled on both DUT and DUT1 load
create GATT service 0xA002, DUT2 start adv, SMP enabled on both DUT and DUT1 load
default initiator param, DUT2 load default responder param
check cmd set:
- ''
@ -1091,8 +1137,8 @@ initial condition:
- - R SSC[1-2] C +GATTC:OK
- - SSC SSC[1-2] bleadv -D -z stop
- - R SSC[1-2] C +BLEADV:OK
- - SSC SSC2 gatts -S -z load -p 0xA0
- - R SSC2 C +GATTS:StartService,OK,A000
- - SSC SSC2 gatts -S -z load -p 0xA2
- - R SSC2 C +GATTS:StartService,OK,A002
- - SSC SSC2 bleadv -L -c 0 -t 3
- - R SSC2 C +BLEADV:SetAdv,OK
- - SSC SSC2 bleadv -D -z start
@ -1120,8 +1166,8 @@ initial condition:
- - R SSC[1-2] C +GATTC:OK
- - SSC SSC[1-2] bleadv -D -z stop
- - R SSC[1-2] C +BLEADV:OK
- - SSC SSC2 gatts -S -z load -p 0xA0
- - R SSC2 C +GATTS:StartService,OK,A000
- - SSC SSC2 gatts -S -z load -p 0xA2
- - R SSC2 C +GATTS:StartService,OK,A002
- - SSC SSC2 bleadv -L -c 0 -t 3
- - R SSC2 C +BLEADV:SetAdv,OK
- - SSC SSC2 bleadv -D -z start
@ -1171,6 +1217,8 @@ initial condition:
- - R SSC[1-5] C +BLESMP:OK
- - SSC SSC1 gattc -F -r <dut2_bt_mac>
- - R SSC1 C +GATTC:OK
- - SSC SSC1 ram
- - R SSC1 A <heap_size>:(\d+)
restore post cmd set:
- ''
- - SSC SSC[1-5] ble -R
@ -1205,6 +1253,7 @@ initial condition:
initial condition detail: one target in AP mode and espnow is de-initialized
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC1 op -Q
- - R SSC1 C +CURMODE:2
- - SSC SSC1 mac -Q -o 2
@ -1239,6 +1288,7 @@ initial condition:
with self role slave
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC[1-<dev_num>] op -Q
- - R SSC[1-<dev_num>] C +CURMODE:2
- - SSC SSC[1-<dev_num>] mac -Q -o 3
@ -1422,6 +1472,7 @@ initial condition:
initial condition detail: testing sta on sta + ap mode, quit AP (autogen by STAM1)
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC1 op -Q
- - R SSC1 C +CURMODE:3
- - SSC SSC1 sta -D
@ -1458,6 +1509,7 @@ initial condition:
by STAM2)
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC1 op -Q
- - R SSC1 C +CURMODE:3
- - SSC SSC1 sta -Q
@ -1494,6 +1546,7 @@ initial condition:
condition STAAP1
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC1 op -Q
- - R SSC1 C +CURMODE:1
- - SSC SSC1 sta -D
@ -1530,6 +1583,7 @@ initial condition:
condition STAAP2
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC1 op -Q
- - R SSC1 C +CURMODE:1
- - SSC SSC1 sta -Q
@ -1566,6 +1620,7 @@ initial condition:
condition STAAP1
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC1 op -Q
- - R SSC1 C +CURMODE:1
- - SSC SSC1 sta -D
@ -1602,6 +1657,7 @@ initial condition:
initial condition STAAP2
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC1 op -Q
- - R SSC1 C +CURMODE:1
- - SSC SSC1 sta -Q
@ -1704,6 +1760,7 @@ initial condition:
T2_2
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC1 op -Q
- - R SSC1 C +CURMODE:2
- - SSC SSC2 op -Q
@ -1766,6 +1823,7 @@ initial condition:
with initial condition T2_2
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC1 op -Q
- - R SSC1 C +CURMODE:2
- - SSC SSC2 op -Q
@ -1827,6 +1885,7 @@ initial condition:
initial condition detail: target 1 as AP+STA, target 2 as AP+STA (autogen)
check cmd set:
- ''
- *dut1_start_wifi
- - SSC SSC1 op -Q
- - R SSC1 C +CURMODE:3
- - SSC SSC2 op -Q
@ -2049,209 +2108,44 @@ initial condition:
- - R SSC[1-2] C +BLEADV:OK
- - SSC SSC1 ram
- - R SSC1 A <heap_size>:(\d+)
- tag: ENABLED_1
<<: *MESH_INIT_COND
initial condition detail: if mesh tree not exist, start one node first, then start others, after mesh network
established, root connect server
- tag: T3_1
<<: *SSC_INIT_COND
initial condition detail: target 1 as SoftAP + STA, target 2 as SoftAP, target 3 as STA
with initial condition T2_2
check cmd set:
- ''
- - SSC SSC[1-<node_num>] mesh -Q -o 2
- - R SSC[1-<node_num>] T <node_num>
- - MESHTREE
- - R PC_COM RE "MESHTREE:%%s%20nodes"%%(<node_num>)
- - SOC SOC1 LISTEN <test_tcp_port1> <pc_ip>
- - R SOC_COM L OK
- - SSC MNODE(0) mesh -S -o 0 -i <pc_ip> -t <test_tcp_port1>
- - ''
- - SOC SOC1 MACCEPT GSOC1
- - P MNODE(0) C +CONNECT,OK
- R SOC_COM L OK
- - SSC SSC[1-<node_num>] mesh -F -o 4 -a 1
- - P SSC[1-<node_num>] C +MESHFLAG:OK
- - SSC SSC[1-<node_num>] mesh -F -o 5 -a 1
- - P SSC[1-<node_num>] C +MESHFLAG:OK
- *dut1_start_wifi
- - SSC SSC1 op -Q
- - R SSC1 C +CURMODE:3
- - SSC SSC2 op -Q
- - R SSC2 C +CURMODE:2
- - SSC SSC3 op -Q
- - R SSC3 C +CURMODE:1
- - SSC SSC3 sta -D
- - 'R SSC3 C +QAP:'
restore cmd set:
- ''
- - SSC SSC[1-<node_num>] reboot
- - P SSC[1-<node_num>] C !!!ready!!!
- - SSC SSC[1-<node_num>] mesh -I
- - P SSC[1-<node_num>] C +MESH:INITED
- - SSC SSC[1-<node_num>] mesh -A -o 12 -t <duration_ms> -c <cnx_rssi> -l <select_rssi> -f <switch_rssi> -b <backoff_rssi>
- - P SSC[1-<node_num>] C +MESH_SET_PARENT_SWITCH:OK
- - SSC SSC[1-<node_num>] mesh -A -o 9 -t <auth_mode> -s <map_password>
- - P SSC[1-<node_num>] C +MESH_SET_AP_AUTH_MODE:OK C +MESH_SET_AP_AUTH_PWD:OK
- - SSC SSC[1-<node_num>] mesh -P -g <mesh_id> -s <ap_ssid> -p <ap_password> -n
<ap_channel> -m <max_connect> -y <max_layer>
- - P SSC[1-<node_num>] C +MESH:CONFIG,OK
- - SSC SSC1 mesh -T
- - P SSC1 C +MESH:START,OK
- - DELAY 10
- - ''
- - SSC SSC[2-<node_num>] mesh -T
- - P SSC[2-<node_num>] C +MESH:START,OK
- - DELAY <delay_time>
- - ''
- - SSC SSC[1-<node_num>] mesh -Q -o 2
- - R SSC[1-<node_num>] T <node_num>
- - MESHTREE
- - R PC_COM RE "MESHTREE:%%s%20nodes"%%(<node_num>)
- - SSC MNODE(0) mesh -Q -o 1 -t <delay_time>
- - R MNODE(0) C NETWORK_TIME:PASS
- - SOC SOC1 LISTEN <test_tcp_port1> <pc_ip>
- - R SOC_COM L OK
- - SSC MNODE(0) mesh -S -o 0 -i <pc_ip> -t <test_tcp_port1>
- - ''
- - SOC SOC1 MACCEPT GSOC1
- - P MNODE(0) C +CONNECT,OK
- R SOC_COM L OK
- - SSC SSC[1-<node_num>] mesh -F -o 4 -a 1
- - P SSC[1-<node_num>] C +MESHFLAG:OK
- - SSC SSC[1-<node_num>] mesh -F -o 5 -a 1
- - P SSC[1-<node_num>] C +MESHFLAG:OK
- - SSC SSC1 op -S -o 3
- - R SSC1 C +MODE:OK
- - SSC SSC2 op -S -o 2
- - R SSC2 C +MODE:OK
- - SSC SSC3 op -S -o 1
- - R SSC3 C +MODE:OK
- - SSC SSC3 sta -D
- - 'R SSC3 C +QAP:'
force restore cmd set:
- ''
- - SSC SSC[1-<node_num>] restore
- - P SSC[1-<node_num>] C !!!ready!!!
- - SSC SSC[1-<node_num>] mesh -I
- - P SSC[1-<node_num>] C +MESH:INITED
- - SSC SSC[1-<node_num>] mesh -A -o 12 -t <duration_ms> -c <cnx_rssi> -l <select_rssi> -f <switch_rssi> -b <backoff_rssi>
- - P SSC[1-<node_num>] C +MESH_SET_PARENT_SWITCH:OK
- - SSC SSC[1-<node_num>] mesh -A -o 9 -t <auth_mode> -s <map_password>
- - P SSC[1-<node_num>] C +MESH_SET_AP_AUTH_MODE:OK C +MESH_SET_AP_AUTH_PWD:OK
- - SSC SSC[1-<node_num>] mesh -P -g <mesh_id> -s <ap_ssid> -p <ap_password> -n
<ap_channel> -m <max_connect> -y <max_layer>
- - P SSC[1-<node_num>] C +MESH:CONFIG,OK
- - SSC SSC1 mesh -T
- - P SSC1 C +MESH:START,OK
- - DELAY 10
- - ''
- - SSC SSC[2-<node_num>] mesh -T
- - P SSC[2-<node_num>] C +MESH:START,OK
- - DELAY <delay_time>
- - ''
- - SSC SSC[1-<node_num>] mesh -Q -o 2
- - R SSC[1-<node_num>] T <node_num>
- - MESHTREE
- - R PC_COM RE "MESHTREE:%%s%20nodes"%%(<node_num>)
- - SSC MNODE(0) mesh -Q -o 1 -t <delay_time>
- - R MNODE(0) C NETWORK_TIME:PASS
- - SOC SOC1 LISTEN <test_tcp_port1> <pc_ip>
- - R SOC_COM L OK
- - SSC MNODE(0) mesh -S -o 0 -i <pc_ip> -t <test_tcp_port1>
- - ''
- - SOC SOC1 MACCEPT GSOC1
- - P MNODE(0) C +CONNECT,OK
- R SOC_COM L OK
- - SSC SSC[1-<node_num>] mesh -F -o 4 -a 1
- - P SSC[1-<node_num>] C +MESHFLAG:OK
- - SSC SSC[1-<node_num>] mesh -F -o 5 -a 1
- - P SSC[1-<node_num>] C +MESHFLAG:OK
- tag: ENABLED_2
<<: *MESH_INIT_COND
initial condition detail: if mesh tree not exist, start all nodes together
check cmd set:
- ''
- - SSC SSC[1-<node_num>] mesh -Q -o 2
- - R SSC[1-<node_num>] T <node_num>
- - MESHTREE
- - R PC_COM RE "MESHTREE:%%s%20nodes"%%(<node_num>)
restore cmd set:
- ''
- - SSC SSC[1-<node_num>] reboot
- - P SSC[1-<node_num>] C !!!ready!!!
- - SSC SSC[1-<node_num>] mesh -I
- - P SSC[1-<node_num>] C +MESH:INITED
- - SSC SSC[1-<node_num>] mesh -A -o 12 -t <duration_ms> -c <cnx_rssi> -l <select_rssi> -f <switch_rssi> -b <backoff_rssi>
- - P SSC[1-<node_num>] C +MESH_SET_PARENT_SWITCH:OK
- - SSC SSC[1-<node_num>] mesh -A -o 9 -t <auth_mode> -s <map_password>
- - P SSC[1-<node_num>] C +MESH_SET_AP_AUTH_MODE:OK C +MESH_SET_AP_AUTH_PWD:OK
- - SSC SSC[1-<node_num>] mesh -P -g <mesh_id> -s <ap_ssid> -p <ap_password> -n
<ap_channel> -m <max_connect> -y <max_layer>
- - P SSC[1-<node_num>] C +MESH:CONFIG,OK
- - SSC SSC[1-<node_num>] mesh -T
- - P SSC[1-<node_num>] C +MESH:START,OK
- - DELAY <delay_time>
- - ''
- - SSC SSC[1-<node_num>] mesh -Q -o 2
- - R SSC[1-<node_num>] T <node_num>
- - MESHTREE
- - R PC_COM RE "MESHTREE:%%s%20nodes"%%(<node_num>)
- - SSC MNODE(0) mesh -Q -o 1 -t <delay_time>
- - R MNODE(0) C NETWORK_TIME:PASS
force restore cmd set:
- ''
- - SSC SSC[1-<node_num>] restore
- - P SSC[1-<node_num>] C !!!ready!!!
- - SSC SSC[1-<node_num>] mesh -I
- - P SSC[1-<node_num>] C +MESH:INITED
- - SSC SSC[1-<node_num>] mesh -A -o 12 -t <duration_ms> -c <cnx_rssi> -l <select_rssi> -f <switch_rssi> -b <backoff_rssi>
- - P SSC[1-<node_num>] C +MESH_SET_PARENT_SWITCH:OK
- - SSC SSC[1-<node_num>] mesh -A -o 9 -t <auth_mode> -s <map_password>
- - P SSC[1-<node_num>] C +MESH_SET_AP_AUTH_MODE:OK C +MESH_SET_AP_AUTH_PWD:OK
- - SSC SSC[1-<node_num>] mesh -P -g <mesh_id> -s <ap_ssid> -p <ap_password> -n
<ap_channel> -m <max_connect> -y <max_layer>
- - P SSC[1-<node_num>] C +MESH:CONFIG,OK
- - SSC SSC[1-<node_num>] mesh -T
- - P SSC[1-<node_num>] C +MESH:START,OK
- - DELAY <delay_time>
- - ''
- - SSC SSC[1-<node_num>] mesh -Q -o 2
- - R SSC[1-<node_num>] T <node_num>
- - MESHTREE
- - R PC_COM RE "MESHTREE:%%s%20nodes"%%(<node_num>)
- - SSC MNODE(0) mesh -Q -o 1 -t <delay_time>
- - R MNODE(0) C NETWORK_TIME:PASS
- tag: ENABLED_3
<<: *MESH_INIT_COND
initial condition detail: all mesh nodes in softap+sta mode, mesh configed but not started
check cmd set:
- ''
restore cmd set:
- ''
- - SSC SSC[1-<node_num>] reboot
- - P SSC[1-<node_num>] C !!!ready!!!
- - SSC SSC[1-<node_num>] mesh -I
- - P SSC[1-<node_num>] C +MESH:INITED
- - SSC SSC[1-<node_num>] mesh -A -o 12 -t <duration_ms> -c <cnx_rssi> -l <select_rssi> -f <switch_rssi> -b <backoff_rssi>
- - P SSC[1-<node_num>] C +MESH_SET_PARENT_SWITCH:OK
- - SSC SSC[1-<node_num>] mesh -A -o 9 -t <auth_mode> -s <map_password>
- - P SSC[1-<node_num>] C +MESH_SET_AP_AUTH_MODE:OK C +MESH_SET_AP_AUTH_PWD:OK
- - SSC SSC[1-<node_num>] mesh -P -g <mesh_id> -s <ap_ssid> -p <ap_password> -n
<ap_channel> -m <max_connect> -y <max_layer>
- - P SSC[1-<node_num>] C +MESH:CONFIG,OK
force restore cmd set:
- ''
- - SSC SSC[1-<node_num>] restore
- - P SSC[1-<node_num>] C !!!ready!!!
- - SSC SSC[1-<node_num>] mesh -I
- - P SSC[1-<node_num>] C +MESH:INITED
- - SSC SSC[1-<node_num>] mesh -A -o 12 -t <duration_ms> -c <cnx_rssi> -l <select_rssi> -f <switch_rssi> -b <backoff_rssi>
- - P SSC[1-<node_num>] C +MESH_SET_PARENT_SWITCH:OK
- - SSC SSC[1-<node_num>] mesh -A -o 9 -t <auth_mode> -s <map_password>
- - P SSC[1-<node_num>] C +MESH_SET_AP_AUTH_MODE:OK C +MESH_SET_AP_AUTH_PWD:OK
- - SSC SSC[1-<node_num>] mesh -P -g <mesh_id> -s <ap_ssid> -p <ap_password> -n
<ap_channel> -m <max_connect> -y <max_layer>
- - P SSC[1-<node_num>] C +MESH:CONFIG,OK
- tag: DISABLED_1
<<: *MESH_INIT_COND
initial condition detail: all mesh node in softap+sta mode, disable all mesh node
check cmd set:
- ''
- - ASSERT
- - ''
restore cmd set:
- ''
- - SSC SSC[1-<node_num>] reboot
- - P SSC[1-<node_num>] C !!!ready!!!
- - SSC SSC[1-<node_num>] op -Q
- - P SSC[1-<node_num>] C +CURMODE:3
- - SSC SSC[1-<node_num>] sta -D
- - P SSC[1-<node_num>] C +QAP:OK
force restore cmd set:
- ''
- - SSC SSC[1-<node_num>] restore
- - P SSC[1-<node_num>] C !!!ready!!!
- - SSC SSC[1-<node_num>] op -S -o 3
- - P SSC[1-<node_num>] C +MODE:OK
- - SSC SSC[1-<node_num>] sta -D
- - P SSC[1-<node_num>] C +QAP:OK
- - SSC SSC1 reboot
- - R SSC1 C !!!ready!!!
- - SSC SSC2 reboot
- - R SSC2 C !!!ready!!!
- - SSC SSC3 reboot
- - R SSC3 C !!!ready!!!
- - SSC SSC1 op -S -o 3
- - R SSC1 C +MODE:OK
- - SSC SSC2 op -S -o 2
- - R SSC2 C +MODE:OK
- - SSC SSC3 op -S -o 1
- - R SSC3 C +MODE:OK
- - SSC SSC3 sta -D
- - 'R SSC3 C +QAP:'

View file

@ -15,6 +15,8 @@ WIFI_CONN_1101
# Wifi scan issue
WIFI_SCAN_0303
WIFI_SCAN_0303_01
WIFI_CONN_0302
WIFI_CONN_0302_01
WIFI_CONN_0101
WIFI_CONN_0101_01
WIFI_CONN_0102
@ -56,10 +58,7 @@ BTSTK_SMP_05002
BTSTK_SMP_05003
BTSTK_SMP_06004
# GAP
BTSTK_GAP_03005
# GAP multi connect
# multi connect
BTSTK_GAP_10001
BTSTK_GAP_10002
BTSTK_GAP_10003
@ -83,4 +82,8 @@ BTSTK_GATT_33002
BTSTK_GATT_33003
BTSTK_GATT_34001
BTSTK_GATT_34002
BTSTK_GATT_34003
BTSTK_GATT_34003
# GATT read multiple
BTSTK_GATT_27002
BTSTK_GATT_27003

View file

@ -5,7 +5,7 @@
category: Function
test point 1: basic function
initial condition: BLE_INIT2
test environment: SSC_T2_1
test environment: SSC_T2_5
execution time: 0
module: BT Stack
sub module: GAP
@ -350,6 +350,53 @@ test cases:
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="ADV_IND")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.ManufacturerSpecificData="0x12345678")'
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="SCAN_RSP")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.ManufacturerSpecificData="0x12345678")'
- ID: BTSTK_GAP_02006
<<: *GAP_CASE
test point 2: BLE GAP config advertising data
summary: ble set advertising data / scan response manufacturer length not equal to real lenght
steps: |
1. DUT1 stop advertise and set short device name
2. DUT1 set manufacturer 0x12345678 and length 3 for adv data and scan response
3. DUT1 start advertising
4. PC do active scan and capture advertising report
5. DUT1 stop advertise and set short device name
6. DUT1 set manufacturer 0x12345678 and length 10 for adv data and scan response
7. DUT1 start advertising
8. PC do active scan and capture advertising report
expected result: |
1. succeed
2. succeed
3. succeed
4. get manufacturer data 0x12345678 in ADV_IND and SCAN_RSP
5. succeed
6. succeed
7. succeed
8. get manufacturer data 0x12345678 in ADV_IND and SCAN_RSP
initial condition: BLE_INIT1
test environment: SSC_T1_3
version: v2 (2016-03-01)
cmd set:
- ""
- *dut1_stop_adv
- *set_default_ble_name
- - "SSC SSC1 bleadv -L -c 0 -m 0x12345678 -t 3 -l 3"
- ["R SSC1 C +BLEADV:SetAdv,OK"]
- *dut1_start_adv
- *open_capture_nic
- - "HCITOOL 2 -i <hci_nic> lescan"
- - 'P PC_COM C +HCITOOL:OK'
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="ADV_IND")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.ManufacturerSpecificData="0x12345678")'
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="SCAN_RSP")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.ManufacturerSpecificData="0x12345678")'
- *dut1_stop_adv
- *set_default_ble_name
- - "SSC SSC1 bleadv -L -c 0 -m 0x12345678 -t 3 -l 10"
- ["R SSC1 C +BLEADV:SetAdv,OK"]
- *dut1_start_adv
- *open_capture_nic
- - "HCITOOL 2 -i <hci_nic> lescan"
- - 'P PC_COM C +HCITOOL:OK'
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="ADV_IND")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.ManufacturerSpecificData="0x12345678")'
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="SCAN_RSP")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.ManufacturerSpecificData="0x12345678")'
- ID: BTSTK_GAP_02007
<<: *GAP_CASE
test point 2: BLE GAP config advertising data
summary: ble set advertising data / scan response service data
@ -378,7 +425,54 @@ test cases:
- - 'P PC_COM C +HCITOOL:OK'
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="ADV_IND")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.ServiceData16BitUUID="1234123456")'
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="SCAN_RSP")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.ServiceData16BitUUID="1234123456")'
- ID: BTSTK_GAP_02007
- ID: BTSTK_GAP_02008
<<: *GAP_CASE
test point 2: BLE GAP config advertising data
summary: ble set advertising data / scan response service data and set length not equal to real length
steps: |
1. DUT1 stop advertise
2. DUT1 set advertising data and scan response service data 0x1234123456 and service data length 3
3. DUT1 start advertising
4. PC do active scan and capture advertising report
5. DUT1 stop advertise
6. DUT1 set advertising data and scan response service data 0x1234123456 and service data length 10
7. DUT1 start advertising
8. PC do active scan and capture advertising report
expected result: |
1. succeed
2. succeed
3. succeed
4. get ServiceData16BitUUID 0x1234123456 in ADV_IND and SCAN_RSP
5. succeed
6. succeed
7. succeed
8. get ServiceData16BitUUID 0x1234123456 in ADV_IND and SCAN_RSP
initial condition: BLE_INIT1
test environment: SSC_T1_3
version: v2 (2016-03-01)
cmd set:
- ""
- *dut1_stop_adv
- *set_default_ble_name
- - "SSC SSC1 bleadv -L -c 0 -n 0 -d 0x1234123456 -t 3 -l 3"
- ["R SSC1 C +BLEADV:SetAdv,OK"]
- *dut1_start_adv
- *open_capture_nic
- - "HCITOOL 2 -i <hci_nic> lescan"
- - 'P PC_COM C +HCITOOL:OK'
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="ADV_IND")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.ServiceData16BitUUID="1234123456")'
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="SCAN_RSP")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.ServiceData16BitUUID="1234123456")'
- *dut1_stop_adv
- *set_default_ble_name
- - "SSC SSC1 bleadv -L -c 0 -n 0 -d 0x1234123456 -t 3 -l 10"
- ["R SSC1 C +BLEADV:SetAdv,OK"]
- *dut1_start_adv
- *open_capture_nic
- - "HCITOOL 2 -i <hci_nic> lescan"
- - 'P PC_COM C +HCITOOL:OK'
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="ADV_IND")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.ServiceData16BitUUID="1234123456")'
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="SCAN_RSP")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.ServiceData16BitUUID="1234123456")'
- ID: BTSTK_GAP_02009
<<: *GAP_CASE
test point 2: BLE GAP config advertising data
summary: ble set advertising data / scan response service uuid list
@ -407,6 +501,53 @@ test cases:
- - 'P PC_COM C +HCITOOL:OK'
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="ADV_IND")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.Complete16BitServiceUUID="ABCD")(HCIEvent.data_0.Complete32BitServiceUUID="ABCDDCBA")(HCIEvent.data_0.Complete128BitServiceUUID="12349B5F8000008000100000ABCD0000")'
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="SCAN_RSP")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.Complete16BitServiceUUID="ABCD")(HCIEvent.data_0.Complete32BitServiceUUID="ABCDDCBA")(HCIEvent.data_0.Complete128BitServiceUUID="12349B5F8000008000100000ABCD0000")'
- ID: BTSTK_GAP_02010
<<: *GAP_CASE
test point 2: BLE GAP config advertising data
summary: ble set advertising data / scan response service uuid list and uuid length not equal to real length
steps: |
1. DUT1 stop advertise
2. DUT1 set advertising data and scan response not include name, service uuid list 0xABCD,ABCDDCBA,12349B5F8000008000100000ABCD0000 and service uuid len 32
3. DUT1 start advertising
4. PC do active scan and capture advertising report
5. DUT1 stop advertise
6. DUT1 set advertising data and scan response not include name, service uuid list 0xABCD,ABCDDCBA,12349B5F8000008000100000ABCD0000 and service uuid len 64
7. DUT1 start advertising
8. PC do active scan and capture advertising report
expected result: |
1. succeed
2. succeed
3. succeed
4. get Complete16BitServiceUUID 0xABCD Complete32BitServiceUUID 0xABCDDCBA
and Complete128BitServiceUUID 0x12349B5F8000008000100000ABCD0000 in ADV_IND and SCAN_RSP
5. succeed
6. succeed
7. succeed
8. get Complete16BitServiceUUID 0xABCD Complete32BitServiceUUID 0xABCDDCBA
and Complete128BitServiceUUID 0x12349B5F8000008000100000ABCD0000 in ADV_IND and SCAN_RSP
initial condition: BLE_INIT1
test environment: SSC_T1_3
version: v2 (2016-03-01)
cmd set:
- ""
- *dut1_stop_adv
- - "SSC SSC1 bleadv -L -c 0 -n 0 -x 0 -i 0x00-0x00 -s ABCD,ABCDDCBA,12349B5F8000008000100000ABCD0000 -t 3 -l 32"
- ["R SSC1 C +BLEADV:SetAdv,OK"]
- *dut1_start_adv
- *open_capture_nic
- - "HCITOOL 2 -i <hci_nic> lescan"
- - 'P PC_COM C +HCITOOL:OK'
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="ADV_IND")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.Complete16BitServiceUUID="ABCD")(HCIEvent.data_0.Complete32BitServiceUUID="ABCDDCBA")(HCIEvent.data_0.Complete128BitServiceUUID="12349B5F8000008000100000ABCD0000")'
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="SCAN_RSP")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.Complete16BitServiceUUID="ABCD")(HCIEvent.data_0.Complete32BitServiceUUID="ABCDDCBA")(HCIEvent.data_0.Complete128BitServiceUUID="12349B5F8000008000100000ABCD0000")'
- *dut1_stop_adv
- - "SSC SSC1 bleadv -L -c 0 -n 0 -x 0 -i 0x00-0x00 -s ABCD,ABCDDCBA,12349B5F8000008000100000ABCD0000 -t 3 -l 64"
- ["R SSC1 C +BLEADV:SetAdv,OK"]
- *dut1_start_adv
- *open_capture_nic
- - "HCITOOL 2 -i <hci_nic> lescan"
- - 'P PC_COM C +HCITOOL:OK'
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="ADV_IND")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.Complete16BitServiceUUID="ABCD")(HCIEvent.data_0.Complete32BitServiceUUID="ABCDDCBA")(HCIEvent.data_0.Complete128BitServiceUUID="12349B5F8000008000100000ABCD0000")'
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="SCAN_RSP")(HCIEvent.address_0=<dut1_bt_mac>)(HCIEvent.data_0.Complete16BitServiceUUID="ABCD")(HCIEvent.data_0.Complete32BitServiceUUID="ABCDDCBA")(HCIEvent.data_0.Complete128BitServiceUUID="12349B5F8000008000100000ABCD0000")'
- ID: BTSTK_GAP_03001
<<: *GAP_CASE
test point 2: BLE GAP set advertise param
@ -564,6 +705,7 @@ test cases:
- 'P BLENIC PDU (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.address_0{%s}<dut1_bt_mac>)'
- ID: BTSTK_GAP_03005
<<: *GAP_CASE
CI ready: "No"
test point 2: BLE GAP set advertise param
summary: ble set adv parameter adv interval
steps: |
@ -644,6 +786,156 @@ test cases:
- - "HCITOOL 2 -i <hci_nic> lescan"
- - 'P PC_COM C +HCITOOL:OK'
- 'P BLENIC {%s} (HCIEvent.le_sub_event_code="LEAdvReport")(HCIEvent.event_type_0="NONCONN_IND")(HCIEvent.address_0=<dut1_bt_mac>)'
- ID: BTSTK_GAP_03008
<<: *GAP_CASE
test point 2: BLE GAP set advertise param
summary: ble adv with random address and RPA_PUBLIC
initial condition: BLE_INIT_SMP
steps: |
1. DUT2 set random address
2. DUT2 adv with RPA_PUBLIC
3. DUT1 start scan
expected result: |
1. succeed
2. succeed
3. succeed
cmd set:
- ""
- - "SSC SSC2 bleadv -D -z stop"
- ["R SSC2 C +BLEADV:Stop,OK"]
- - "SSC SSC2 ble -S -z privacy -p 1"
- ["R SSC2 C +BLECONN:SetResAddr,Success"]
- - "SSC SSC2 bleadv -D -z start -t 0 -o 2"
- ["R SSC2 C +BLEADV:OK"]
- - "SSC SSC1 blescan -D -z start"
- ["R SSC1 P <dut2_bt_mac> C Complete"]
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK", "R SSC2 C +BLE:GattsConnect"]
- ID: BTSTK_GAP_03009
<<: *GAP_CASE
test point 2: BLE GAP set advertise param
summary: ble set adv owner address type as RPA_PUBLIC
initial condition: BLE_INIT_SMP
steps: |
1. DUT2 set owner address type as RPA_PUBLIC and start adv
2. DUT1 scan
3. exchange IRK and pairing
4. DUT2 set privacy
5. DUT2 set owner address type as RPA_PUBLIC and start adv
6. DUT1 scan
7. DUT1 connect to DUT2
expected result: |
1. succeed
2. succeed
3. succeed
4. succeed
5. succeed
6. succeed
7. succeed
cmd set:
- ""
- - "SSC SSC2 blesmp -S -z AuthReqMode -v 0x01"
- ['P SSC2 C +BLESMP:OK']
- - "SSC SSC2 blesmp -S -z IOCAP -v 0x03"
- ['P SSC2 C +BLESMP:OK']
- - "SSC SSC2 blesmp -S -z RspKey -v 0x03"
- ['P SSC2 C +BLESMP:OK']
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ['P SSC1 C +BLE:GattcConnect,OK', 'P SSC2 C +BLE:GattsConnect']
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['P SSC1 C +BLESMP:SecReq']
- - "SSC SSC1 blesmp -R -a 1 -r <dut2_bt_mac>"
- ['P SSC[1-2] C +BLESMP:AuthComplete,Success,0']
- - "SSC SSC1 bleconn -D -z all"
- ['P SSC1 C +BLE:GattcDisconnect,OK', 'P SSC2 C +BLE:GattsDisconnect,OK']
- - "SSC SSC2 ble -S -z privacy -p 1"
- ["R SSC2 C +BLECONN:SetResAddr,Success"]
- - "SSC SSC2 bleadv -D -z stop"
- ["R SSC2 C +BLEADV:OK"]
- - "SSC SSC2 bleadv -D -z start -o 2"
- ["R SSC2 C +BLEADV:OK"]
- - "SSC SSC1 blescan -D -z start"
- ["R SSC1 P <dut2_bt_mac> C Complete"]
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK", "R SSC2 C +BLE:GattsConnect"]
- ID: BTSTK_GAP_03010
<<: *GAP_CASE
CI ready: "No" # can't restore to use public address after set to use private address
test point 2: BLE GAP set advertise param
summary: ble adv with privacy address and RPA_RANDOM
initial condition: BLE_INIT_SMP
steps: |
1. DUT2 set random address
2. DUT2 adv with RPA_RANDOM
3. DUT1 start scan
expected result: |
1. succeed
2. succeed
3. succeed
cmd set:
- ""
- - "SSC SSC2 bleadv -D -z stop"
- ["R SSC2 C +BLEADV:Stop,OK"]
- - "SSC SSC2 ble -S -z privacy -p 1"
- ["R SSC2 C +BLECONN:SetResAddr,Success"]
- - "SSC SSC2 bleadv -D -z start -t 0 -o 3"
- ["R SSC2 C +BLEADV:OK"]
- - "SSC SSC1 blescan -D -z start"
- ["R SSC1 P <dut2_bt_mac> C Complete"]
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK", "R SSC2 C +BLE:GattsConnect"]
- ID: BTSTK_GAP_03011
<<: *GAP_CASE
CI ready: "No" # can't restore to use public address after set to use private address
test point 2: BLE GAP set advertise param
summary: ble set adv owner address type as RPA_RANDOM
initial condition: BLE_INIT_SMP
steps: |
1. DUT2 set owner address type as RPA_RANDOM and start adv
2. DUT2 set static random address
3. DUT2 set owner address type as RPA_RANDOM and start adv
4. DUT1 start scan
5. exchange IRK and do pairing
6. DUT2 set privacy
7. DUT2 set owner address type as RPA_RANDOM and start adv
8. DUT1 scan
9. DUT1 connect to DUT2
expected result: |
1. failed
2. succeed
3. succeed
4. succeed
5. succeed
6. succeed
7. succeed
8. succeed
9. succeed
cmd set:
- ""
- - "SSC SSC2 blesmp -S -z AuthReqMode -v 0x01"
- ['P SSC2 C +BLESMP:OK']
- - "SSC SSC2 blesmp -S -z IOCAP -v 0x03"
- ['P SSC2 C +BLESMP:OK']
- - "SSC SSC2 blesmp -S -z RspKey -v 0x03"
- ['P SSC2 C +BLESMP:OK']
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ['P SSC1 C +BLE:GattcConnect,OK', 'P SSC2 C +BLE:GattsConnect']
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['P SSC1 C +BLESMP:SecReq']
- - "SSC SSC1 blesmp -R -a 1 -r <dut2_bt_mac>"
- ['P SSC[1-2] C +BLESMP:AuthComplete,Success,0']
- - "SSC SSC1 bleconn -D -z all"
- ['P SSC1 C +BLE:GattcDisconnect,OK', 'P SSC2 C +BLE:GattsDisconnect,OK']
- - "SSC SSC2 ble -S -z privacy -p 1"
- ["R SSC2 C +BLECONN:SetResAddr,Success"]
- - "SSC SSC2 bleadv -D -z stop"
- ["R SSC2 C +BLEADV:OK"]
- - "SSC SSC2 bleadv -D -z start -o 3"
- ["R SSC2 C +BLEADV:OK"]
- - "SSC SSC1 blescan -D -z start"
- ["R SSC1 P <dut2_bt_mac> C Complete"]
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK", "R SSC2 C +BLE:GattsConnect"]
- ID: BTSTK_GAP_04001
<<: *GAP_CASE
test point 2: BLE GAP set scan param
@ -754,7 +1046,7 @@ test cases:
3. fail
4. fail
initial condition: BLE_INIT1
test environment: SSC_T1_1
test environment: SSC_T1_4
cmd set:
- ""
- - "SSC SSC1 blescan -L -c 0 -w 0x0004"
@ -784,7 +1076,6 @@ test cases:
5. succeed
6. DUT1 in scan result
initial condition: BLE_INIT2
test environment: SSC_T2_1
cmd set:
- ""
- *dut1_stop_adv
@ -812,7 +1103,7 @@ test cases:
2. succeed
3. failed
initial condition: BLE_INIT1
test environment: SSC_T1_1
test environment: SSC_T1_4
cmd set:
- ""
- - "SSC SSC1 blescan -L -c 0"
@ -881,7 +1172,7 @@ test cases:
<<: *GAP_CASE
allow fail: 1/2
test point 2: BLE GAP connect / disconnect
summary: ble connect/disconnect to same connection multiple times
summary: ble connect/disconnect to same connection multiple times
steps: |
1. DUT1 connect to DUT2 as "client"
2. DUT1 start gatt server app
@ -1674,7 +1965,7 @@ test cases:
2. fail
3. fail
initial condition: BLE_DEINIT1
test environment: SSC_T1_1
test environment: SSC_T1_4
cmd set:
- ""
- - "SSC SSC1 bleadv -L -c 0"
@ -1702,7 +1993,7 @@ test cases:
3. fail
4. fail
initial condition: BLE_DEINIT1
test environment: SSC_T1_1
test environment: SSC_T1_4
cmd set:
- ""
- - "SSC SSC1 bt -D -z init"
@ -1732,7 +2023,7 @@ test cases:
3. fail
4. fail
initial condition: BLE_DEINIT1
test environment: SSC_T1_1
test environment: SSC_T1_4
cmd set:
- ""
- - "SSC SSC1 bt -D -z start"
@ -1941,7 +2232,7 @@ test cases:
- ["R SSC1 C +BLEADV:SetAdv,OK"]
- *dut1_start_adv
- - "SSC SSC2 blescan -D -z start -t 1 -e 1"
- - 'P SSC2 RE "\+BTSCANEXT:%%s,txp,0xEB"%%(<dut1_bt_mac>)'
- - 'P SSC2 RE "\+BTSCANEXT:%%s,txp,0xEB"%%(<dut1_bt_mac>)'
- 'R SSC2 C Complete'
- *dut1_stop_adv
- - "SSC SSC1 bleadv -L -c 0 -x 0 -t 3"
@ -2111,6 +2402,150 @@ test cases:
- 'P SSC2 RE "\+BTSCANEXT:%%s,srv32,0xABCDDCBA"%%(<dut1_bt_mac>)'
- 'P SSC2 RE "\+BTSCANEXT:%%s,srv128,0x12349B5F8000008000100000ABCD0000"%%(<dut1_bt_mac>)'
- 'R SSC2 C Complete'
- ID: BTSTK_GAP_09012
<<: *GAP_CASE
test point 2: BLE GAP processing scan data
summary: adv include name and not set device name
steps: |
1. DUT1 stop advertise
2. DUT1 set advertising data and scan response include name
3. DUT1 start advertising
4. DUT2 start scan and processing scan data
expected result: |
1. succeed
2. succeed
3. succeed
4. failed
cmd set:
- ""
- *dut1_stop_adv
- - "SSC SSC1 bleadv -L -c 0 -n 1 -t 3"
- ["R SSC1 C +BLEADV:SetAdv,OK"]
- - "SSC SSC1 bleadv -D -z start"
- ["R SSC1 C +BLEADV:Start,OK"]
- - "SSC SSC2 blescan -D -z start"
- - 'P SSC2 RE "\+BTSCAN:INQ,%%s"%%(<dut1_bt_mac>)'
- 'R SSC2 C Complete'
- ID: BTSTK_GAP_09013
<<: *GAP_CASE
test point 2: BLE GAP processing scan data
summary: adv manufacturer_len not equal to real len
steps: |
1. DUT1 stop adv
2. DUT1 set manufacturer len shorter then real len
3. DUT1 start adv
4. DUT2 start scan
5. DUT1 stop adv
6. DUT1 set manufacturer len longer then real len
7. DUT1 start adv
8. DUT2 start scan
expected result: |
1. succeed
2. succeed
3. succeed
4. succeed
5. succeed
6. succeed
7. succeed
8. succeed
cmd set:
- ""
- *dut1_stop_adv
- - "SSC SSC1 bleadv -L -c 0 -m 0x12345678 -t 3 -l 6"
- ["R SSC1 C +BLEADV:SetAdv,OK"]
- *dut1_start_adv
- - "SSC SSC2 blescan -D -z start -e 1"
- - 'P SSC2 RE "\+BTSCANEXT:%%s,man,0x12345678"%%(<dut1_bt_mac>)'
- 'R SSC2 C Complete'
- *dut1_stop_adv
- - "SSC SSC1 bleadv -L -c 0 -m 0x12345678 -t 3 -l 10"
- ["R SSC1 C +BLEADV:SetAdv,OK"]
- *dut1_start_adv
- - "SSC SSC2 blescan -D -z start -e 1"
- - 'P SSC2 RE "\+BTSCANEXT:%%s,man,0x12345678"%%(<dut1_bt_mac>)'
- 'R SSC2 C Complete'
- ID: BTSTK_GAP_09014
<<: *GAP_CASE
test point 2: BLE GAP processing scan data
summary: set adv service data length not equal to real length
steps: |
1. DUT1 stop advertise
2. DUT1 set advertising data and scan response service data 0x1234123456 and set service data length 4
3. DUT1 start advertising
4. DUT2 start scan and processing scan data
5. DUT1 stop advertise
6. DUT1 set advertising data and scan response service data 0x1234123456 and set service data length 10
7. DUT1 start advertising
8. DUT2 start scan and processing scan data
expected result: |
1. succeed
2. succeed
3. succeed
4. scan with the correct adv data
5. succeed
6. succeed
7. succeed
8. scan with the correct adv data
cmd set:
- ""
- *dut1_stop_adv
- *set_default_ble_name
- - "SSC SSC1 bleadv -L -c 0 -n 0 -d 0x1234123456 -t 3 -l 4"
- ["R SSC1 C +BLEADV:SetAdv,OK"]
- *dut1_start_adv
- - "SSC SSC2 blescan -D -z start -t 1 -e 1"
- - 'P SSC2 RE "\+BTSCANEXT:%%s,srvdata,0x1234123456"%%(<dut1_bt_mac>)'
- 'R SSC2 C Complete'
- *dut1_stop_adv
- *set_default_ble_name
- - "SSC SSC1 bleadv -L -c 0 -n 0 -d 0x1234123456 -t 3 -l 10"
- ["R SSC1 C +BLEADV:SetAdv,OK"]
- *dut1_start_adv
- - "SSC SSC2 blescan -D -z start -t 1 -e 1"
- - 'P SSC2 RE "\+BTSCANEXT:%%s,srvdata,0x1234123456"%%(<dut1_bt_mac>)'
- 'R SSC2 C Complete'
- ID: BTSTK_GAP_09015
<<: *GAP_CASE
test point 2: BLE GAP processing scan data
summary: set service uuid length not equal to real length
steps: |
1. DUT1 stop advertise
2. DUT1 set advertising data and scan response not include name, service uuid list 0xABCD,ABCDDCBA,12349B5F8000008000100000ABCD0000 and set service uuid length 32
3. DUT1 start advertising
4. DUT2 start scan and processing scan data
5. DUT1 stop advertise
6. DUT1 set advertising data and scan response not include name, service uuid list 0xABCD,ABCDDCBA,12349B5F8000008000100000ABCD0000 and set service uuid length 64
7. DUT1 start advertising
8. DUT2 start scan and processing scan data
expected result: |
1. succeed
2. succeed
3. succeed
4. scan with the correct adv data
5. succeed
6. succeed
7. succeed
8. scan with the correct adv data
cmd set:
- ""
- *dut1_stop_adv
- - "SSC SSC1 bleadv -L -c 0 -n 0 -x 0 -i 0x00-0x00 -s ABCD,ABCDDCBA,12349B5F8000008000100000ABCD0000 -t 3 -l 32"
- ["R SSC1 C +BLEADV:SetAdv,OK"]
- *dut1_start_adv
- - "SSC SSC2 blescan -D -z start -t 1 -e 1"
- - 'P SSC2 RE "\+BTSCANEXT:%%s,srv16,0xABCD"%%(<dut1_bt_mac>)'
- 'P SSC2 RE "\+BTSCANEXT:%%s,srv32,0xABCDDCBA"%%(<dut1_bt_mac>)'
- 'P SSC2 RE "\+BTSCANEXT:%%s,srv128,0x12349B5F8000008000100000ABCD0000"%%(<dut1_bt_mac>)'
- 'R SSC2 C Complete'
- *dut1_stop_adv
- - "SSC SSC1 bleadv -L -c 0 -n 0 -x 0 -i 0x00-0x00 -s ABCD,ABCDDCBA,12349B5F8000008000100000ABCD0000 -t 3 -l 64"
- ["R SSC1 C +BLEADV:SetAdv,OK"]
- *dut1_start_adv
- - "SSC SSC2 blescan -D -z start -t 1 -e 1"
- - 'P SSC2 RE "\+BTSCANEXT:%%s,srv16,0xABCD"%%(<dut1_bt_mac>)'
- 'P SSC2 RE "\+BTSCANEXT:%%s,srv32,0xABCDDCBA"%%(<dut1_bt_mac>)'
- 'P SSC2 RE "\+BTSCANEXT:%%s,srv128,0x12349B5F8000008000100000ABCD0000"%%(<dut1_bt_mac>)'
- 'R SSC2 C Complete'
- ID: BTSTK_GAP_10001
<<: *GAP_CASE
test point 2: BLE GAP master multi connection test
@ -2341,6 +2776,7 @@ test cases:
- ["P SSC1 C Disconnect"]
- ID: BTSTK_GAP_40001
<<: *GAP_CASE
auto test: 'No'
test point 2: test if BLE work after switch off some sub modules
summary: GAP only test
steps: |
@ -2404,6 +2840,42 @@ test cases:
- ""
- - "fail_timeout = 10"
- ""
- ID: BTSTK_GAP_50004
<<: *GAP_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE GAP performance test
summary: BLE Connect and disconnect correct performance test
steps: |
1. DUT1 disconnect with DUT2
2. DUT2 start advertising
3. DUT1 connect to DUT2
4. loop step 1-4 1000 times
5. reboot
6. loop step 1-5
expected result: |
1. succeed
2. succeed
3. succeed
4. succeed
5. succeed
6. meet pass standard
initial condition: BLE_INIT2
execution time: 6
version: v1 (2017-05-19)
CI ready: 'No'
cmd set:
- "BLEStress/BLEConnCorPerformance"
- - "test_time = 100"
- ""
- - "reboot_time = 1000"
- ""
- - "average_conn_time = 3"
- ""
- - "fail_ratio = 0.01"
- ""
- - "fail_timeout = 10"
- ""
- ID: BTSTK_GAP_51001
<<: *GAP_CASE
category: Performance
@ -2512,7 +2984,7 @@ test cases:
- ["R SSC2 C +BLEADV:OK"]
- - "SSC SSC1 blescan -D -z start"
- ['R SSC1 P <static_device_addr> C Complete']
- - "SSC SSC1 bleconn -C -p 0x10 -a <static_device_addr>"
- - "SSC SSC1 bleconn -C -p 0x10 -a <static_device_addr> -r 1"
- ["P SSC1 C +BLE:GattcConnect,OK", "P SSC2 C +BLE:GattsConnect"]
- ID: BTSTK_GAP_14002
<<: *GAP_CASE
@ -2604,19 +3076,21 @@ test cases:
- ID: BTSTK_GAP_14008
<<: *GAP_CASE
test point 2: BLE set random address test
summary: disconnect after encryption and set random address as resolvable private address and reconnect
summary: BLE set random address as resolvable private address and reconnect after disconnect
steps: |
1. SSC2 set AuthReqMode and IOCAP,set RspKey as Enc and IRK
2. pairing
3. SSC1 disconnect to SSC2
4. SSC2 do local privacy
5. SSC2 bleadv and SSC1 blescan
6. SSC1 connect to SSC2
expected result: |
1. succeed
2. succeed
3. succeed
4. succeed
5. succeed
6. succeed
initial condition: BLE_INIT_SMP
cmd set:
- ""
@ -2636,34 +3110,30 @@ test cases:
- ['P SSC1 C +BLE:GattcDisconnect,OK', 'P SSC2 C +BLE:GattsDisconnect,OK']
- - "SSC SSC2 ble -S -z privacy -p 1"
- ["R SSC2 C +BLECONN:SetResAddr,Success"]
- - "SSC SSC2 bleadv -D -z stop"
- ["R SSC2 C +BLEADV:OK"]
- - "SSC SSC2 bleadv -L -c 0 -t 3"
- ["R SSC2 C +BLEADV:SetAdv,OK C +BLEADV:SetScanRes,OK"]
- - "SSC SSC2 bleadv -D -z start -o 1"
- ["R SSC2 C +BLEADV:OK"]
- - "SSC SSC1 blescan -D -z stop"
- ["R SSC1 C +BLESCAN:OK"]
- - "SSC SSC1 blescan -L -c 0"
- ["R SSC1 C +BLESCAN:SetScanParam,OK"]
- - "SSC SSC1 blescan -D -z start -t 3"
- ["R SSC1 P <dut2_bt_mac>"]
- ["R SSC1 P <dut2_bt_mac> C InquiryComplete"]
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK", "R SSC2 C +BLE:GattsConnect"]
- ID: BTSTK_GAP_14009
<<: *GAP_CASE
test point 2: BLE set random address test
summary: reboot after BLE DUT encryption and set random address as resolvable private address
summary: BLE set random address as resolvable private address and reconnect after reboot
steps: |
1. SSC2 set AuthReqMode and IOCAP,set RspKey as Enc and IRK
2. pairing
3. SSC1 and SSC2 reboot
4. SSC2 do local privacy
5. SSC2 bleadv and SSC1 blescan
6. SSC1 connect to SSC2
expected result: |
1. succeed
2. succeed
3. succeed
4. succeed
5. succeed
6. succeed
initial condition: BLE_INIT_SMP
allow fail: 2/3
cmd set:
@ -2684,6 +3154,8 @@ test cases:
- ['R SSC[1-2] C !!!ready!!!']
- - "SSC SSC[1-2] ble -R"
- ["R SSC[1-2] C +BLE:OK"]
- - "SSC SSC2 gatts -S -z load -p 0xA0"
- ['R SSC2 C +GATTS:LoadProfile,OK']
- - "SSC SSC2 ble -S -z privacy -p 1"
- ["R SSC2 C +BLECONN:SetResAddr,Success"]
- - "SSC SSC2 bleadv -D -z stop"
@ -2697,7 +3169,9 @@ test cases:
- - "SSC SSC1 blescan -L -c 0"
- ["R SSC1 C +BLESCAN:SetScanParam,OK"]
- - "SSC SSC1 blescan -D -z start -t 3"
- ["R SSC1 P <dut2_bt_mac>"]
- ["R SSC1 P <dut2_bt_mac> C InquiryComplete"]
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK", "R SSC2 C +BLE:GattsConnect"]
- ID: BTSTK_GAP_15001
<<: *GAP_CASE
test point 2: BLE GAP white list test
@ -2714,7 +3188,7 @@ test cases:
4. succeed
initial condition: BLE_INIT_REBOOT2
cmd set:
- ""
- ""
- - "SSC SSC1 ble -W -z get"
- ['P SSC1 C +BLE:GetWhiteList,OK,12']
- - "SSC SSC1 ble -W -a <dut2_bt_mac> -z add"

View file

@ -5,7 +5,7 @@
category: Function
test point 1: basic function
initial condition: BLE_CONN2
test environment: SSC_T2_1
test environment: SSC_T2_5
execution time: 0
module: BT Stack
sub module: GATT
@ -19,14 +19,47 @@
- - "SSC SSC1 gattc -D -z primaryService -p 0x10"
- ["R SSC1 C +GATTC:Discover,OK"]
.included_service_connection: &included_service_connection
.included_service_connection: &included_primary_service_connection
LIST_MERGE:
- - "SSC SSC2 gatts -S -z load -p 0xA1"
- ["R SSC2 C +GATTS:StartService,OK,A001"]
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK,0010", "R SSC2 C +BLE:GattsConnect"]
- ["R SSC2 C +GATTS:LoadProfile,OK,A001", "R SSC2 C +GATTS:StartService,OK,A001"]
- - "SSC SSC2 gatts -S -z include -p 0xA1 -i 0xA0"
- ["R SSC2 C +GATTS:AddIncludedService,OK"]
- - SSC SSC1 gattc -F -r <dut2_bt_mac>
- ['R SSC1 C +GATTC:OK']
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK,0010", "R SSC2 C +BLE:GattsConnect"]
.included_second_service_connection: &included_second_service_connection
LIST_MERGE:
- - "SSC SSC2 gatts -S -z load -p 0xA4"
- ["R SSC2 C +GATTS:StartService,OK,A004"]
- - "SSC SSC2 gatts -S -z load -p 0xA1"
- ["R SSC2 C +GATTS:LoadProfile,OK,A001", "R SSC2 C +GATTS:StartService,OK,A001"]
- - "SSC SSC2 gatts -S -z include -p 0xA1 -i 0xA4"
- ["R SSC2 C +GATTS:AddIncludedService,OK"]
- - SSC SSC1 gattc -F -r <dut2_bt_mac>
- ['R SSC1 C +GATTC:OK']
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK,0010", "R SSC2 C +BLE:GattsConnect"]
.table_include_table_service: &table_include_table_service
LIST_MERGE:
- - "SSC SSC2 gatts -S -z load -p 0xA5 -i 0xA2"
- ["R SSC2 C +GATTS:StartService,OK,A005"]
- - SSC SSC1 gattc -F -r <dut2_bt_mac>
- ['R SSC1 C +GATTC:OK']
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK,0010", "R SSC2 C +BLE:GattsConnect"]
.table_include_service: &table_include_service
LIST_MERGE:
- - "SSC SSC2 gatts -S -z load -p 0xA5 -i 0xA0"
- ["R SSC2 C +GATTS:StartService,OK,A005"]
- - SSC SSC1 gattc -F -r <dut2_bt_mac>
- ['R SSC1 C +GATTC:OK']
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK,0010", "R SSC2 C +BLE:GattsConnect"]
.register_notify_c107: &register_notify_c107
LIST_MERGE:
@ -47,7 +80,7 @@ test cases:
expected result: |
1. succeed
initial condition: BLE_INIT1
test environment: SSC_T1_1
test environment: SSC_T1_4
cmd set:
- ""
- - "SSC SSC1 gatts -S -z load -p 0xA0"
@ -63,7 +96,7 @@ test cases:
1. succeed
2. succeed
initial condition: BLE_INIT1
test environment: SSC_T1_1
test environment: SSC_T1_4
cmd set:
- ""
- - "SSC SSC1 gatts -S -z load -p 0xA0"
@ -73,7 +106,7 @@ test cases:
- ID: BTSTK_GATT_20001
<<: *GATT_CASE
test point 2: BLE GATT client service / char discovery
summary: GATT client discover primary service
summary: GATT client discover manual primary service
steps: |
1. DUT2 create preset service 0xA000
2. DUT2 create preset service 0xA001
@ -87,14 +120,13 @@ test cases:
initial condition: BLE_INIT2
cmd set:
- ""
- *included_service_connection
- *included_primary_service_connection
- - "SSC SSC1 gattc -D -z primaryService -p 0x10"
- ["R SSC1 C +GATTC:DiscoverService,A000 C +GATTC:DiscoverService,A001"]
- ID: BTSTK_GATT_20002
<<: *GATT_CASE
test point 2: BLE GATT client service / char discovery
summary: GATT client get included service
allow fail: 1/2
summary: GATT client get manual included service
steps: |
1. DUT2 create preset service 0xA000
2. DUT2 create preset service 0xA001
@ -110,11 +142,99 @@ test cases:
initial condition: BLE_INIT2
cmd set:
- ""
- *included_service_connection
- *included_primary_service_connection
- - "SSC SSC1 gattc -D -z primaryService -p 0x10"
- ["R SSC1 C +GATTC:DiscoverService,A000 A <handle_range>:GATTC:DiscoverService,A001,(\\d+-\\d+)"]
- - "SSC SSC1 gattc -D -z includedService -p 0x10 -s 0xA001 -i 0xA000 -q <handle_range> -k 1"
- ["R SSC1 C +GATTC:IncludedService,0010,A001,A000"]
- ID: BTSTK_GATT_20003
<<: *GATT_CASE
test point 2: BLE GATT client service / char discovery
summary: GATT client discover table primary service (table service include table service)
steps: |
1. DUT2 create preset service 0xA002
2. DUT2 create preset service 0xA005
3. DUT1 connect to DUT2
4. DUT1 do primary service discovery
expected result: |
1. succeed
2. succeed
3. succeed
4. found service 0xA002 and 0xA005
initial condition: BLE_INIT3
cmd set:
- ""
- *table_include_table_service
- - "SSC SSC1 gattc -D -z primaryService -p 0x10"
- ["R SSC1 C +GATTC:DiscoverService,A002 C +GATTC:DiscoverService,A005"]
- ID: BTSTK_GATT_20004
<<: *GATT_CASE
test point 2: BLE GATT client service / char discovery
summary: GATT client get table included service
steps: |
1. DUT2 create preset service 0xA002
2. DUT2 create preset service 0xA005
3. DUT1 connect to DUT2
4. DUT1 do primary service discovery
5. DUT1 get included service 0xA002 from service 0xA005
expected result: |
1. succeed
2. succeed
3. succeed
4. succeed
5. get included service 0xA002 from service 0xA005
initial condition: BLE_INIT3
cmd set:
- ""
- *table_include_table_service
- - "SSC SSC1 gattc -D -z primaryService -p 0x10"
- ["R SSC1 C +GATTC:DiscoverService,A002 A <handle_range>:GATTC:DiscoverService,A005,(\\d+-\\d+)"]
- - "SSC SSC1 gattc -D -z includedService -p 0x10 -s 0xA005 -i 0xA002 -q <handle_range> -k 1"
- ["R SSC1 C +GATTC:IncludedService,0010,A005,A002"]
- ID: BTSTK_GATT_20005
<<: *GATT_CASE
test point 2: BLE GATT client service / char discovery
summary: GATT client discover table primary service (table service include manual service)
steps: |
1. DUT2 create preset service 0xA000
2. DUT2 create preset service 0xA005
3. DUT1 connect to DUT2
4. DUT1 do primary service discovery
expected result: |
1. succeed
2. succeed
3. succeed
4. found service 0xA000 and 0xA005
initial condition: BLE_INIT2
cmd set:
- ""
- *table_include_service
- - "SSC SSC1 gattc -D -z primaryService -p 0x10"
- ["R SSC1 C +GATTC:DiscoverService,A000 C +GATTC:DiscoverService,A005"]
- ID: BTSTK_GATT_20006
<<: *GATT_CASE
test point 2: BLE GATT client service / char discovery
summary: GATT client get table included manual service
steps: |
1. DUT2 create preset service 0xA000
2. DUT2 create preset service 0xA005
3. DUT1 connect to DUT2
4. DUT1 do primary service discovery
5. DUT1 get included service 0xA000 from service 0xA005
expected result: |
1. succeed
2. succeed
3. succeed
4. succeed
5. get included service 0xA000 from service 0xA005
initial condition: BLE_INIT2
cmd set:
- ""
- *table_include_service
- - "SSC SSC1 gattc -D -z primaryService -p 0x10"
- ["R SSC1 C +GATTC:DiscoverService,A000 A <handle_range>:GATTC:DiscoverService,A005,(\\d+-\\d+)"]
- - "SSC SSC1 gattc -D -z includedService -p 0x10 -s 0xA005 -i 0xA000 -q <handle_range> -k 1"
- ["R SSC1 C +GATTC:IncludedService,0010,A005,A000"]
- ID: BTSTK_GATT_60001
<<: *GATT_CASE
test point 2: BLE GATT server get and set value
@ -594,10 +714,10 @@ test cases:
- ""
- - "SSC SSC2 gatts -S -z load -p 0xA1"
- ["R SSC2 C +GATTS:StartService,OK,A001"]
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK,0010", "R SSC2 C +BLE:GattsConnect"]
- - SSC SSC1 gattc -F -r <dut2_bt_mac>
- ['R SSC1 C +GATTC:OK']
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK,0010", "R SSC2 C +BLE:GattsConnect"]
- *primary_service_discovery
- - "SSC SSC1 gattc -R -z char -s 0xA000 -c 0xC100 -p 0x10"
- ["R SSC1 C +GATTC:ReadOnce,0010,A000,C100,1", "R SSC1 C +GATTC:Read,OK,0010,A000,C100"]
@ -623,10 +743,10 @@ test cases:
- ""
- - "SSC SSC2 gatts -S -z load -p 0xA1"
- ["R SSC2 C +GATTS:StartService,OK,A001"]
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK,0010", "R SSC2 C +BLE:GattsConnect"]
- - SSC SSC1 gattc -F -r <dut2_bt_mac>
- ['R SSC1 C +GATTC:OK']
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK,0010", "R SSC2 C +BLE:GattsConnect"]
- *primary_service_discovery
- - "SSC SSC1 gattc -R -z descriptor -s 0xA000 -c 0xC107 -d 0x2902 -p 0x10"
- ["R SSC1 C +GATTC:ReadOnce,0010,A000,C107,2902,2", "R SSC1 C +GATTC:ReadDescriptor,OK,0010,A000,C107,2902"]
@ -889,10 +1009,10 @@ test cases:
- ""
- - "SSC SSC2 gatts -S -z load -p 0xA1"
- ["R SSC2 C +GATTS:StartService,OK,A001"]
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK,0010", "R SSC2 C +BLE:GattsConnect"]
- - SSC SSC1 gattc -F -r <dut2_bt_mac>
- ['R SSC1 C +GATTC:OK']
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK,0010", "R SSC2 C +BLE:GattsConnect"]
- *primary_service_discovery
- - "SSC SSC1 gattc -W -z char -s 0xA000 -c 0xC102 -p 0x10 -v 0x01"
- ["R SSC1 C +GATTC:WriteOnce,0010,A000,C102", "R SSC1 C +GATTC:Write,OK,0010,A000,C102"]
@ -917,10 +1037,10 @@ test cases:
- ""
- - "SSC SSC2 gatts -S -z load -p 0xA1"
- ["R SSC2 C +GATTS:StartService,OK,A001"]
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK,0010", "R SSC2 C +BLE:GattsConnect"]
- - SSC SSC1 gattc -F -r <dut2_bt_mac>
- ['R SSC1 C +GATTC:OK']
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ["R SSC1 C +BLE:GattcConnect,OK,0010", "R SSC2 C +BLE:GattsConnect"]
- *primary_service_discovery
- - "SSC SSC1 gattc -W -z descriptor -s 0xA000 -c 0xC107 -d 0x2902 -p 0x10 -v 0x0100"
- ["R SSC1 C +GATTC:WriteOnce,0010,A000,C107,2902", "R SSC1 C +GATTC:WriteDescriptor,OK,0010,A000,C107,2902"]
@ -1217,7 +1337,7 @@ test cases:
- ID: BTSTK_GATT_23004
<<: *GATT_CASE
test point 2: BLE GATT client receive notify and indication
summary: GATT client can't receive notification/indication without write to CCC
summary: GATT client can't receive notification/indication without write to CCC (manual service)
steps: |
1. DUT1 do service discovery
2. DUT1 register notify on notify and inidcation char
@ -1284,7 +1404,7 @@ test cases:
- ID: BTSTK_GATT_23007
<<: *GATT_CASE
test point 2: BLE GATT client receive notify and indication
summary: GATT client can't receive notification/indication without write to CCC
summary: GATT client can't receive notification/indication without write to CCC (auto service auto reply)
steps: |
1. DUT1 do service discovery
2. DUT1 register notify on notify and inidcation char
@ -1352,7 +1472,7 @@ test cases:
- ID: BTSTK_GATT_23010
<<: *GATT_CASE
test point 2: BLE GATT client receive notify and indication
summary: GATT client can't receive notification/indication without write to CCC
summary: GATT client can't receive notification/indication without write to CCC (auto service manual reply)
steps: |
1. DUT1 do service discovery
2. DUT1 register notify on notify and inidcation char
@ -1685,9 +1805,9 @@ test cases:
cmd set:
- ""
- *primary_service_discovery
- - "SSC SSC1 gattc -W -z char -s 0xA002 -c 0xC302 -p 0x10 -v 0x01 -w 1"
- - "SSC SSC1 gattc -W -z char -s 0xA002 -c 0xC302 -p 0x10 -v -x01 -w 1"
- ["R SSC1 C +GATTC:Write,OK"]
- - "SSC SSC1 gattc -W -z char -s 0xA002 -c 0xC302 -p 0x10 -v 0x01 -w 1"
- - "SSC SSC1 gattc -W -z char -s 0xA002 -c 0xC302 -p 0x10 -v -x01 -w 1"
- ["R SSC1 C +GATTC:Write,OK"]
- ID: BTSTK_GATT_25015
<<: *GATT_CASE
@ -1880,6 +2000,61 @@ test cases:
- ["R SSC1 C +GATTC:WriteOnce,0010,A000,C109"]
- - "SSC SSC1 gattc -W -z char -p 0x10 -s 0xA000 -c 0xC109 -l 512"
- ["R SSC1 C +GATTC:WriteOnce,0010,A000,C109"]
- ID: BTSTK_GATT_27001
<<: *GATT_CASE
test point 2: BLE GATT read multiple
summary: GATT client read 2 char and 11 char of same service
steps: |
1. DUT1 do discover
2. GATT client read 2 char
3. GATT client read 11 char
expected result: |
1. succeed
2. succeed
3. succeed
cmd set:
- ""
- *primary_service_discovery
- - "SSC SSC1 gattc -R -z multiple -u #0xC100##0xC101# -s 0xA000"
- ['R SSC1 C +GATTC:ReadOnce,22', 'R SSC1 C +GATTC:ReadMultiple,OK']
- - "SSC SSC1 gattc -R -z multiple -u #0xC100##0xC101##0xC107##0xC108##0xC109##0xC110##0xC100##0xC101##0xC107##0xC108##0xC109# -s 0xA000"
- ['R SSC1 C +GATTC:Read,ERROR']
- ID: BTSTK_GATT_27002
<<: *GATT_CASE
test point 2: BLE GATT read multiple
summary: GATT client read char and descriptor
steps: |
1. DUT1 do discover
2. GATT client read all char and descriptor
expected result: |
1. succeed
2. succeed
cmd set:
- ""
- *primary_service_discovery
- - "SSC SSC1 gattc -R -z multiple -u 0xA00xC100#0xA00xC101#0xA00xC1000x29010xA00xC1070x2902"
- ['R SSC1 C +GATTC:ReadOnce', 'R SSC1 C +GATTC:ReadMultiple,OK']
- ID: BTSTK_GATT_27003
<<: *GATT_CASE
test point 2: BLE GATT read multiple
summary: GATT client read char and descriptor of included service and table service
initial condition: BLE_INIT2
steps: |
1. DUT2 load service included service and table service
2. DUT1 search service
3. GATT client read all char and descriptor of different services
expected result: |
1. succeed
2. succeed
3. succeed
cmd set:
- ""
- - "SSC SSC2 gatts -S -z load -p 0xA2"
- ['R SSC2 C +GATTS:StartService,OK,A002']
- *included_primary_service_connection
- *primary_service_discovery
- - "SSC SSC1 gattc -R -z multiple -u 0xA10xC200#0xA00xC100#0xA00xC101#0xA20xC300#0xA20xC301#"
- ['R SSC1 C +GATTC:ReadOnce', 'R SSC1 C +GATTC:ReadMultiple,OK']
- ID: BTSTK_GATT_30001
<<: *GATT_CASE
test point 2: BLE GATT multi connection service discovery test
@ -2071,7 +2246,7 @@ test cases:
- ID: BTSTK_GATT_32002
<<: *GATT_CASE
test point 2: BLE GATT multi connection write test
summary: do read when DUT1 is slave, connected by 4 masters
summary: do write when DUT1 is slave, connected by 4 masters
steps: |
1. do primary service discovery on DUT[2-5]
expected result: |
@ -2121,7 +2296,7 @@ test cases:
- ID: BTSTK_GATT_32004
<<: *GATT_CASE
test point 2: BLE GATT multi connection write test
summary: do read when master and slave both create GATTC and GATTS
summary: do write when master and slave both create GATTC and GATTS
steps: |
1. DUT1 do primary service discovery for DUT2
2. DUT2 do primary service discovery for DUT1
@ -2230,7 +2405,7 @@ test cases:
- ID: BTSTK_GATT_33004
<<: *GATT_CASE
test point 2: BLE GATT multi connection notify test
summary: do read when master and slave both create GATTC and GATTS
summary: do notify when master and slave both create GATTC and GATTS
steps: |
1. DUT1 do primary service discovery for DUT2
2. DUT2 do primary service discovery for DUT1
@ -2253,7 +2428,7 @@ test cases:
- ID: BTSTK_GATT_34001
<<: *GATT_CASE
test point 2: BLE GATT multi connection indicate test
summary: do notify when DUT1 role is master, connected with 4 slaves
summary: do indicate when DUT1 role is master, connected with 4 slaves
steps: |
1. do primary service discovery
2. do register indication for char
@ -2277,7 +2452,7 @@ test cases:
- ID: BTSTK_GATT_34002
<<: *GATT_CASE
test point 2: BLE GATT multi connection indicate test
summary: do notify when DUT1 is slave, connected by 4 masters
summary: do indicate when DUT1 is slave, connected by 4 masters
steps: |
1. do primary service discovery on DUT[2-5]
2. DUT[2-5] do register indication
@ -2301,7 +2476,7 @@ test cases:
- ID: BTSTK_GATT_34003
<<: *GATT_CASE
test point 2: BLE GATT multi connection indicate test
summary: do notify when DUT1 connect to DUT[2-3] and connected by DUT[4-5]
summary: do indicate when DUT1 connect to DUT[2-3] and connected by DUT[4-5]
steps: |
1. DUT1 do primary service discovery for DUT[2-3]
2. DUT1 register indication
@ -2339,7 +2514,7 @@ test cases:
- ID: BTSTK_GATT_34004
<<: *GATT_CASE
test point 2: BLE GATT multi connection indicate test
summary: do read when master and slave both create GATTC and GATTS
summary: do indicate when master and slave both create GATTC and GATTS
steps: |
1. DUT1 do primary service discovery for DUT2
2. DUT2 do primary service discovery for DUT1
@ -2533,7 +2708,7 @@ test cases:
- ""
- - gatt_op = "write"
- ""
- - op_char = "0xC304"
- - op_char = "0xC317"
- ""
- - op_len = 490
- ""
@ -2564,7 +2739,7 @@ test cases:
- ""
- - op_char = "0xC305"
- ""
- - op_len = 256
- - op_len = 490
- ""
- ID: BTSTK_GATT_50004
<<: *GATT_CASE
@ -2595,3 +2770,267 @@ test cases:
- ""
- - op_len = 256
- ""
- ID: BTSTK_GATT_50005
<<: *GATT_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE GATT performance test
summary: GATT master connect 4 slave and read char performance test
initial condition: BLE_CONN5
test environment: SSC_T5_1
steps: |
1. update connection parameter
2. do primary service discovery
3. do write char for some time
expected result: |
1. succeed
2. succeed
3. calculate throughput
execution time: 2
cmd set:
- "BLEStress/BLEMultiPerformance"
- - test_time = 120
- ""
- - mtu = 512
- ""
- - gatt_op = "read"
- ""
- - op_char = "0xC301"
- ""
- - op_len = 256
- ""
- - master_duts = ["SSC1"]
- ""
- - slave_duts = ["SSC2", "SSC3", "SSC4", "SSC5"]
- ""
- ID: BTSTK_GATT_50006
<<: *GATT_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE GATT performance test
summary: GATT 4 master connect 1 slave and read char performance test
initial condition: BLE_CONN6
test environment: SSC_T5_1
steps: |
1. update connection parameter
2. do primary service discovery
3. do write char for some time
expected result: |
1. succeed
2. succeed
3. calculate throughput
execution time: 2
cmd set:
- "BLEStress/BLEMultiPerformance"
- - test_time = 120
- ""
- - mtu = 512
- ""
- - gatt_op = "read"
- ""
- - op_char = "0xC301"
- ""
- - op_len = 256
- ""
- - master_duts = ["SSC2", "SSC3", "SSC4", "SSC5"]
- ""
- - slave_duts = ["SSC1"]
- ""
- ID: BTSTK_GATT_50007
<<: *GATT_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE GATT performance test
summary: GATT master connect 4 slave and write char performance test
initial condition: BLE_CONN5
test environment: SSC_T5_1
steps: |
1. update connection parameter
2. do primary service discovery
3. do write char for some time
expected result: |
1. succeed
2. succeed
3. calculate throughput
execution time: 2
cmd set:
- "BLEStress/BLEMultiPerformance"
- - test_time = 120
- ""
- - mtu = 512
- ""
- - gatt_op = "write"
- ""
- - op_char = "0xC304"
- ""
- - op_len = 256
- ""
- - master_duts = ["SSC1"]
- ""
- - slave_duts = ["SSC2", "SSC3", "SSC4", "SSC5"]
- ""
- ID: BTSTK_GATT_50008
<<: *GATT_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE GATT performance test
summary: GATT 4 master connect 1 slave and write char performance test
initial condition: BLE_CONN6
test environment: SSC_T5_1
steps: |
1. update connection parameter
2. do primary service discovery
3. do write char for some time
expected result: |
1. succeed
2. succeed
3. calculate throughput
execution time: 2
cmd set:
- "BLEStress/BLEMultiPerformance"
- - test_time = 120
- ""
- - mtu = 512
- ""
- - gatt_op = "write"
- ""
- - op_char = "0xC304"
- ""
- - op_len = 256
- ""
- - master_duts = ["SSC2", "SSC3", "SSC4", "SSC5"]
- ""
- - slave_duts = ["SSC1"]
- ""
- ID: BTSTK_GATT_50009
<<: *GATT_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE GATT performance test
summary: notify performance test when GATT master connects to 4 slaves
initial condition: BLE_CONN5
test environment: SSC_T5_1
steps: |
1. update connection parameter
2. do primary service discovery
3. do write char for some time
expected result: |
1. succeed
2. succeed
3. calculate throughput
execution time: 2
cmd set:
- "BLEStress/BLEMultiPerformance"
- - test_time = 120
- ""
- - mtu = 512
- ""
- - gatt_op = "notify"
- ""
- - op_char = "0xC305"
- ""
- - op_len = 256
- ""
- - master_duts = ["SSC1"]
- ""
- - slave_duts = ["SSC2", "SSC3", "SSC4", "SSC5"]
- ""
- ID: BTSTK_GATT_50010
<<: *GATT_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE GATT performance test
summary: notify performance test when GATT 4 masters connect to 1 slave
initial condition: BLE_CONN6
test environment: SSC_T5_1
steps: |
1. update connection parameter
2. do primary service discovery
3. do write char for some time
expected result: |
1. succeed
2. succeed
3. calculate throughput
execution time: 2
cmd set:
- "BLEStress/BLEMultiPerformance"
- - test_time = 120
- ""
- - mtu = 512
- ""
- - gatt_op = "notify"
- ""
- - op_char = "0xC305"
- ""
- - op_len = 256
- ""
- - master_duts = ["SSC2", "SSC3", "SSC4", "SSC5"]
- ""
- - slave_duts = ["SSC1"]
- ""
- ID: BTSTK_GATT_50011
<<: *GATT_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE GATT performance test
summary: indicate performance test when GATT master connects 4 slaves
initial condition: BLE_CONN5
test environment: SSC_T5_1
steps: |
1. update connection parameter
2. do primary service discovery
3. do write char for some time
expected result: |
1. succeed
2. succeed
3. calculate throughput
execution time: 2
cmd set:
- "BLEStress/BLEMultiPerformance"
- - test_time = 120
- ""
- - mtu = 512
- ""
- - gatt_op = "indicate"
- ""
- - op_char = "0xC306"
- ""
- - op_len = 256
- ""
- - master_duts = ["SSC1"]
- ""
- - slave_duts = ["SSC2", "SSC3", "SSC4", "SSC5"]
- ""
- ID: BTSTK_GATT_50012
<<: *GATT_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE GATT performance test
summary: indicate performance test when GATT 4 masters connect 1 slave
initial condition: BLE_CONN6
test environment: SSC_T5_1
steps: |
1. update connection parameter
2. do primary service discovery
3. do write char for some time
expected result: |
1. succeed
2. succeed
3. calculate throughput
execution time: 2
cmd set:
- "BLEStress/BLEMultiPerformance"
- - test_time = 120
- ""
- - mtu = 512
- ""
- - gatt_op = "indicate"
- ""
- - op_char = "0xC306"
- ""
- - op_len = 256
- ""
- - master_duts = ["SSC2", "SSC3", "SSC4", "SSC5"]
- ""
- - slave_duts = ["SSC1"]
- ""

View file

@ -17,8 +17,8 @@
test cases:
- ID: BTSTK_MISC_0101
<<: *MISC_CASE
test point 2: bt init and enable
summary: correct init and deinit flow
test point 2: bt host init and enable
summary: correct host init and deinit flow
steps: |
1. disable and deinit bt
2. init bt
@ -45,8 +45,8 @@ test cases:
- ["R SSC1 C +BT:OK"]
- ID: BTSTK_MISC_0102
<<: *MISC_CASE
test point 2: bt init and enable
summary: incorrect deinit disable flow
test point 2: bt host init and enable
summary: incorrect host deinit disable flow
steps: |
1. disable and deinit bt
2. init and enable bt
@ -85,8 +85,8 @@ test cases:
- ["R SSC1 C +BT:ERROR"]
- ID: BTSTK_MISC_0103
<<: *MISC_CASE
test point 2: bt init and enable
summary: incorrect init enable flow
test point 2: bt host init and enable
summary: incorrect host init enable flow
steps: |
1. disable and deinit bt
2. enable bt
@ -247,7 +247,7 @@ test cases:
- ID: BTSTK_MISC_0401
<<: *MISC_CASE
test point 2: bt controller init and enable
summary: incorrect init enable flow
summary: incorrect controller init enable flow
steps: |
1. disable and deinit btc
2. enable btc
@ -284,7 +284,7 @@ test cases:
- ID: BTSTK_MISC_0402
<<: *MISC_CASE
test point 2: bt controller init and enable
summary: correct init and deinit flow
summary: correct controller init and deinit flow
steps: |
1. disable and deinit btc
2. init btc
@ -312,7 +312,7 @@ test cases:
- ID: BTSTK_MISC_0403
<<: *MISC_CASE
test point 2: bt controller init and enable
summary: incorrect deinit disable flow
summary: incorrect controller deinit disable flow
steps: |
1. disable and deinit btc
2. init and enable btc

View file

@ -5,7 +5,7 @@
category: Function
test point 1: basic function
initial condition: BLE_INIT_SMP
test environment: SSC_T2_1
test environment: SSC_T2_5
execution time: 0
module: BT Stack
sub module: SMP
@ -70,7 +70,7 @@
.check_connection: &check_connection
LIST_MERGE:
- - "SSC SSC1 gattc -D -z primaryService -p 0x10"
- ["R SSC1 C +GATTC:DiscoverService,A000"]
- ["R SSC1 C +GATTC:DiscoverService,A002"]
.disconnect: &disconnect
LIST_MERGE:
@ -1619,7 +1619,7 @@ test cases:
- ID: BTSTK_SMP_03001
<<: *SMP_CASE
test point 2: BLE SMP pair with pairing request test
summary: BLE SMP start pair with pairing request
summary: BLE SMP start pair with secruity request
steps: |
1. set sec properity None on initiator and responder
2. set IOCAP to KeyboardDisplay on initiator and responder
@ -1666,7 +1666,7 @@ test cases:
- ID: BTSTK_SMP_04001
<<: *SMP_CASE
test point 2: BLE SMP key test
summary: BLE SMP set key size test
summary: BLE SMP set key size less than required
allow fail: 1/2
steps: |
1. set key size 7
@ -1691,7 +1691,7 @@ test cases:
- ID: BTSTK_SMP_04002
<<: *SMP_CASE
test point 2: BLE SMP key test
summary: BLE SMP set key size test
summary: BLE SMP set key size greater than required
allow fail: 1/2
steps: |
1. set key size 16
@ -1777,6 +1777,8 @@ test cases:
- - "SSC SSC1 blesmp -R -a 1 -r <dut2_bt_mac>"
- ['R SSC2 A <key>:BLESMP:NCReq,(\d+)', 'R SSC1 C NCReq P <key>']
- - "SSC SSC2 blesmp -K -r <dut1_bt_mac> -a {%d} -k 000001"
- []
- - DELAY 10
- ['P SSC[1-2] C +BLESMP:AuthComplete,Fail']
- *disconnect
- - LOOP 2 6 "[1,0]" "[0,1]"
@ -1864,7 +1866,7 @@ test cases:
- [""]
- ID: BTSTK_SMP_06001
<<: *SMP_CASE
test environment: SSC_T1_1
test environment: SSC_T1_4
initial condition: BLE_DEINIT1
test point 2: BLE SMP use API in abnormal state
summary: BLE SMP use API when BLE not initialized, not enabled or not registered callback
@ -2253,15 +2255,21 @@ test cases:
- ID: BTSTK_SMP_08003
<<: *SMP_CASE
test point 2: BLE SMP bond item management test
summary: BLE SMP get bond list and number
summary: BLE SMP get bond list and number when pairing and after reboot
steps: |
1. DUT2 set AuthReqMode and RspKey
2. pairing
3. get bong and remove bond
1. all slaves set AuthReqMode and RspKey
2. do pairing
3. master and slave get bond list and num
4. reboot
5. master and slave get bond list and num
6. slave remove bond device
expected result: |
1. Succeed
2. Succeed
3. Succeed
4. succeed
5. succeed
6. succeed
test environment: SSC_T5_1
initial condition: BLE_INIT_SMP5
cmd set:
@ -2286,12 +2294,18 @@ test cases:
- ['P SSC1 C +BLESMP:GetBondList,OK,4']
- - "SSC SSC1 blesmp -B -z getnum"
- ['P SSC1 C +BLESMP:GetBondNum,4']
- - "SSC SSC1 bleconn -D -z all"
- ['R SSC1 C +BLECONN:']
- - "SSC SSC1 blesmp -B -z remove -r <dut2_bt_mac>"
- ['P SSC1 RE "\+BLESMP:RemoveBond,Success,%%s"%%(<dut2_bt_mac>)']
- - "SSC SSC1 blesmp -B -z remove -r <dut3_bt_mac>"
- ['P SSC1 RE "\+BLESMP:RemoveBond,Success,%%s"%%(<dut3_bt_mac>)']
- - "SSC SSC2 blesmp -B -z getnum"
- ['P SSC2 C +BLESMP:GetBondNum,1']
- - "SSC SSC[1-2] reboot"
- ['R SSC[1-2] C !!!ready!!!']
- - "SSC SSC[1-2] ble -R"
- ["R SSC[1-2] C +BLE:OK"]
- - "SSC SSC1 blesmp -B -z getnum"
- ['P SSC1 C +BLESMP:GetBondNum,4']
- - "SSC SSC2 blesmp -B -z getnum"
- ['P SSC2 C +BLESMP:GetBondNum,1']
- - "SSC SSC2 blesmp -B -z remove -r <dut1_bt_mac>"
- ['P SSC2 RE "\+BLESMP:RemoveBond,Success,%%s"%%(<dut1_bt_mac>)']
- ID: BTSTK_SMP_08004
<<: *SMP_CASE
test point 2: BLE SMP bond item management test
@ -2304,3 +2318,336 @@ test cases:
- ""
- - "SSC SSC1 blesmp -B -z remove -r <dut2_bt_mac>"
- ['P SSC1 C +BLESMP:RemoveBond,Fail']
- ID: BTSTK_SMP_08005
<<: *SMP_CASE
test point 2: BLE SMP remove bond
summary: BLE SMP bond 15/16 devices and get list
steps: |
1. DUT2 set AuthReqMode and RspKey
2. DUT2 set static random address
3. DUT1 and DUT2 do pairing
4. loop step 2 and step3 16 times
5. get bond list and bond num
6. DUT2 set static random address
7. DUT1 and DUT2 do pairing
8. get bond list and bond num
expected result: |
1. Succeed
2. Succeed
3. Succeed
4. succeed
5. succeed
6. succeed
7. succeed
8. succeed
cmd set:
- ""
- - "SSC SSC[1-2] blesmp -S -z AuthReqMode -v 0x01"
- ['P SSC[1-2] C +BLESMP:OK']
- - "SSC SSC[1-2] blesmp -S -z IOCAP -v 0x03"
- ['P SSC[1-2] C +BLESMP:OK']
- - "SSC SSC[1-2] blesmp -S -z RspKey -v 0x03"
- ['P SSC[1-2] C +BLESMP:OK']
- - LOOP 15 7 "range(0,15)" "range(0,15)" "range(0,15)"
- ""
- - "SSC SSC2 bleadv -D -z stop"
- ['R SSC2 C +BLEADV:Stop,OK']
- - "SSC SSC2 ble -S -z randAddr -a c0:9b:0e:36:6d:7{%x} -r 1"
- ["R SSC2 C +BLECONN:SetRandAddr,OK"]
- - "SSC SSC2 bleadv -D -z start -o 1"
- ['R SSC2 C +BLEADV:Start,OK']
- - "SSC SSC1 bleconn -C -p 0x10 -a c0:9b:0e:36:6d:7{%x} -r 1"
- ['P SSC1 C +BLE:GattcConnect,OK', 'P SSC2 C +BLE:GattsConnect']
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['P SSC1 C +BLESMP:SecReq']
- - "SSC SSC1 blesmp -R -a 1 -r c0:9b:0e:36:6d:7{%x}"
- ['P SSC1 C +BLESMP:AuthComplete,Success,0','P SSC2 C +BLESMP:AuthComplete,Success,0']
- - "SSC SSC1 bleconn -D -z all"
- ['P SSC1 C +BLE:CLOSE', 'P SSC2 C +BLE:GattsDisconnect']
- - "SSC SSC1 blesmp -B -z getlist -n 16"
- ['P SSC1 C +BLESMP:GetBondList,OK,15']
- - "SSC SSC2 ble -S -z randAddr -a c1:0a:d3:25:7a:cf -r 1"
- ["R SSC2 C +BLECONN:SetRandAddr,OK"]
- - "SSC SSC2 bleadv -D -z stop"
- ['R SSC2 C +BLEADV:Stop,OK']
- - "SSC SSC2 bleadv -D -z start -o 1"
- ['R SSC2 C +BLEADV:Start,OK']
- - "SSC SSC1 bleconn -C -p 0x10 -a c1:0a:d3:25:7a:cf -r 1"
- ['P SSC1 C +BLE:GattcConnect,OK', 'P SSC2 C +BLE:GattsConnect']
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['P SSC1 C +BLESMP:SecReq']
- - "SSC SSC1 blesmp -R -a 1 -r c1:0a:d3:25:7a:cf"
- ['P SSC1 C +BLESMP:AuthComplete,Success,0','P SSC2 C +BLESMP:AuthComplete,Success,0']
- - "SSC SSC1 blesmp -B -z getlist -n 16"
- ['P SSC1 C +BLESMP:GetBondList,OK,15']
- ID: BTSTK_SMP_50001
<<: *SMP_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE SMP GATT performance test
summary: GATT read char performance test after just work pair
Test App: SSC_BLE_PERF
steps: |
1. update connection parameter
2. do primary service discovery
3. do read char for some time
expected result: |
1. succeed
2. succeed
3. calculate throughput
execution time: 2
cmd set:
- "BLEStress/BLESMPGATTPerformance"
- - test_time = 420
- ""
- - mtu = 512
- ""
- - gatt_op = "read"
- ""
- - pair_op = "just_work_pair"
- ""
- - op_char = "0xC301"
- ""
- ID: BTSTK_SMP_50002
<<: *SMP_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE SMP GATT performance test
summary: GATT read char performance test after numberic comparision pair
Test App: SSC_BLE_PERF
steps: |
1. update connection parameter
2. do primary service discovery
3. do read char for some time
expected result: |
1. succeed
2. succeed
3. calculate throughput
execution time: 2
cmd set:
- "BLEStress/BLESMPGATTPerformance"
- - test_time = 420
- ""
- - mtu = 512
- ""
- - gatt_op = "read"
- ""
- - pair_op = "numberic_comparision_pair"
- ""
- - op_char = "0xC301"
- ""
- ID: BTSTK_SMP_50003
<<: *SMP_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE SMP GATT performance test
summary: GATT write char performance test after just work pair
Test App: SSC_BLE_PERF
steps: |
1. update connection parameter
2. do primary service discovery
3. do write char for some time
expected result: |
1. succeed
2. succeed
3. calculate throughput
execution time: 2
cmd set:
- "BLEStress/BLESMPGATTPerformance"
- - test_time = 420
- ""
- - mtu = 512
- ""
- - gatt_op = "write"
- ""
- - op_char = "0xC304"
- ""
- - pair_op = "just_work_pair"
- ""
- - op_len = 490
- ""
- ID: BTSTK_SMP_50004
<<: *SMP_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE SMP GATT performance test
summary: GATT write char performance test after numberic comparision pair
Test App: SSC_BLE_PERF
steps: |
1. update connection parameter
2. do primary service discovery
3. do write char for some time
expected result: |
1. succeed
2. succeed
3. calculate throughput
execution time: 2
cmd set:
- "BLEStress/BLESMPGATTPerformance"
- - test_time = 420
- ""
- - mtu = 512
- ""
- - gatt_op = "write"
- ""
- - op_char = "0xC304"
- ""
- - pair_op = "numberic_comparision_pair"
- ""
- - op_len = 490
- ""
- ID: BTSTK_SMP_50005
<<: *SMP_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE SMP GATT performance test
summary: GATT notify performance test after just work pair
Test App: SSC_BLE_PERF
steps: |
1. update connection parameter
2. do primary service discovery
3. do notify for some time
expected result: |
1. succeed
2. succeed
3. calculate throughput
execution time: 2
cmd set:
- "BLEStress/BLESMPGATTPerformance"
- - test_time = 420
- ""
- - mtu = 512
- ""
- - gatt_op = "notify"
- ""
- - op_char = "0xC305"
- ""
- - pair_op = "just_work_pair"
- ""
- - op_len = 490
- ""
- ID: BTSTK_SMP_50006
<<: *SMP_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE SMP GATT performance test
summary: GATT notify performance test after numberic comparision pair
Test App: SSC_BLE_PERF
steps: |
1. update connection parameter
2. do primary service discovery
3. do notify for some time
expected result: |
1. succeed
2. succeed
3. calculate throughput
execution time: 2
cmd set:
- "BLEStress/BLESMPGATTPerformance"
- - test_time = 420
- ""
- - mtu = 512
- ""
- - gatt_op = "notify"
- ""
- - op_char = "0xC305"
- ""
- - pair_op = "numberic_comparision_pair"
- ""
- - op_len = 490
- ""
- ID: BTSTK_SMP_50007
<<: *SMP_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE SMP GATT performance test
summary: GATT indicate performance test after just work pair
Test App: SSC_BLE_PERF
steps: |
1. update connection parameter
2. do primary service discovery
3. do notify for some time
expected result: |
1. succeed
2. succeed
3. calculate throughput
execution time: 2
cmd set:
- "BLEStress/BLESMPGATTPerformance"
- - test_time = 420
- ""
- - mtu = 512
- ""
- - gatt_op = "indicate"
- ""
- - pair_op = "just_work_pair"
- ""
- - op_char = "0xC306"
- ""
- - op_len = 490
- ""
- ID: BTSTK_SMP_50008
<<: *SMP_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE SMP GATT performance test
summary: GATT indicate performance test after numberic comparision pair
Test App: SSC_BLE_PERF
steps: |
1. update connection parameter
2. do primary service discovery
3. do notify for some time
expected result: |
1. succeed
2. succeed
3. calculate throughput
execution time: 2
cmd set:
- "BLEStress/BLESMPGATTPerformance"
- - test_time = 420
- ""
- - mtu = 512
- ""
- - gatt_op = "indicate"
- ""
- - pair_op = "numberic_comparision_pair"
- ""
- - op_char = "0xC306"
- ""
- - op_len = 490
- ""
- ID: BTSTK_SMP_51001
<<: *SMP_CASE
category: Performance
test point 1: performance + stress
test point 2: BLE SMP performance test
summary: BLE SMP Connect and disconnect performance test
steps: |
1. DUT2 set AuthReqMode and RspKey
2. DUT1 disconnect with DUT2
3. DUT2 start advertising
4. DUT1 connect to DUT2
5. do service discovery
6. loop step 1-4
7. check connection fail ratio and average conn time
expected result: |
1. succeed
2. succeed
3. succeed
4. succeed
5. succeed
6. succeed
7. meet pass standard
execution time: 6
version: v1 (2017-05-19)
CI ready: 'No'
cmd set:
- "BLEStress/BLESMPConnPerformance"
- - "test_time = 420"
- ""
- - "average_conn_time = 3"
- ""
- - "fail_ratio = 0.01"
- ""
- - "fail_timeout = 10"
- ""

View file

@ -21,7 +21,7 @@ test cases:
steps: 系统重启
sub module: Misc
summary: test reboot function
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: sw reboot
version: v1 (2016-8-15)
@ -49,7 +49,7 @@ test cases:
steps: 查询空闲ram
sub module: Misc
summary: get heap size test
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: 'get heap size '
version: v1 (2016-8-15)

View file

@ -38,7 +38,7 @@ test cases:
打开DHCP OK\n5.查询到sta ip \n6.target1 连接AP ok\n7.查询到sta ip 为target_ip"
sub module: DHCP
summary: dhcp client function test
test environment: SSC_T1_1
test environment: SSC_T1_5
test point 1: basic function
test point 2: DHCP client function test
version: v2 (2016-10-19)
@ -90,7 +90,7 @@ test cases:
7.target1 查询 DHCP 状态
sub module: DHCP
summary: dhcp status query
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: DHCP client function test
version: v1 (2016-8-15)
@ -136,7 +136,7 @@ test cases:
打开DHCP ok"
sub module: DHCP
summary: server dhcp lease test
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
@ -185,7 +185,7 @@ test cases:
4. Loop step3
sub module: DHCP
summary: dhcp server ip pool
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
@ -242,7 +242,7 @@ test cases:
4. Loop step3 twice
sub module: DHCP
summary: dhcp server ip pool empty
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
@ -306,7 +306,7 @@ test cases:
8. target2 change mac and connect to target1
sub module: DHCP
summary: dhcp server timeout test
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
@ -347,7 +347,7 @@ test cases:
3. disable DHCP server, do config and enable
sub module: DHCP
summary: disconnect STA if config dhcp server
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
@ -398,7 +398,7 @@ test cases:
5. change to first mac, connect to softap
sub module: DHCP
summary: dhcp server assign same IP to same MAC when it's not released
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
@ -455,7 +455,7 @@ test cases:
6. target2 change mac and connect to target1
sub module: DHCP
summary: dhcp server prefer assign released IP to new client
test environment: SSC_T2_1
test environment: SSC_T2_2
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
@ -516,7 +516,7 @@ test cases:
7. target2 change mac and connect to target1
sub module: DHCP
summary: dhcp server prefer assign released IP to new client
test environment: SSC_T2_1
test environment: SSC_T2_2
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
@ -568,7 +568,7 @@ test cases:
5. softap list connected station
sub module: DHCP
summary: dhcp server reconfig and new client able to get first IP in pool
test environment: SSC_T2_1
test environment: SSC_T2_2
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
@ -624,7 +624,7 @@ test cases:
7. softap list connected station
sub module: DHCP
summary: dhcp server reconfig and new client able to get first IP in pool
test environment: SSC_T2_1
test environment: SSC_T2_2
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
@ -674,7 +674,7 @@ test cases:
5. softap list connected station
sub module: DHCP
summary: dhcp server reconfig, old client and new client able to get IP
test environment: SSC_T2_1
test environment: SSC_T2_2
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
@ -723,7 +723,7 @@ test cases:
sub module: DHCP
summary: dhcp server reconfig, old client able to get IP (discover with requested
IP)
test environment: SSC_T2_1
test environment: SSC_T2_2
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
@ -749,6 +749,8 @@ test cases:
- - R SSC1 C +DHCP:LEASE,OK
- - SSC SSC1 dhcp -S -o 2
- - R SSC1 C +DHCP:AP,OK
- - WIFI <pc_wifi_nic> CONN <random_string> <random_string> 192.168.4.2
- - R PC_COM NC ERROR C +WIFICONN:OK
- - SSC SSC2 sta -C -s <random_string> -p <random_string>
- - R SSC2 C +JAP:CONNECTED
- - DELAY 30
@ -773,7 +775,7 @@ test cases:
5. softap list connected station
sub module: DHCP
summary: dhcp server reconfig, old client able to renew IP (direct send request)
test environment: SSC_T2_1
test environment: SSC_T2_2
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
@ -812,7 +814,7 @@ test cases:
打开DHCP OK\n5.target2 jap target 1,ok"
sub module: DHCP
summary: dhcp server function test
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: DHCP server function test
version: v2 (2016-10-19)
@ -859,7 +861,7 @@ test cases:
6.target1 jap AP
sub module: DHCP
summary: sta dhcp static ip interaction
test environment: SSC_T1_1
test environment: SSC_T1_5
test point 1: interaction
test point 2: static IP and DHCP interaction test
version: v2 (2016-10-19)
@ -914,7 +916,7 @@ test cases:
设置正确的地址池\n9.target2 连接target1 "
sub module: DHCP
summary: ap dhcp static ip interaction
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: interaction
test point 2: static IP and DHCP interaction test
version: v1 (2016-8-15)

View file

@ -18,7 +18,7 @@ test cases:
initial condition: STAM2
level: Integration
module: TCPIP
steps: 1. get host name "espressif.cn"
steps: 1. get host name "gbot.espressif.cn"
sub module: DNS
summary: get host by name test
test environment: SSC_T1_2
@ -54,7 +54,7 @@ test cases:
level: Integration
module: TCPIP
steps: |-
1. get host name "espressif.cn"
1. get host name "gbot.espressif.cn"
2. connect, send, recv
sub module: DNS
summary: TCP connect to gbot.espressif.cn
@ -147,3 +147,301 @@ test cases:
test point 1: abnormal/special use
test point 2: use special DNS server config
version: v1 (2016-8-15)
- CI ready: 'No'
ID: TCPIP_DNS_0301
SDK: ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stable
cmd set:
- DNSTest/DNSTest
- - test_mode = "fallback_main_backup_dns_all_error"
- ['']
- - fallback_dns_option = "error"
- ['']
- - test_option = "main_backup_error"
- ['']
- - test_count = 20
- [dummy]
- - fallback_dns = "1.1.1.1"
- ['']
- - website_dns = "www.baidu.com"
- ['']
execution time: 0.3
expected result: |-
2.mode set ok
3.connect ap sucess
4.set fallback dns ok
5.get dns ip fail
initial condition: None
level: Integration
module: TCPIP
steps: |-
1.AP main,backup DNS all error
2.set SSC1 to sta mode
3.SSC1 connect to ap
4.set SSC1 fallback DNS
5.SSC1 get website dns IP
sub module: DNS
summary: DNS fallback main backup DNS all error test
test environment: SSC_T1_DNS
test point 1: stress + function
test point 2: DNS stress test
version: v2 (2016-10-23)
- CI ready: 'No'
ID: TCPIP_DNS_0302
SDK: ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stable
cmd set:
- DNSTest/DNSTest
- - test_mode = "fallback_dns_error_mian_backup_dns_right"
- ['']
- - fallback_dns_option = "error"
- ['']
- - test_option = "main_backup_right"
- ['']
- - test_count = 20
- [dummy]
- - fallback_dns = "2.2.2.2"
- ['']
- - website_dns = "www.baidu.com"
- ['']
execution time: 0.3
expected result: |-
2.mode set ok
3.connect ap sucess
4.set fallback dns ok
5.get dns ip ok
initial condition: None
level: Integration
module: TCPIP
steps: |-
1.AP main,backup DNS all right
2.set SSC1 to sta mode
3.SSC1 connect to ap
4.set SSC1 fallback DNS
5.SSC1 get website dns IP
sub module: DNS
summary: DNS fallback DNS error main backup DNS right test
test environment: SSC_T1_DNS
test point 1: stress + function
test point 2: DNS stress test
version: v2 (2016-10-23)
- CI ready: 'No'
ID: TCPIP_DNS_0303
SDK: ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stable
cmd set:
- DNSTest/DNSTest
- - test_mode = "fallback_main_dns_error_backup_dns_right"
- ['']
- - fallback_dns_option = "error"
- ['']
- - test_option = "backup_right"
- ['']
- - test_count = 20
- [dummy]
- - fallback_dns = "1.1.1.1"
- ['']
- - website_dns = "www.baidu.com"
- ['']
execution time: 0.3
expected result: |-
2.mode set ok
3.connect ap sucess
4.set fallback dns ok
5.get dns ip ok
initial condition: None
level: Integration
module: TCPIP
steps: |-
1.AP main DNS error,backup DNS right
2.SSC1 set as sta mode
3.SSC1 connect to ap
4.set SSC1 fallback DNS
5.SSC1 get website dns IP
sub module: DNS
summary: DNS fallback main DNS error backup DNS right test
test environment: SSC_T1_DNS
test point 1: stress + function
test point 2: DNS stress test
version: v2 (2016-10-23)
- CI ready: 'No'
ID: TCPIP_DNS_0304
SDK: ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stable
cmd set:
- DNSTest/DNSTest
- - test_mode = "fallback_main_backup_dns_all_right"
- ['']
- - fallback_dns_option = "right"
- ['']
- - test_option = "main_backup_right"
- ['']
- - test_count = 20
- [dummy]
- - fallback_dns = "208.67.222.222"
- ['']
- - website_dns = "www.baidu.com"
- ['']
execution time: 0.3
expected result: |-
2.mode set ok
3.connect ap sucess
4.set fallback dns ok
5.get dns IP ok
initial condition: None
level: Integration
module: TCPIP
steps: |-
1.AP main ,backup DNS right
2.SSC1 set as sta mode
3.SSC1 connect to ap
4.set SSC1 fallback DNS
5.SSC1 get website dns IP
sub module: DNS
summary: DNS fallback main backup DNS all right test
test environment: SSC_T1_DNS
test point 1: stress + function
test point 2: DNS stress test
version: v2 (2016-10-23)
- CI ready: 'No'
ID: TCPIP_DNS_0305
SDK: ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stable
cmd set:
- DNSTest/DNSTest
- - test_mode = "fallback_dns_right_main_backup_error"
- ['']
- - fallback_dns_set = "right"
- ['']
- - fallback_dns_option = "right"
- ['']
- - test_option = "main_backup_error"
- ['']
- - test_count = 20
- [dummy]
- - fallback_dns = "208.67.222.222"
- ['']
- - website_dns = "www.baidu.com"
- ['']
execution time: 0.3
expected result: |-
2.mode set ok
3.connect ap sucess
4.set fallback dns ok
5.get dns IP ok
initial condition: None
level: Integration
module: TCPIP
steps: |-
1.AP main ,backup DNS all error
2.SSC1 set as mode
3.SSC1 connect to ap
4.set SSC1 fallback DNS
5.SSC1 get website dns IP
sub module: DNS
summary: DNS fallback DNS right main backup error test
test environment: SSC_T1_DNS
test point 1: stress + function
test point 2: DNS stress test
version: v2 (2016-10-23)
- CI ready: 'No'
ID: TCPIP_DNS_0306
SDK: ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stable
cmd set:
- DNSTest/DNSTest
- - test_mode = "dns_dhcp_option"
- ['']
- - test_count = 20
- [dummy]
- - fallback_dns = "208.67.222.222"
- ['']
- - website_dns = "www.baidu.com"
- ['']
execution time: 0.3
expected result: |-
1.ap set ok
2.set sta mode ok
3.jap ok
4.disable dhcp ok
5.set static ip addr suc
6.set fallback dns suc
7.get dns ip suc
8.dhcp start suc
9.get dns ip ok
11.jap ok
12.get dns ip ok
initial condition: None
level: Integration
module: TCPIP
steps: |-
1.AP main ,backup DNS all right
2.set SSC1 to sta mode
3.SSC1 connect to ap
4.SSC1 disable dhcp
5.SSC1 set static ip addr
6.SSC1 set fallback dns
7.SSC1 get website dns IP
8.SSC1 start dhcp
9.SSC1 get website dns IP
10.SSC1 disconnect with ap
11.SSC1 reconnet ap
12.SSC1 get website dns IP
sub module: DNS
summary: DNS DHCP option test
test environment: SSC_T1_DNS
test point 1: stress + function
test point 2: DNS stress test
version: v2 (2016-10-23)
- CI ready: 'No'
ID: TCPIP_DNS_0307
SDK: ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stable
cmd set:
- DNSTest/DNSTest
- - test_mode = "softap_dns_test"
- ['']
- - test_count = 20
- [dummy]
- - main_dns = "208.67.222.222"
- ['']
execution time: 0.3
expected result: |-
1.set mode ok
2.set mode ok
3.sta connect softap suc
4.disable dhcp ok
5.set dns server suc
6.set main dns suc
7.SSC2 main dns must the same as SSC1
initial condition: None
level: Integration
module: TCPIP
steps: |-
1.SSC1 set as softap
2.SSC2 set as sta
3.SSC2 connected softap
4.SSC1 disable dhcp
5.SSC1 dhcp action dns server
6.SSC1 set main dns
7.check SSC2 main dns server
sub module: DNS
summary: DNS softap DNS test
test environment: SSC_T2_1
test point 1: stress + function
test point 2: DNS stress test
version: v2 (2016-10-23)

View file

@ -27,7 +27,7 @@ test cases:
2.ping -i <pc_ip> -c 2
sub module: ICMP
summary: ping function test
test environment: SSC_T1_1
test environment: SSC_T1_5
test point 1: basic function
test point 2: ping function test
version: v1 (2016-8-15)

View file

@ -39,7 +39,7 @@ test cases:
4. join group with wrong host addr and wrong multicast addr
sub module: IGMP
summary: station IGMP join group address check
test environment: SSC_T1_1
test environment: SSC_T1_5
test point 1: basic function
test point 2: IGMP API parameter check
version: v1 (2016-8-15)
@ -83,7 +83,7 @@ test cases:
5. leave group with correct host addr and correct multicast addr
sub module: IGMP
summary: station IGMP leave group address check
test environment: SSC_T1_1
test environment: SSC_T1_5
test point 1: basic function
test point 2: IGMP API parameter check
version: v1 (2016-8-15)
@ -127,7 +127,7 @@ test cases:
4. join group with wrong host addr and wrong multicast addr
sub module: IGMP
summary: softAP IGMP join group address check
test environment: SSC_T1_1
test environment: SSC_T1_8
test point 1: basic function
test point 2: IGMP API parameter check
version: v1 (2016-8-15)
@ -171,7 +171,7 @@ test cases:
5. leave group with correct host addr and correct multicast addr
sub module: IGMP
summary: softAP IGMP leave group address check
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: IGMP API parameter check
version: v1 (2016-8-15)
@ -180,9 +180,8 @@ test cases:
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: '1/2'
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
@ -211,7 +210,7 @@ test cases:
3. PC send UDP packet to multicast addr
sub module: IGMP
summary: station IGMP recv packets
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: IGMP send/recv test
version: v1 (2016-8-15)
@ -220,9 +219,8 @@ test cases:
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: '1/2'
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
@ -257,7 +255,7 @@ test cases:
4. target2 send to multicast addr
sub module: IGMP
summary: station send multicast packets
test environment: SSC_T2_1
test environment: SSC_T2_4
test point 1: basic function
test point 2: IGMP send/recv test
version: v1 (2016-8-15)
@ -266,7 +264,6 @@ test cases:
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
@ -297,7 +294,7 @@ test cases:
3. PC send UDP packet to multicast addr
sub module: IGMP
summary: softAP IGMP recv packets
test environment: SSC_T1_1
test environment: SSC_T1_8
test point 1: basic function
test point 2: IGMP send/recv test
version: v1 (2016-8-15)
@ -306,7 +303,6 @@ test cases:
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
@ -341,7 +337,383 @@ test cases:
4. target2 send to multicast addr
sub module: IGMP
summary: softAP send multicast packets
test environment: SSC_T2_1
test environment: SSC_T2_4
test point 1: basic function
test point 2: IGMP send/recv test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_IGMP_0101
SDK: 'ESP32_IDF'
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 soc -B -t UDP -p <test_udp_port1>
- - R SSC1 A <sock1>:\+BIND:(\d+),OK
- - SSC SSC1 soc -J -s <sock1> -m 224.1.1.1
- - R SSC1 C +IGMP:OK
- - SSC SSC1 soc -G -s <sock1> -m 224.1.1.1
- - R SSC1 C +IGMP:OK
- - SSC SSC1 soc -J -s <sock1> -m 223.1.1.1
- - R SSC1 C +IGMP:ERROR
- - SSC SSC1 soc -J -s <sock1> -m 240.1.1.1
- - R SSC1 C +IGMP:ERROR
execution time: 0.0
expected result: |
1. OK
2. OK
3. OK
4. ERROR
5. ERROR
initial condition: STAM2
level: Integration
module: TCPIP
steps: |
1. create UDP socket
2. join group with correct multicast addr
3. leave group with correct multicast addr
4. join group with wrong multicast addr
5. join group with wrong multicast addr
sub module: IGMP
summary: station IGMP join group address check
test environment: SSC_T1_6
test point 1: basic function
test point 2: IGMP API parameter check
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_IGMP_0102
SDK: 'ESP32_IDF'
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 soc -B -t UDP -p <test_udp_port1>
- - R SSC1 A <sock1>:\+BIND:(\d+),OK
- - SSC SSC1 soc -J -s <sock1> -m 224.1.1.1
- - R SSC1 C +IGMP:OK
- - SSC SSC1 soc -G -s <sock1> -m 224.1.1.1
- - R SSC1 C +IGMP:OK
- - SSC SSC1 soc -B -t UDP -p <random_port>
- - R SSC1 A <sock2>:\+BIND:(\d+),OK
- - SSC SSC1 soc -J -s <sock2> -m 224.1.1.2
- - R SSC1 C +IGMP:OK
- - SSC SSC1 soc -G -s <sock2> -m 224.1.1.1
- - R SSC1 C +IGMP:ERROR
execution time: 0.0
expected result: |
1. OK
2. OK
3. OK
4. OK
5. OK
6. ERROR
initial condition: STAM2
level: Integration
module: TCPIP
steps: |
1. create UDP socket
2. join group with correct multicast addr
3. leave group with correct multicast addr
4. create UDP socket
5. join group with correct multicast addr
6. leave group with wrong multicast addr
sub module: IGMP
summary: station IGMP leave group address check
test environment: SSC_T1_5
test point 1: basic function
test point 2: IGMP API parameter check
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_IGMP_0103
SDK: 'ESP32_IDF'
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 soc -B -t UDP -p <test_udp_port1>
- - R SSC1 A <sock1>:\+BIND:(\d+),OK
- - SSC SSC1 soc -J -s <sock1> -m 224.1.1.1
- - R SSC1 C +IGMP:OK
- - SSC SSC1 soc -G -s <sock1> -m 224.1.1.1
- - R SSC1 C +IGMP:OK
- - SSC SSC1 soc -J -s <sock1> -m 223.1.1.1
- - R SSC1 C +IGMP:ERROR
- - SSC SSC1 soc -J -s <sock1> -m 240.1.1.1
- - R SSC1 C +IGMP:ERROR
execution time: 0.0
expected result: |
1. OK
2. OK
3. OK
4. ERROR
5. ERROR
initial condition: APM2
level: Integration
module: TCPIP
steps: |
1. create UDP socket
2. join group with correct multicast addr
3. leave group with correct multicast addr
4. join group with wrong multicast addr
5. join group with wrong multicast addr
sub module: IGMP
summary: softAP IGMP join group address check
test environment: SSC_T1_8
test point 1: basic function
test point 2: IGMP API parameter check
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_IGMP_0104
SDK: 'ESP32_IDF'
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 soc -B -t UDP -p <test_udp_port1>
- - R SSC1 A <sock1>:\+BIND:(\d+),OK
- - SSC SSC1 soc -J -s <sock1> -m 224.1.1.1
- - R SSC1 C +IGMP:OK
- - SSC SSC1 soc -G -s <sock1> -m 224.1.1.1
- - R SSC1 C +IGMP:OK
- - SSC SSC1 soc -B -t UDP -p <random_port>
- - R SSC1 A <sock2>:\+BIND:(\d+),OK
- - SSC SSC1 soc -J -s <sock2> -m 224.1.1.2
- - R SSC1 C +IGMP:OK
- - SSC SSC1 soc -G -s <sock2> -m 224.1.1.1
- - R SSC1 C +IGMP:ERROR
execution time: 0.0
expected result: |
1. OK
2. OK
3. OK
4. OK
5. OK
6. ERROR
initial condition: APM2
level: Integration
module: TCPIP
steps: |
1. create UDP socket
2. join group with correct multicast addr
3. leave group with correct multicast addr
4. create UDP socket
5. join group with correct multicast addr
6. leave group with wrong multicast addr
sub module: IGMP
summary: softAP IGMP leave group address check
test environment: SSC_T1_7
test point 1: basic function
test point 2: IGMP API parameter check
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_IGMP_0201
SDK: 'ESP32_IDF'
Test App: SSC
allow fail: '1/5'
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 soc -B -t UDP -p <test_udp_port2>
- - R SSC1 A <sock1>:\+BIND:(\d+),OK
- - SSC SSC1 soc -J -s <sock1> -m 224.1.1.1
- - R SSC1 C +IGMP:OK
- - SOC SOC1 BIND <test_udp_port2>
- - R SOC_COM L OK
- - SOC SOC1 SENDTO 1 <test_udp_port2> 224.1.1.1
- - R SSC1 SL <sock1>+1
- - SSC SSC1 soc -G -s <sock1> -m 224.1.1.1
- - R SSC1 C +IGMP:OK
- - SOC SOC1 SENDTO 1 <test_udp_port2> 224.1.1.1
- - R SSC1 NC +RECVFROM
execution time: 0.0
expected result: |
1. OK
2. OK
3. OK
4. able to recv packet
5. OK
6. not able to recv packet
initial condition: STAM2
level: Integration
module: TCPIP
steps: |
1. create UDP socket
2. join group with correct multicast addr
3. PC上 SOC1 UDP 传输bing <test_udp_port2> <pc_ip>
4. PC send UDP packet to multicast addr
5. leave group with correct multicast addr
6. PC send UDP packet to multicast addr
sub module: IGMP
summary: station IGMP recv packets
test environment: SSC_T1_6
test point 1: basic function
test point 2: IGMP send/recv test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_IGMP_0202
SDK: 'ESP32_IDF'
Test App: SSC
allow fail: '1/5'
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC2 op -S -o 1
- - R SSC2 C +MODE:OK
- - SSC SSC2 sta -C -s <ap_ssid> -p <ap_password>
- - R SSC2 C +JAP:CONNECTED
- - SSC SSC2 soc -T
- - R SSC2 C +CLOSEALL
- - SSC SSC1 soc -B -t UDP -p <test_udp_port1>
- - R SSC1 A <sock1>:\+BIND:(\d+),OK
- - SSC SSC1 soc -J -s <sock1> -m 224.1.1.1
- - R SSC1 C +IGMP:OK
- - SSC SSC2 soc -B -t UDP -p <random_port>
- - R SSC2 A <sock2>:\+BIND:(\d+),OK
- - SSC SSC2 soc -S -s <sock2> -i 224.1.1.1 -p <test_udp_port1> -l 10
- - R SSC1 SL <sock1>+1
- - SSC SSC1 soc -G -s <sock1> -m 224.1.1.1
- - R SSC1 C +IGMP:OK
- - SSC SSC2 soc -S -s <sock2> -i 224.1.1.1 -p <test_udp_port1> -l 10
- - R SSC1 NC +RECVFROM
- - SSC SSC2 soc -T -s <sock2>
- - R SSC2 RE CLOSE:\d+,OK
execution time: 0.0
expected result: |
1. OK
2. target2 connect succeed
3. CLOSEALL
4. OK
5. OK
6. OK
7. able to recv packet
8. OK
9. not able to recv packet
10. OK
initial condition: STAM2
level: Integration
module: TCPIP
steps: |
1. target2 set to sta mode
2. target2 join AP
3. target2 close socket
4. target1 create UDP socket
5. target1 join group using multicast addr
6. target2 create UDP socket
7. target2 send to multicast addr
8. target1 leave group with correct multicast addr
9. target2 send to multicast addr
10. target2 close socket
sub module: IGMP
summary: station send multicast packets
test environment: SSC_T2_4
test point 1: basic function
test point 2: IGMP send/recv test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_IGMP_0203
SDK: 'ESP32_IDF'
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 soc -B -t UDP -p <test_udp_port1>
- - R SSC1 A <sock1>:\+BIND:(\d+),OK
- - SSC SSC1 soc -J -s <sock1> -m 224.1.1.1
- - R SSC1 C +IGMP:OK
- - SOC SOC1 BIND <test_udp_port1> <pc_ip_wifi>
- - R SOC_COM L OK
- - SOC SOC1 SENDTO 1 <test_udp_port1> 224.1.1.1
- - R SSC1 SL <sock1>+1
- - SSC SSC1 soc -G -s <sock1> -m 224.1.1.1
- - R SSC1 C +IGMP:OK
- - SOC SOC1 SENDTO 1 <test_udp_port1> 224.1.1.1
- - R SSC1 NC +RECVFROM
execution time: 0.0
expected result: |
1. OK
2. OK
3. OK
4. able to recv packet
5. OK
6. not able to recv packet
initial condition: APM2
level: Integration
module: TCPIP
steps: |
1. create UDP socket
2. join group using multicast addr
3. PC上 SOC1 UDP 传输bing <test_udp_port1> <pc_ip_wifi>
4. PC send UDP packet to multicast addr
5. leave group with correct multicast addr
6. PC send UDP packet to multicast addr
sub module: IGMP
summary: softAP IGMP recv packets
test environment: SSC_T1_8
test point 1: basic function
test point 2: IGMP send/recv test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_IGMP_0204
SDK: 'ESP32_IDF'
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password>
- - R SSC2 C +JAP:CONNECTED
- - SSC SSC1 soc -B -t UDP -p <test_udp_port1>
- - R SSC1 A <sock1>:\+BIND:(\d+),OK
- - SSC SSC1 soc -J -s <sock1> -m 224.1.1.1
- - R SSC1 C +IGMP:OK
- - SSC SSC2 soc -B -t UDP -p <random_port>
- - R SSC2 A <sock2>:\+BIND:(\d+),OK
- - SSC SSC2 soc -S -s <sock2> -i 224.1.1.1 -p <test_udp_port1> -l 10
- - R SSC1 SL <sock1>+1
- - SSC SSC1 soc -G -s <sock1> -m 224.1.1.1
- - R SSC1 C +IGMP:OK
- - SSC SSC2 soc -S -s <sock2> -i 224.1.1.1 -p <test_udp_port1> -l 10
- - R SSC1 NC +RECVFROM
- - SSC SSC2 soc -T -s <sock2>
- - R SSC2 RE CLOSE:\d+,OK
execution time: 0.0
expected result: |
1. target2 connect succeed
2. OK
3. OK
4. OK
5. target1 able to recv packet
6. OK
7. target1 not able to recv packet
8. OK
initial condition: APM2
level: Integration
module: TCPIP
steps: |
1. target2 join AP
2. target1 create UDP socket
3. target1 join group using multicast addr
4. target2 create UDP socket
5. target2 send to multicast addr
6. target1 leave group with correct multicast addr
7. target2 send to multicast addr
8. target2 close socket
sub module: IGMP
summary: softAP send multicast packets
test environment: SSC_T2_4
test point 1: basic function
test point 2: IGMP send/recv test
version: v1 (2016-8-15)

View file

@ -35,7 +35,7 @@ test cases:
1\n5.target1 设置sta ip 192.168.123.123\n6.target1 查询 当前sta ip "
sub module: IP
summary: sta set and query static ip test
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: set and query static IP
version: v1 (2016-8-15)
@ -79,7 +79,7 @@ test cases:
ip 为target_ap_ip"
sub module: IP
summary: ap set and query static ip test
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: set and query static IP
version: v1 (2016-8-15)

View file

@ -44,7 +44,7 @@ test cases:
6.target1上使用步骤2创建的socket去连接 PC的ip远端端口不存在。
sub module: TCP
summary: STA mode, connect test. use different ip, port
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -86,7 +86,7 @@ test cases:
4.PC tcp 连接到不存在的port ,<target_ip>
sub module: TCP
summary: STA mode, server listen test. use different kinds of port
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -133,14 +133,14 @@ test cases:
steps: |
1. PC上建立TCP 监听 test_tcp_port1
2.target1上创建TCP socket
3.target1上使用步骤2创建的socket去连接PC的iptest_tcp_port1
3.target1上使用步骤2创建的socket去连接 PC的iptest_tcp_port1
4.PC与target1 创建好TCP 连接有ACCEPT
5.PC send 5 bytes to 8266
6.8266 send 5 bytes to PC
7.8266 send 1460 to PC.
sub module: TCP
summary: STA mode, send/recv basic test
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -204,7 +204,7 @@ test cases:
10.target1 shutdown socket3 R
sub module: TCP
summary: STA mode, shutdown basic test
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -278,7 +278,7 @@ test cases:
socket1\n15.target1关闭socket1"
sub module: TCP
summary: STA mode, close for different types of TCP sockets test
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -346,7 +346,7 @@ test cases:
11.target1上使用步骤10创建的socket5去连接 PC的iptest_tcp_port1,PC有ACCEPT
sub module: TCP
summary: STA mode, create max TCP sockets test
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -395,7 +395,7 @@ test cases:
\ "
sub module: TCP
summary: STA mode, accept max TCP client by server test
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -459,7 +459,7 @@ test cases:
11.target1 abort socket1
sub module: TCP
summary: STA mode, espconn abort test
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -508,7 +508,7 @@ test cases:
6.target1上使用步骤2创建的socket去连接 PC的ip远端端口不存在。
sub module: TCP
summary: AP mode, connect test. use different ip, port
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -550,7 +550,7 @@ test cases:
4.PC tcp 连接到不存在的port ,<target_ip>
sub module: TCP
summary: AP mode, server listen test. use different kinds of port
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -595,7 +595,7 @@ test cases:
level: Integration
module: TCPIP
steps: |
1. PC上建立TCP 监听 test_tcp_port1
1.PC上建立TCP 监听 test_tcp_port1
2.target1上创建TCP socket
3.target1上使用步骤2创建的socket去连接PC的iptest_tcp_port1
4.PC与target1 创建好TCP 连接有ACCEPT
@ -604,7 +604,7 @@ test cases:
7.8266 send 100 * 1460 to PC.
sub module: TCP
summary: AP mode, send/recv basic test
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -668,7 +668,7 @@ test cases:
10.target1 shutdown socket3 R
sub module: TCP
summary: AP mode, shutdown basic test
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -742,7 +742,7 @@ test cases:
socket1\n15.target1关闭socket1"
sub module: TCP
summary: AP mode, close for different types of TCP sockets test
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -810,7 +810,7 @@ test cases:
11.target1上使用步骤10创建的socket5去连接 PC的iptest_tcp_port1,PC有ACCEPT
sub module: TCP
summary: AP mode, create max TCP sockets test
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -859,7 +859,7 @@ test cases:
\ "
sub module: TCP
summary: AP mode, accept max TCP client by server test
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -931,7 +931,7 @@ test cases:
12.target1上使用步骤2创建的socket去连接 PC的ip<test_tcp_port1>
sub module: TCP
summary: STA mode, connect test. use socket in state that can't connect
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) in different state
version: v1 (2016-8-15)
@ -991,7 +991,7 @@ test cases:
9.target1上使用不存在socket,创建TCP 监听
sub module: TCP
summary: STA mode, server listen test. use socket in state that can't listen
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) in different state
version: v1 (2016-8-15)
@ -1051,7 +1051,7 @@ test cases:
9.target1上不指定socket往上发送数据
sub module: TCP
summary: send test. use socket in state that can't send
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) in different state
version: v1 (2016-8-15)
@ -1101,8 +1101,8 @@ test cases:
6.PC send 100 * 1460 data to target,
7.在target上开始recv
sub module: TCP
summary: STA mode, recv buffer test
test environment: SSC_T1_1
summary: STA mode, TCP recv buffer test
test environment: SSC_T1_6
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) in different state
version: v2 (2016-10-19)
@ -1166,8 +1166,8 @@ test cases:
CONNECT<random_port>,<target_ip> ,tcp 连接创建成功创建socket4 \n10.target1 查询the socket
information"
sub module: TCP
summary: STA mode, get active socket info test
test environment: SSC_T1_1
summary: STA mode, TCP get active socket info test
test environment: SSC_T1_6
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) in different state
version: v1 (2016-8-15)
@ -1239,7 +1239,7 @@ test cases:
12.target1上使用步骤2创建的socket去连接 PC的ip<test_tcp_port1>
sub module: TCP
summary: AP mode, connect test. use socket in state that can't connect
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) in different state
version: v1 (2016-8-15)
@ -1299,7 +1299,7 @@ test cases:
9.target1上使用不存在socket,创建TCP 监听
sub module: TCP
summary: AP mode, server listen test. use socket in state that can't listen
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) in different state
version: v1 (2016-8-15)
@ -1348,8 +1348,8 @@ test cases:
6.PC send 100 * 1460 data to 8266,
7.target重新调用recv
sub module: TCP
summary: AP mode, recv buffer test
test environment: SSC_T1_1
summary: AP mode, TCP recv buffer test
test environment: SSC_T1_7
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) in different state
version: v2 (2016-10-19)
@ -1413,8 +1413,8 @@ test cases:
CONNECT<random_port>,<target_ip> ,tcp 连接创建成功创建socket4 \n10.target1 查询the socket
information"
sub module: TCP
summary: AP mode, get active socket info test
test environment: SSC_T1_1
summary: AP mode, TCP get active socket info test
test environment: SSC_T1_7
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) in different state
version: v1 (2016-8-15)
@ -1478,7 +1478,7 @@ test cases:
11.target1 abort socket1
sub module: TCP
summary: AP mode, espconn abort test
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: use TCP SAP (socket/espconn API) in different state
version: v1 (2016-8-15)
@ -1501,7 +1501,7 @@ test cases:
steps: 1.lev -N -t GET
sub module: TCP
summary: STA mode, max connections number query
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket option test
version: v1 (2016-8-15)
@ -1542,7 +1542,7 @@ test cases:
5.lev -N -t SET -n 8
sub module: TCP
summary: STA mode, max connections number set
test environment: SSC_T1_1
test environment: SSC_T1_5
test point 1: basic function
test point 2: socket option test
version: v1 (2016-8-15)
@ -1613,7 +1613,7 @@ test cases:
10.target1上使用步骤5创建的socket4去连接 pc_ip_wifi的iptest_tcp_port1,未连接成功
sub module: TCP
summary: STA mode, max connections fucntion verify
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket option test
version: v1 (2016-8-15)
@ -1674,7 +1674,7 @@ test cases:
9.target1上lev -N -t SET -n 8
sub module: TCP
summary: STA mode, max connections set interact with TCP connect and send
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket option test
version: v1 (2016-8-15)
@ -1716,7 +1716,7 @@ test cases:
5.target1上lev -A -s <sock1> -t SET -n 4
sub module: TCP
summary: STA mode, max TCP connection allowed by server test
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket option test
version: v1 (2016-8-15)
@ -1761,7 +1761,7 @@ test cases:
-K -s <sock1> -t GET \n6.lev -K -s <sock1> -t SET -i 30 -d 3 -c 2\n7.等待30s"
sub module: TCP
summary: STA mode, keep alive test
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket option test
version: v1 (2016-8-15)
@ -1820,7 +1820,7 @@ test cases:
-K -s <sock1> -t GET \n6.lev -K -s <sock1> -t SET -i 30 -d 3 -c 2\n7.PC往8266发送数据\n8.8266往PC上发送数据\n9.PC往8266发送146000数据\n10.8266往PC上发送1460*100数据\n11.等待30s"
sub module: TCP
summary: STA mode, keep alive interact with TCP send
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket option test
version: v1 (2016-8-15)
@ -1843,7 +1843,7 @@ test cases:
steps: 1.lev -N -t GET
sub module: TCP
summary: AP mode, max connections number query
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: socket option test
version: v1 (2016-8-15)
@ -1884,7 +1884,7 @@ test cases:
5.lev -N -t SET -n 8
sub module: TCP
summary: AP mode, max connections number set
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: socket option test
version: v1 (2016-8-15)
@ -1955,7 +1955,7 @@ test cases:
10.target1上使用步骤5创建的socket4去连接 pc_ip_wifi的iptest_tcp_port1,未连接成功
sub module: TCP
summary: AP mode, max connections fucntion verify
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: socket option test
version: v1 (2016-8-15)
@ -2016,7 +2016,7 @@ test cases:
9.target1上lev -N -t SET -n 8
sub module: TCP
summary: AP mode, max connections set interact with TCP connect and send
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: socket option test
version: v1 (2016-8-15)
@ -2059,7 +2059,7 @@ test cases:
5.target1上lev -A -s <sock1> -t SET -n 4
sub module: TCP
summary: AP mode, max TCP connection allowed by server test
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: socket option test
version: v1 (2016-8-15)
@ -2105,7 +2105,7 @@ test cases:
-K -s <sock1> -t GET \n6.lev -K -s <sock1> -t SET -i 30 -d 3 -c 2\n7.等待30s"
sub module: TCP
summary: AP mode, keep alive test
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: socket option test
version: v1 (2016-8-15)
@ -2165,7 +2165,7 @@ test cases:
-K -s <sock1> -t GET \n6.lev -K -s <sock1> -t SET -i 30 -d 3 -c 2\n7.PC往8266发送数据\n8.8266往PC上发送数据\n9.PC往8266发送146000数据\n10.8266往PC上发送1460*100数据\n11.等待30s"
sub module: TCP
summary: AP mode, keep alive interact with TCP send
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: socket option test
version: v1 (2016-8-15)
@ -2213,7 +2213,7 @@ test cases:
6.8266往PC上发送5字节数据
sub module: TCP
summary: do TCP send after WIFI disconnected
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: TCP handling abnormal event
version: v1 (2016-8-15)
@ -2261,7 +2261,7 @@ test cases:
6.关闭建立的socket1连接
sub module: TCP
summary: "close TCP socket after WIFI \ndisconnected"
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: TCP handling abnormal event
version: v1 (2016-8-15)
@ -2305,7 +2305,7 @@ test cases:
\n6.8266往PC上发送5字节数据"
sub module: TCP
summary: do TCP send after mode changed
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: TCP handling abnormal event
version: v1 (2016-8-15)
@ -2349,7 +2349,7 @@ test cases:
\n6.关闭建立的socket1连接"
sub module: TCP
summary: close TCP socket after mode changed
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: TCP handling abnormal event
version: v1 (2016-8-15)
@ -2399,7 +2399,7 @@ test cases:
6.target1上使用socket1发送数据等待 90 分钟
sub module: TCP
summary: do TCP send after PC NIC disabled
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: TCP handling abnormal event
version: v1 (2016-8-15)
@ -2442,7 +2442,7 @@ test cases:
PC的iptest_tcp_port1\n4.PC与target1创建好TCP 连接有ACCEPT\n5.PC上网卡禁止掉 \n6.关闭建立的socket1连接"
sub module: TCP
summary: close TCP socket after PC NIC disabled
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: TCP handling abnormal event
version: v1 (2016-8-15)
@ -2492,7 +2492,7 @@ test cases:
ip \n7.查询sta ip 地址是否生效\n8.8266往PC上发送5字节数据"
sub module: TCP
summary: do TCP send after IP changed
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: TCP handling abnormal event
version: v1 (2016-8-15)
@ -2542,7 +2542,7 @@ test cases:
ip \n7.查询sta ip 地址是否生效\n8.关闭建立的socket1连接"
sub module: TCP
summary: close TCP socket after IP changed
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: TCP handling abnormal event
version: v1 (2016-8-15)
@ -2594,7 +2594,7 @@ test cases:
7.8266往PC socket1上发送5字节数据
sub module: TCP
summary: do TCP send after socket changed
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: TCP handling abnormal event
version: v1 (2016-8-15)
@ -2646,7 +2646,7 @@ test cases:
7.关闭socket2连接
sub module: TCP
summary: close TCP send after socket changed
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: TCP handling abnormal event
version: v1 (2016-8-15)
@ -2683,7 +2683,7 @@ test cases:
2. target try to connect to TCP server with PC NIC IP
sub module: TCP
summary: PC do not reply TCP SYN of target
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: TCP connect and disconnect abnormal case
version: v1 (2015-8-15)
@ -2747,7 +2747,7 @@ test cases:
10.等待30s
sub module: TCP
summary: Test socket with so_keepalive option
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -2778,7 +2778,7 @@ test cases:
2.target1上创建TCP socket,bind test_udp_port1
sub module: TCP
summary: Test socket with so_reuseaddr option closed on TCP submodule
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -2830,7 +2830,7 @@ test cases:
sub module: TCP
summary: Test socket with so_reuseaddr option opened that close TCP connection not
react immediately on ESP32
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -2862,7 +2862,7 @@ test cases:
sub module: TCP
summary: Test socket with so_reuseaddr option opened that build two tcp sockets
by binding same ip and port on ESP32
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -2893,7 +2893,7 @@ test cases:
- - R PC_COM C OK
- - SSC SSC1 soc -S -s <sock1> -l 5000
- - P SSC1 RE SEND:\d+,OK
- - SSC SSC1 soc -S -s <sock1> -l 5000
- - SSC SSC1 soc -S -s <sock1> -l 5000 -n 4
- - P SSC1 RE SEND:\d+,ERROR,11
execution time: 0.0
expected result: |-
@ -2923,7 +2923,7 @@ test cases:
10.target1 send 5000 bytes to PC
sub module: TCP
summary: Test socket with so_sndtimeo option on ESP32
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -2978,7 +2978,7 @@ test cases:
8.PC send 5 bytes to target1
sub module: TCP
summary: Test socket with so_rcvtimeo option
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -3017,7 +3017,7 @@ test cases:
4.target1上使用步骤2创建的socket去连接 PC的iprandom_port, 获取 error code
sub module: TCP
summary: Test socket with so_error option
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -3066,7 +3066,7 @@ test cases:
7.查询空闲ram
sub module: TCP
summary: Test socket with so_linger option
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -3115,7 +3115,7 @@ test cases:
sub module: TCP
summary: Test socket with so_reuseaddr option opened that close TCP connection not
react immediately on 8266_RTOS
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -3148,7 +3148,7 @@ test cases:
sub module: TCP
summary: Test socket with so_reuseaddr option opened that build two tcp sockets
by binding same ip and port on 8266_RTOS
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -3209,7 +3209,7 @@ test cases:
10.target1 send 1500 bytes to PC
sub module: TCP
summary: Test socket with so_sndtimeo option on 8266_RTOS
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -3262,7 +3262,7 @@ test cases:
8.关闭socket
sub module: TCP
summary: Test socket with Maxconnect option
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -3311,7 +3311,7 @@ test cases:
7.关闭socket
sub module: TCP
summary: Test socket with MaxConnectNum option
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -3356,7 +3356,7 @@ test cases:
6.等待30s
sub module: TCP
summary: Test socket with Registtime option
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -3393,7 +3393,7 @@ test cases:
4.target1上对步骤2创建的socket设置 Abort 属性
sub module: TCP
summary: Test socket with Abort option
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -3439,7 +3439,7 @@ test cases:
sub module: TCP
summary: Test socket with so_reuseaddr option opened that close TCP connection not
react immediately on 8266_NonOS
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -3469,7 +3469,7 @@ test cases:
sub module: TCP
summary: Test socket with so_reuseaddr option opened that build two tcp sockets
by binding same ip and port on 8266_NonOS
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -3506,7 +3506,7 @@ test cases:
Loop executing step 1
sub module: TCP
summary: test possible TCP connect/disconnect method
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: function + stress
test point 2: TCP connect and disconnect test
version: v2 (2016-11-15)
@ -3584,7 +3584,7 @@ test cases:
2. PC send random length data to target
sub module: TCP
summary: send random length segment to target
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: stable
test point 2: TCP stable test
version: v2 (2016-11-15)
@ -3716,6 +3716,39 @@ test cases:
test point 1: stress
test point 2: TCP stress test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_TCP_5106
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stable
cmd set:
- TCPStress/TCPRandomSend
- - delay_config = [0, 0.01, 0.1, 0.5, 1]
- - dummy
- - send_count = 1000
- - ''
- - test_time = 300
- - ''
execution time: 12.0
expected result: |-
1. succeed
2. succeed
initial condition: T1_ETH
level: Integration
module: TCPIP
steps: |-
1. create TCP connection
2. PC send random length data to target
sub module: TCP
summary: send random length segment to target for Ethernet
test environment: ETH_T1_1
test point 1: stable
test point 2: TCP stable test
version: v2 (2016-11-15)
- CI ready: 'Yes'
ID: TCPIP_TCP_5201
SDK: |-
@ -3751,7 +3784,7 @@ test cases:
3. do send/recv on all tcp connections
sub module: TCP
summary: TCP send/recv stress test
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: stress
test point 2: TCP stress test
version: v2 (2016-11-15)
@ -3788,7 +3821,7 @@ test cases:
2. send specified pattern on both direction
sub module: TCP
summary: TCP send/recv data validation
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: stress
test point 2: TCP stress test
version: v2 (2016-11-15)
@ -3827,6 +3860,43 @@ test cases:
test point 1: stress
test point 2: TCP stress test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_TCP_5204
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stress
cmd set:
- TCPStress/TCPDataValidation
- - test_time = 1440
- - dummy
- - tx_enable = True
- - ''
- - rx_enable = True
- - ''
- - conn_num = 1
- - ''
- - send_len = 1024
- - ''
execution time: 24.0
expected result: |-
1. succeed
2. verify reciveid data on target and PC succeed
initial condition: T1_ETH
level: Integration
module: TCPIP
steps: |-
1. create TCP connection
2. send specified pattern on both direction
sub module: TCP
summary: TCP send/recv data validation for Ethernet
test environment: ETH_T1_1
test point 1: stress
test point 2: TCP stress test
version: v2 (2016-11-15)
- CI ready: 'No'
ID: TCPIP_TCP_5301
SDK: |-
@ -3937,7 +4007,7 @@ test cases:
Loop for step 1-2
sub module: TCP
summary: TCP throughput Tx for Ethernet
test environment: SSC_T1_1
test environment: ETH_T1_1
test point 1: stress
test point 2: TCP stress test
version: v1 (2016-8-15)
@ -3975,7 +4045,7 @@ test cases:
Loop for step 1-2
sub module: TCP
summary: TCP throughput Rx for Ethernet
test environment: SSC_T1_1
test environment: ETH_T1_1
test point 1: stress
test point 2: TCP stress test
version: v1 (2016-8-15)
@ -4013,7 +4083,7 @@ test cases:
Loop for step 1-3
sub module: TCP
summary: Eth random close while sending packets
test environment: SSC_T1_1
test environment: ETH_T1_1
test point 1: stress
test point 2: TCP stress test
version: v1 (2016-8-15)
@ -4051,7 +4121,7 @@ test cases:
3. send TCP packet
4. calculate the troughput
sub module: TCP
summary: STA TCP throughput while connecting with softAP
summary: STA TCP throughput Tx while connected with softAP
test environment: SSC_T2_ShieldBox2
test point 1: Performance test
test point 2: TCP throughput
@ -4090,11 +4160,51 @@ test cases:
3. send TCP packet
4. calculate the troughput
sub module: TCP
summary: STA TCP throughput while connecting with softAP
summary: STA TCP throughput Rx while connected with softAP
test environment: SSC_T2_ShieldBox2
test point 1: Performance test
test point 2: TCP throughput
version: v1 (2016-10-18)
- CI ready: 'No'
ID: TCPIP_TCP_5701
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stress
cmd set:
- StableTest/EthGetIP
- - test_count = 5000
- [dummy]
comment: ''
execution time: 5.0
expected result: '1. succeed
2. succeed
3. succeed
4. succeed'
initial condition: None
initial condition description (auto): none
level: Integration
module: TCPIP
steps: |-
1. reboot
2. open eth
3. delay 10s
4. ip query
sub module: TCP
summary: Eth get ip test
test environment: ETH_T1_1
test point 1: stress
test point 2: TCP stress test
version: v1 (2016-8-15)
- CI ready: 'No'
ID: TCPIP_TCP_6001
SDK: ESP32_IDF, 8266_NonOS, 8266_RTOS

View file

@ -35,7 +35,7 @@ test cases:
4.target1上创建TCP socket3, target_udp_port1
sub module: UDP
summary: STA mode, udp bind test. use different ip, port
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: use UDP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -81,7 +81,7 @@ test cases:
5.target1上使用步骤3创建的socket1往pc_ip2test_tcp_port2上发送10字节数据
sub module: UDP
summary: STA mode, sendto test. use different ip, port
test environment: SSC_T1_1
test environment: SSC_T1_9
test point 1: basic function
test point 2: use UDP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -132,7 +132,7 @@ test cases:
6.target1上使用步骤2创建的socket1往pc_iptest_tcp_port1上发送1472*10字节数据
sub module: UDP
summary: STA mode, sendto test with different length
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: use UDP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -176,7 +176,7 @@ test cases:
5.target1上使用步骤2创建的socket1往pc_iptest_tcp_port1上发送1473字节数据
sub module: UDP
summary: STA mode, sendto test with different length
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: use UDP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -229,7 +229,7 @@ test cases:
7.PC往8266上发送1472字节数据
sub module: UDP
summary: STA mode, recvfrom basic test
test environment: SSC_T1_1
test environment: SSC_T1_9
test point 1: basic function
test point 2: use UDP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -261,7 +261,7 @@ test cases:
2.关闭socket1
sub module: UDP
summary: STA mode, close UDP sockets test
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: use UDP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -305,7 +305,7 @@ test cases:
5.target1上UDP传输Bind socket5,本地ip target_udp_port5
sub module: UDP
summary: STA mode, create max udp socket test
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: use UDP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -336,8 +336,8 @@ test cases:
1.target1上UDP传输Bind socket1,本地ip target_udp_port1
2.target1上查询创建socket信息
sub module: UDP
summary: STA mode, get active socket info test
test environment: SSC_T1_1
summary: STA mode, UDP get active socket info test
test environment: SSC_T1_6
test point 1: basic function
test point 2: use UDP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -377,7 +377,7 @@ test cases:
4.target1上创建TCP socket3, target_udp_port1
sub module: UDP
summary: AP mode, udp bind test. use different ip, port
test environment: SSC_T1_1
test environment: SSC_T1_8
test point 1: basic function
test point 2: use UDP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -430,7 +430,7 @@ test cases:
5.target1上使用步骤3创建的socket1往pc_ip2test_tcp_port2上发送10字节数据
sub module: UDP
summary: AP mode, sendto test. use different ip, port
test environment: SSC_T2_1
test environment: SSC_T2_2
test point 1: basic function
test point 2: use UDP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -482,7 +482,7 @@ test cases:
6.target1上使用步骤2创建的socket1往pc_iptest_tcp_port1上发送1472*10字节数据
sub module: UDP
summary: AP mode, sendto test with different length
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: use UDP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -526,7 +526,7 @@ test cases:
5.target1上使用步骤2创建的socket1往pc_iptest_tcp_port1上发送1473字节数据
sub module: UDP
summary: AP mode, sendto test with different length
test environment: SSC_T1_1
test environment: SSC_T1_7
test point 1: basic function
test point 2: use UDP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -583,7 +583,7 @@ test cases:
7.PC往8266上发送1472字节数据
sub module: UDP
summary: AP mode, recvfrom basic test
test environment: SSC_T2_1
test environment: SSC_T2_2
test point 1: basic function
test point 2: use UDP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -615,7 +615,7 @@ test cases:
2.关闭socket1
sub module: UDP
summary: AP mode, close UDP sockets test
test environment: SSC_T1_1
test environment: SSC_T1_8
test point 1: basic function
test point 2: use UDP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -659,7 +659,7 @@ test cases:
5.target1上UDP传输Bind socket5,本地ip target_udp_port5
sub module: UDP
summary: AP mode, create max udp socket test
test environment: SSC_T1_1
test environment: SSC_T1_8
test point 1: basic function
test point 2: use UDP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -690,8 +690,8 @@ test cases:
1.target1上UDP传输Bind socket1,本地ip target_udp_port1
2.target1上查询创建socket信息
sub module: UDP
summary: AP mode, get active socket info test
test environment: SSC_T1_1
summary: AP mode, UDP get active socket info test
test environment: SSC_T1_8
test point 1: basic function
test point 2: use UDP SAP (socket/espconn API) with different parameter
version: v1 (2016-8-15)
@ -744,8 +744,8 @@ test cases:
7.PC往8266上发送1472字节数据
8.PC往8266上发送1472字节数据
sub module: UDP
summary: STA mode, recv buffer test
test environment: SSC_T1_1
summary: STA mode, UDP recv buffer test
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: use UDP SAP (socket/espconn API) in different state
version: v2 (2016-10-19)
@ -800,8 +800,8 @@ test cases:
7.PC往8266上发送1472字节数据
8.PC往8266上发送1472字节数据
sub module: UDP
summary: AP mode, recv buffer test
test environment: SSC_T1_1
summary: AP mode, UDP recv buffer test
test environment: SSC_T1_7
test point 1: abnormal/special use
test point 2: use UDP SAP (socket/espconn API) in different state
version: v2 (2016-10-19)
@ -846,7 +846,7 @@ test cases:
5.target1上使用步骤2创建的socket1往pc_iptest_tcp_port1上发送5字节数据
sub module: UDP
summary: do UDP send after WIFI disconnected
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: UDP handling abnormal event
version: v1 (2016-8-15)
@ -891,7 +891,7 @@ test cases:
5.关闭建立的socket1连接
sub module: UDP
summary: "close UDP socket after WIFI \ndisconnected"
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: UDP handling abnormal event
version: v1 (2016-8-15)
@ -933,7 +933,7 @@ test cases:
mode \n5.8266往PC上发送5字节数据"
sub module: UDP
summary: do UDP send after mode changed
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: UDP handling abnormal event
version: v1 (2016-8-15)
@ -975,7 +975,7 @@ test cases:
mode \n5.关闭建立的socket1连接"
sub module: UDP
summary: close UDP socket after mode changed
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: UDP handling abnormal event
version: v1 (2016-8-15)
@ -1017,7 +1017,7 @@ test cases:
\n5.关闭建立的socket1连接"
sub module: UDP
summary: close UDP socket after PC NIC disabled
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: UDP handling abnormal event
version: v1 (2016-8-15)
@ -1065,7 +1065,7 @@ test cases:
1\n5.设置sta ip \n6.查询sta ip 地址是否生效\n7.8266往PC上发送5字节数据"
sub module: UDP
summary: do UDP send after IP changed
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: UDP handling abnormal event
version: v1 (2016-8-15)
@ -1113,7 +1113,7 @@ test cases:
1\n5.设置sta ip \n6.查询sta ip 地址是否生效\n7.关闭建立的socket1连接"
sub module: UDP
summary: close UDP socket after IP changed
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: abnormal/special use
test point 2: UDP handling abnormal event
version: v1 (2016-8-15)
@ -1144,7 +1144,7 @@ test cases:
2.target1上创建UDP socket,bind test_udp_port1
sub module: UDP
summary: Test socket with so_reuseaddr option closed on UDP submodule
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -1176,7 +1176,7 @@ test cases:
sub module: UDP
summary: Test socket with so_reuseaddr option opened that build two udp sockets
by binding same port on ESP32
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -1209,7 +1209,7 @@ test cases:
sub module: UDP
summary: Test socket with so_reuseaddr option opened that build two udp sockets
by binding same port on 8266_RTOS
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: basic function
test point 2: socket test with different option
version: v1 (2016-8-15)
@ -1248,7 +1248,7 @@ test cases:
3. do send/recv on all udp
sub module: UDP
summary: UDP send/recv stress test
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: stress
test point 2: UDP stress test
version: v2 (2016-11-15)
@ -1285,7 +1285,7 @@ test cases:
2. create UDP and recv data for several seconds
sub module: UDP
summary: UDP loss rate on DUT Rx
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: Performance test
test point 2: UDP stress test
version: v1 (2016-10-18)
@ -1322,7 +1322,7 @@ test cases:
2. create UDP and recv data for several seconds
sub module: UDP
summary: UDP loss rate on DUT Tx
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: Performance test
test point 2: UDP stress test
version: v1 (2016-10-18)
@ -1337,7 +1337,7 @@ test cases:
category: Stress
cmd set:
- UDPStress/UDPBroadcast
- - test_time = 0.2
- - test_time = 30
- - dummy
- - send_len = 20
- - ''
@ -1359,7 +1359,7 @@ test cases:
2. create UDP and recv data for several seconds
sub module: UDP
summary: UDP broadcase loss rate on DUT Rx
test environment: SSC_T1_1
test environment: SSC_T1_6
test point 1: Performance test
test point 2: UDP stress test
version: v1 (2016-10-18)
@ -1480,7 +1480,7 @@ test cases:
sub module: UDP
summary: STA connect to softAP, STA send UDP to softAP, calculate the UDP lose on
softAP
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: Performance test
test point 2: UDP stress test
version: v1 (2016-10-18)
@ -1520,7 +1520,7 @@ test cases:
sub module: UDP
summary: STA connect to softAP, softAP send UDP to STA, calculate the UDP lose on
STA
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: Performance test
test point 2: UDP stress test
version: v1 (2016-10-18)
@ -1634,7 +1634,7 @@ test cases:
Loop for step 1-2
sub module: UDP
summary: UDP throughput Tx for Ethernet
test environment: SSC_T1_1
test environment: ETH_T1_1
test point 1: stress
test point 2: UDP stress test
version: v1 (2016-8-15)
@ -1672,7 +1672,7 @@ test cases:
Loop for step 1-2
sub module: UDP
summary: UDP throughput Rx for Ethernet
test environment: SSC_T1_1
test environment: ETH_T1_1
test point 1: stress
test point 2: UDP stress test
version: v1 (2016-8-15)
@ -1710,7 +1710,7 @@ test cases:
3. DUT calculate the packet lose rate
sub module: UDP
summary: UDP loss rate on DUT Rx for Eth
test environment: SSC_T1_1
test environment: ETH_T1_1
test point 1: Performance test
test point 2: UDP stress test
version: v1 (2016-10-18)
@ -1748,7 +1748,7 @@ test cases:
3. send UDP packet
4. calculate the troughput
sub module: UDP
summary: STA UDP throughput while connecting with softAP
summary: STA UDP throughput Tx while connected with softAP
test environment: SSC_T2_ShieldBox2
test point 1: Performance test
test point 2: UDP throughput
@ -1787,7 +1787,7 @@ test cases:
3. send UDP packet
4. calculate the troughput
sub module: UDP
summary: STA UDP throughput while connecting with softAP
summary: STA UDP throughput Rx while connected with softAP
test environment: SSC_T2_ShieldBox2
test point 1: Performance test
test point 2: UDP throughput

View file

@ -39,7 +39,7 @@ test cases:
为target1_mac\n6.target1 设置softAP mode 下的mac 为target1_ap_mac\n"
sub module: MAC Address
summary: set mac, query mac
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: mac address function test
version: v1 (2016-8-15)
@ -93,7 +93,7 @@ test cases:
jap target1\n8.target1 查询连接到的sta \n9.target2 设置sta mode 下的mac 为 target2_mac\n"
sub module: MAC Address
summary: set mac and do scan/JAP/SAP
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: mac address function test
version: v1 (2016-8-15)

View file

@ -51,7 +51,7 @@ test cases:
和pwd,加密方式 t 5 错误的加密方式\n12.target2上查询 target_ssid"
sub module: WIFI Connect
summary: station SAP+JAP test, different encryption
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: SAP/JAP with different config
version: v1 (2016-8-15)
@ -101,7 +101,7 @@ test cases:
6.target 2 上查询target_ssid
sub module: WIFI Connect
summary: station SAP+JAP test, different channel
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: SAP/JAP with different config
version: v1 (2016-8-15)
@ -150,7 +150,7 @@ test cases:
4.target 2上scan target_ap_mac
sub module: WIFI Connect
summary: station SAP+JAP test, ssid hidden
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: SAP/JAP with different config
version: v1 (2016-8-15)
@ -192,7 +192,7 @@ test cases:
4.PC WIFI CONNECT target1
sub module: WIFI Connect
summary: station SAP test, max allowed sta
test environment: SSC_T2_1
test environment: SSC_T2_2
test point 1: basic function
test point 2: SAP/JAP with different config
version: v1 (2016-8-15)
@ -232,7 +232,7 @@ test cases:
4.查询target1 JAP 是DISCONN
sub module: WIFI Connect
summary: JAP query test
test environment: SSC_T1_1
test environment: SSC_T1_5
test point 1: basic function
test point 2: query JAP status
version: v1 (2016-8-15)
@ -265,10 +265,93 @@ test cases:
2.target 1上查询到跟设置AP时一致
sub module: WIFI Connect
summary: AP config query test
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: query AP config
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: WIFI_CONN_0302
SDK: |-
8266_NonOS
8266_RTOS
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 sta -S
- - R SSC1 C +SCAN_DONE:OK
- - SSC SSC1 sta -C -s <ap_ssid> -p <ap_password>
- - P SSC1 C +JAP:CONNECTED
- P SSC1 C +SCANDONE
- - SSC SSC1 sta -D
- - R SSC1 C +QAP:OK
- - SSC SSC1 sta -C -s <ap_ssid> -p <ap_password>
- - ''
- - SSC SSC1 sta -S
- - P SSC1 C +JAP:CONNECTED
- P SSC1 C +SCANDONE
execution time: 0.0
expected result: |
2. scan succeed, JAP succeed
5. JAP succeed, scan succeed
initial condition: STAM1
level: Integration
module: WIFI MAC
steps: |
1. target 1 STA join AP
2. target 1 STA scan before JAP succeed
3. target 1 quite AP
4. target 1 scan
5. target 1 JAP before scan succeed
sub module: WIFI Connect
summary: JAP during scan
test environment: SSC_T1_5
test point 1: interaction
test point 2: Conn interact with other WiFi operation
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: WIFI_CONN_0302
SDK: |-
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 sta -S
- - R SSC1 C +SCAN_DONE:OK
- - SSC SSC1 sta -C -s <ap_ssid> -p <ap_password>
- - P SSC1 C +JAP:CONNECTED
- P SSC1 C +SCANFAIL
- - SSC SSC1 sta -D
- - R SSC1 C +QAP:OK
- - SSC SSC1 sta -C -s <ap_ssid> -p <ap_password>
- - ''
- - SSC SSC1 sta -S
- - P SSC1 C +JAP:CONNECTED
- P SSC1 C +SCAN:ERROR
execution time: 0.0
expected result: |
2. scan failed, JAP succeed
5. JAP succeed, scan failed
initial condition: STAM1
level: Integration
module: WIFI MAC
steps: |
1. target 1 STA join AP
2. target 1 STA scan before JAP succeed
3. target 1 quite AP
4. target 1 scan
5. target 1 JAP before scan succeed
sub module: WIFI Connect
summary: JAP during scan
test environment: SSC_T1_5
test point 1: interaction
test point 2: Conn interact with other WiFi operation
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: WIFI_CONN_0401
SDK: |-
@ -319,7 +402,7 @@ test cases:
7.系统重启后target1 自动重连AP
sub module: WIFI Connect
summary: auto reconnect test
test environment: SSC_T1_1
test environment: SSC_T1_5
test point 1: basic function
test point 2: power on auto reconnect test
version: v1 (2016-8-15)
@ -383,7 +466,7 @@ test cases:
修改mode 为sta mode\n9.等待15starget1 修改mode 为softAP mode"
sub module: WIFI Connect
summary: reconnect policy test
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: reconnect policy test
version: v1 (2016-8-15)
@ -438,7 +521,7 @@ test cases:
6.target2 断开target1 连接
sub module: WIFI Connect
summary: will not do reconnect after manually disconnected
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: abnormal/special use
test point 2: reconnect policy test
version: v1 (2016-8-15)
@ -528,7 +611,7 @@ test cases:
4.查询到两个sta 连接到target1 上
sub module: WIFI Connect
summary: list stations connected to soft ap test
test environment: SSC_T2_1
test environment: SSC_T2_2
test point 1: basic function
test point 2: list SoftAP connected station
version: v1 (2016-8-15)
@ -686,7 +769,7 @@ test cases:
6. set target1 softap auth mode 0, wait sta connected
sub module: WIFI Connect
summary: test auth change event
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: wifi auth changed event test
version: v1 (2016-8-15)
@ -828,7 +911,7 @@ test cases:
5. target2 connect to target1 with correct password
sub module: WIFI Connect
summary: test wifi disconnect reason REASON_ASSOC_TOOMANY, REASON_HANDSHAKE_TIMEOUT
test environment: SSC_T2_1
test environment: SSC_T2_2
test point 1: basic function
test point 2: wifi disconnect reason test
version: v1 (2016-8-15)
@ -892,7 +975,7 @@ test cases:
4. check heap size
sub module: WIFI Connect
summary: wifi start and stop, heap size unchanged
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: wifi start and stop, heap size unchanged
version: v1 (2016-12-31)
@ -917,7 +1000,7 @@ test cases:
1. sta connect
sub module: WIFI Connect
summary: sta connect after WiFi stop
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -946,7 +1029,7 @@ test cases:
2. query sta state
sub module: WIFI Connect
summary: sta reconnect start and connect fail after WiFi stop
test environment: SSC_T1_1
test environment: SSC_T1_5
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -971,7 +1054,7 @@ test cases:
1. sta disconnect
sub module: WIFI Connect
summary: station disconnect after WiFi stop
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -996,7 +1079,7 @@ test cases:
1. query sta state
sub module: WIFI Connect
summary: query sta state after WiFi stop
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -1021,7 +1104,7 @@ test cases:
1. sta scan ssid and pwd
sub module: WIFI Connect
summary: sta scan after WiFi stop
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -1046,7 +1129,7 @@ test cases:
1. ap connect ssid and pwd
sub module: WIFI Connect
summary: ap connect after WiFi stop
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -1071,7 +1154,7 @@ test cases:
1. ap disconnect
sub module: WIFI Connect
summary: ap disconnect after WiFi stop
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -1096,7 +1179,7 @@ test cases:
1. ap list station
sub module: WIFI Connect
summary: ap list station after WiFi stop
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -1121,7 +1204,7 @@ test cases:
1. query ap config
sub module: WIFI Connect
summary: query ap config after WiFi stop
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -1158,7 +1241,7 @@ test cases:
4. ap set ssid and pwd
sub module: WIFI Connect
summary: ap set ssid and pwd after WiFi stop
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -1183,7 +1266,7 @@ test cases:
1. query mac
sub module: WIFI Connect
summary: query mac after WiFi stop
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -1215,8 +1298,8 @@ test cases:
2. set ap mac
3. set station mac
sub module: WIFI Connect
summary: set mac after WiFi stop
test environment: SSC_T1_1
summary: enable AP mode after WiFi stop and set AP mac
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -1248,8 +1331,8 @@ test cases:
2. set station mac
3. query station mac
sub module: WIFI Connect
summary: query mac after WiFi stop
test environment: SSC_T1_1
summary: enable STA mode after WiFi stop and set STA mac
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -1281,8 +1364,8 @@ test cases:
2. set station mac
3. set ap mac
sub module: WIFI Connect
summary: set mac after WiFi stop
test environment: SSC_T1_1
summary: enable STA mode after WiFi stop and set AP mac
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -1307,7 +1390,7 @@ test cases:
1. set channel
sub module: WIFI Connect
summary: set channel after WiFi stop
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -1336,7 +1419,7 @@ test cases:
2. query channel
sub module: WIFI Connect
summary: query channel after WiFi stop
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -1361,7 +1444,7 @@ test cases:
1. query current mode
sub module: WIFI Connect
summary: be AP mode after WiFi stop
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -1386,7 +1469,7 @@ test cases:
1. set STA mode
sub module: WIFI Connect
summary: set STA mode after WiFi stop
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -1411,7 +1494,7 @@ test cases:
1. set AP mode
sub module: WIFI Connect
summary: set ap mode after WiFi stop
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: use WiFi API after WiFi stop
version: v1 (2016-12-31)
@ -1448,7 +1531,7 @@ test cases:
4. wifi stop
sub module: WIFI Connect
summary: incorrect deinit stop flow
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: WiFi deinit and stop
version: v1 (2016-12-31)
@ -1485,7 +1568,7 @@ test cases:
4. wifi stop
sub module: WIFI Connect
summary: incorrect deinit start flow
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: WiFi deinit and start
version: v1 (2016-12-31)
@ -1537,8 +1620,8 @@ test cases:
7. wifi deinit
8. wifi start
sub module: WIFI Connect
summary: incorrect deinit stop flow
test environment: SSC_T1_1
summary: incorrect init start flow
test environment: SSC_T1_4
test point 1: basic function
test point 2: WiFi deinit and stop
version: v1 (2016-12-31)
@ -1782,7 +1865,7 @@ test cases:
2. 1 SSC connect with AP
3. check connection status within 24 hours
sub module: WIFI Connect
summary: connection stable
summary: WiFi STA connection stable test
test environment: SSC_T1_1
test point 1: stress + function
test point 2: connection keep alive stress test
@ -1819,7 +1902,7 @@ test cases:
3. SSC stop send pkt
4. SSC connect ap
sub module: WIFI Connect
summary: connection stable
summary: Switch channel when sending WiFi packets
test environment: SSC_T1_1
test point 1: stress
test point 2: connect ap
@ -1965,8 +2048,65 @@ test cases:
module: WIFI MAC
steps: 1. set sta mode 2. disconnect sta 3. sta connect ap
sub module: WIFI Connect
summary: sta connect ap
summary: STA connect to AP compatibility test
test environment: SSC_T1_IOT1
test point 1: Compatibility Test test point
test point 2: WIFI compatibility test
version: v1 (2016-10-23)
- CI ready: 'No'
ID: WIFI_CONN_0704
SDK: All
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 sta -C -s <wep_ap_ssid> -p <wep_ap_password>
- - R SSC1 C +JAP:OK
- R SSC1 NC +JAPAUTHCHANGED C +JAP:CONNECTED
execution time: 0
expected result: 1. sta connect ap suc and no +JAPAUTHCHANGED found
initial condition: STAM1
level: Integration
module: WIFI MAC
steps: 1. sta JAP
sub module: WIFI Connect
summary: sta connect wep encrypt ap
test environment: SSC_T1_WEP
test point 1: basic function
test point 2: ap connect test
version: v1 (2016-10-23)
- CI ready: 'No'
ID: WIFI_CONN_9902
SDK: All
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Performance
cmd set:
- WiFiStress/WifiStaConnectionHolder
- - test_count = 10
- - ''
- - retry_count = 1
- - ''
execution time: 1
expected result: |-
1. set SSC1 AP+STA mode, SSC2 AP mode, SSC3 STA mode
2. SSC3 connect SSC1
3. SSC2 random set ap channel
4. SSC1 connect SSC2
initial condition: T3_1
level: Integration
module: WIFI MAC
steps: |-
1. set mode suc
2. connect suc
3. set channel suc
4. connect suc
sub module: WIFI Connect
summary: STA keep connected with AP stable test
test environment: SSC_T3_1
test point 1: AP switch channel dut Connection holder Test test point
test point 2: WIFI Connection holder test
version: v1 (2016-10-23)

View file

@ -43,7 +43,7 @@ test cases:
6.target1断开AP
sub module: WIFI Mode
summary: mode switch test (sta mode)
test environment: SSC_T2_1
test environment: SSC_T2_3
test point 1: basic function
test point 2: wifi mode fucntion
version: v1 (2016-8-15)
@ -84,7 +84,7 @@ test cases:
4.target1 DISCONN AP
sub module: WIFI Mode
summary: mode switch test (AP mode)
test environment: SSC_T2_1
test environment: SSC_T2_3
test point 1: basic function
test point 2: wifi mode fucntion
version: v1 (2016-8-15)
@ -129,7 +129,7 @@ test cases:
5.target2 上查询target_ssid
sub module: WIFI Mode
summary: mode switch test (STA+AP mode)
test environment: SSC_T2_1
test environment: SSC_T2_3
test point 1: basic function
test point 2: wifi mode fucntion
version: v1 (2016-8-15)

View file

@ -33,7 +33,7 @@ test cases:
3.target2 scan <target_tmp_ssid>
sub module: WIFI Scan
summary: scan with scan config ssid
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: scan with different config
version: v1 (2016-8-15)
@ -66,7 +66,7 @@ test cases:
2.target2上查询<target_ap_mac>
sub module: WIFI Scan
summary: scan with scan config bssid
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: scan with different config
version: v1 (2016-8-15)
@ -107,7 +107,7 @@ test cases:
4.target2 上查询channel 6的<target_tmp_ssid>
sub module: WIFI Scan
summary: scan with scan config channel
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: scan with different config
version: v1 (2016-8-15)
@ -157,7 +157,7 @@ test cases:
6.target 2上查询<target_ap_mac>
sub module: WIFI Scan
summary: scan with scan config show hidden
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: scan with different config
version: v1 (2016-8-15)
@ -207,10 +207,60 @@ test cases:
6.target2 上查询不到<target_tmp_ssid>
sub module: WIFI Scan
summary: scan with several configs
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: basic function
test point 2: scan with different config
version: v1 (2016-8-15)
- CI ready: 'No'
ID: WIFI_SCAN_0201
SDK: ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 phy -S -o 1 -m b
- - R SSC1 C +SPHY:protocol
- - SSC SSC1 sta -S
- - R SSC1 P <ap_ssid_11b> P <ap_ssid_11g> P <ap_ssid_11n_20> P <ap_ssid_11n_40>
- - SSC SSC1 phy -S -o 1 -m g
- - R SSC1 C +SPHY:protocol
- - SSC SSC1 sta -S
- - R SSC1 P <ap_ssid_11b> P <ap_ssid_11g> P <ap_ssid_11n_20> P <ap_ssid_11n_40>
- - SSC SSC1 phy -S -o 1 -m n -b 20
- - R SSC1 C +SPHY:protocol
- - SSC SSC1 sta -S
- - R SSC1 P <ap_ssid_11b> P <ap_ssid_11g> P <ap_ssid_11n_20> P <ap_ssid_11n_40>
- - SSC SSC1 phy -S -o 1 -m n -b 40
- - R SSC1 C +SPHY:protocol
- - SSC SSC1 sta -S
- - R SSC1 P <ap_ssid_11b> P <ap_ssid_11g> P <ap_ssid_11n_20> P <ap_ssid_11n_40>
execution time: 0.0
expected result: |-
3. find all 3 ext APs
5. find all 3 ext APs
7. find all 3 ext APs
9. find all 3 ext APs
initial condition: STAM1
level: Integration
module: WIFI MAC
steps: |-
1. 3 ext APs in 11b, 11g, 11n mode
2. STA in 11b mode
3. do all channel scan
4. STA in 11g mode
5. do all channel scan
6. STA in 11n ht20 mode
7. do all channel scan
8. STA in 11n ht40 mode
9. do all channel scan
sub module: WIFI Scan
summary: STA in differnt PHY mode to scan AP in different PHY mode
test environment: SSC_T2_PhyMode
test point 1: basic function
test point 2: Scan in different mode and channel
version: v1 (2015-8-15)
- CI ready: 'No'
ID: WIFI_SCAN_0202
SDK: |-
@ -242,8 +292,8 @@ test cases:
2.target2 jap
3.target2 conn target1 by bssid
sub module: WIFI Scan
summary: do scan/JAP/SAP
test environment: SSC_T2_1
summary: do scan/JAP/SAP with bssid set config
test environment: SSC_T2_5
test point 1: basic function
test point 2: scan function test
version: v1 (2016-8-15)
@ -311,8 +361,8 @@ test cases:
11.target2 scan all channel jap target1
12.target2 jap target1
sub module: WIFI Scan
summary: do scan/JAP/SAP
test environment: SSC_T2_1
summary: do scan/JAP/SAP with scan method and weakest auth mode
test environment: SSC_T2_5
test point 1: basic function
test point 2: scan function test
version: v1 (2016-8-15)
@ -363,8 +413,8 @@ test cases:
6.target2 scan all channel and jap rssi > -1
7.target2 scan all channel and jap target1 rssi > -80
sub module: WIFI Scan
summary: do scan/JAP/SAP
test environment: SSC_T2_1
summary: do scan/JAP/SAP with scan method and weakest rssi
test environment: SSC_T2_5
test point 1: basic function
test point 2: scan function test
version: v1 (2016-8-15)
@ -403,8 +453,8 @@ test cases:
3.target2 scan ap all channel and jap target1 by auth
4.target2 scan ap all channel jap target1 by auth
sub module: WIFI Scan
summary: do scan/JAP/SAP
test environment: SSC_T2_1
summary: do scan/JAP/SAP with scan method and sort method
test environment: SSC_T2_5
test point 1: basic function
test point 2: scan function test
version: v1 (2016-8-15)
@ -456,7 +506,7 @@ test cases:
7.target1 scan type set to 5
sub module: WIFI Scan
summary: do active/passive scan
test environment: SSC_T1_1
test environment: SSC_T1_4
test point 1: basic function
test point 2: scan function test
version: v1 (2016-8-15)
@ -487,7 +537,7 @@ test cases:
2. do scan before scan finished
sub module: WIFI Scan
summary: reject scan request before scan finished
test environment: SSC_T1_1
test environment: SSC_T1_5
test point 1: interaction
test point 2: Scan interact with other WiFi operation
version: v1 (2015-8-15)
@ -533,7 +583,7 @@ test cases:
3. target 2 scan in AP channel in 11b.g,n,ht40 mode
sub module: WIFI Scan
summary: scan in congest channel
test environment: SSC_T2_1
test environment: SSC_T2_4
test point 1: interaction
test point 2: Scan interact with other WiFi operation
version: v1 (2015-8-15)
@ -573,7 +623,7 @@ test cases:
5. target 1 JAP before scan succeed
sub module: WIFI Scan
summary: scan during JAP
test environment: SSC_T1_1
test environment: SSC_T1_5
test point 1: interaction
test point 2: Scan interact with other WiFi operation
version: v1 (2015-8-15)
@ -617,7 +667,7 @@ test cases:
5. target 2 STA JAP before target 1 STA scan succeed
sub module: WIFI Scan
summary: scan during ext STA join SoftAP
test environment: SSC_T2_1
test environment: SSC_T2_5
test point 1: interaction
test point 2: Scan interact with other WiFi operation
version: v1 (2015-8-15)
@ -669,14 +719,17 @@ test cases:
- - ''
- - test_mode = "conn_by_bssid"
- - ''
execution time: 5.0
expected result: 2. connect success
execution time: 0.2
expected result: |-
1. all routers configure correctly
3. connect success
initial condition: None
level: Integration
module: WIFI MAC
steps: |-
1. 1 SSC target connect PC by Uart.
2. SSC target connect ap by bssid
1. Manually configure the two routers with the same ssid ,password and security mode
2. SSC1 target connect PC by Uart.
3. SSC target connect ap by the specified bssid
sub module: WIFI Scan
summary: connect specify ap test
test environment: SSC_T1_SCANSPECIFIED
@ -695,14 +748,19 @@ test cases:
- - ''
- - test_mode = "conn_max_rssi_ap"
- - ''
execution time: 5.0
expected result: 2. connect success
execution time: 0.2
expected result: |-
1. configure ap right
3. connect success
4. rssi value is the largest of the four routers
initial condition: None
level: Integration
module: WIFI MAC
steps: |-
1. 1 SSC target connect PC by Uart.
2. SSC connect max rssi ap.
1. Manually configure the four routers with the same ssid ,password and security mode
2. 1 SSC target connect PC by Uart.
3. SSC connect max rssi ap.
4. check connection ap's rssi value
sub module: WIFI Scan
summary: connect max rssi ap
test environment: SSC_T1_SCANSPECIFIED
@ -721,14 +779,19 @@ test cases:
- - ''
- - test_mode = "conn_most_security_ap"
- - ''
execution time: 5.0
expected result: 2. connect success
execution time: 0.2
expected result: |-
1. the routers are configured correctly
3. connect success
4. encryption mode is the highest in four routers
initial condition: None
level: Integration
module: WIFI MAC
steps: |-
1. 1 SSC target connect PC by Uart.
2. SSC connect max rssi ap
1. Manually configure the four routers with the same ssid ,password and different security mode
2. target1 connect PC by Uart.
3. target1 connect the highest encryption mode ap
4. check connection ap's security mode
sub module: WIFI Scan
summary: connect most security ap
test environment: SSC_T1_SCANSPECIFIED
@ -747,14 +810,17 @@ test cases:
- - ''
- - test_mode = "conn_setting_ap"
- - ''
execution time: 5.0
expected result: 2. connect success
execution time: 0.2
expected result: |-
1. the routers are configured correctly
3. connect success
initial condition: None
level: Integration
module: WIFI MAC
steps: |-
1. 1 SSC target connect PC by Uart.
2. SSC connect setting ap
1. Manually configure the four routers with the same ssid different password
2. target1 connect PC by Uart.
3. target1 connect setting ap
sub module: WIFI Scan
summary: connect setting ap
test environment: SSC_T1_SCANSPECIFIED
@ -775,17 +841,23 @@ test cases:
- - ''
- - apc_num_list = [1,3]
- - ''
execution time: 5.0
expected result: 2. connect success
execution time: 0.5
expected result: |-
1. the routers are configured correctly
3. ap1 power on
4. connect success
5. ap2 power on and ap1 power off
6. connect success
initial condition: None
level: Integration
module: WIFI MAC
steps: |-
1. 1 SSC target connect PC by Uart.
2. ap1 power on by apc
3. SSC connect ap
4. ap1 power off and ap2 power on
5. SSC auto connect ap2.
1. Manually configure the two routers with the same ssid ,password different security mode
2. target1 connect PC by Uart.
3. ap1 power on by apc
4. atrget1 connect ap
5. ap1 power off and ap2 power on
6. atrget1 auto connect ap2.
sub module: WIFI Scan
summary: reconnect same ssid ap
test environment: SSC_T1_SCANSPECIFIED
@ -806,14 +878,21 @@ test cases:
- - ''
- - rssi_threshold = 60
- - ''
execution time: 5.0
expected result: 2. connect success
- - low_rssi_num = 1
- - ''
execution time: 0.3
expected result: |-
1. the routers are configured correctly
3. connect success
4. connect to the correct ap
initial condition: None
level: Integration
module: WIFI MAC
steps: |-
1. 1 SSC target connect PC by Uart.
2. SSC1 connect ap
1. manuall configure two routers with the same ssid password and below rssi_threshold ap's channel at the front
2. target1 connect PC by Uart.
3. atrget1 connect ap
4. check connection ap's bssid
sub module: WIFI Scan
summary: quick connect ap
test environment: SSC_T1_SCANSPECIFIED
@ -824,22 +903,26 @@ test cases:
ID: WIFI_SCAN_5207
SDK: ESP32_IDF
Test App: SSC
auto test: 'Yes'
auto test: 'No'
category: Stress
cmd set:
- WiFiStress/WifiScanOptimize
- - test_times = 10
- - ''
execution time: 5.0
expected result: 2. connect success
cmd set: ''
execution time: 0.3
expected result: |-
1. the routers are configured correctly
3. set suc
5. burn suc
6. set mode ok and SSC connected to the open security mode ap auto
initial condition: None
level: Integration
module: WIFI MAC
steps: |-
1. 1 SSC target connect PC by Uart.
2. make menuconfig
3. write ap ssid
4. connect ap auto
1. configure four router with the same ssid and one of them security mode is open
2. target1 connect PC by Uart.
3. set the ssid of the router in the manuconfig but not the password
4. save the setting and compile
5. burn bin files
6. set target1 to sta mode
7. loop 1,2,3,4 ten times
sub module: WIFI Scan
summary: connect open security ap
test environment: SSC_T1_SCANSPECIFIED

View file

@ -10,18 +10,78 @@ test environment:
test environment detail: |-
PC has 2 wired NIC connected to AP.
PC has 1 WiFi NIC.
1 SSC target connect with PC by UART.
1 SSC DUT connect with PC by UART.
- tag: ETH_T1_1
<<: *TEST_ENV
Target Count: 1
test environment detail: |-
PC connected to AP by wired NIC.
1 ETH DUT connect with PC by UART, connect to AP by wired NIC.
- tag: SSC_T1_2
<<: *TEST_ENV
Target Count: 1
test environment detail: |-
Able to access WAN after connect to AP.
1 SSC target connect with PC by UART.
1 SSC DUT connect with PC by UART.
- tag: SSC_T1_3
<<: *TEST_ENV
Target Count: 1
test environment detail: PC has one BT adapter (dongle). 1 SSC target connect with
test environment detail: PC has one BT adapter (dongle). 1 SSC DUT connect with
PC by UART.
- tag: SSC_T1_4
<<: *TEST_ENV
Target Count: 1
test environment detail: |-
1 SSC DUT connect with PC by UART.
- tag: SSC_T1_5
<<: *TEST_ENV
Target Count: 1
test environment detail: |-
1 SSC DUT connect with PC by UART.
AP placed near DUT.
- tag: SSC_T1_6
<<: *TEST_ENV
Target Count: 1
test environment detail: |-
1 SSC DUT connect with PC by UART.
AP placed near DUT.
PC has 1 wired NIC connected to AP.
- tag: SSC_T1_7
<<: *TEST_ENV
Target Count: 1
test environment detail: |-
1 SSC DUT connect with PC by UART.
PC has 1 WiFi NIC.
AP placed near DUT and PC.
- tag: SSC_T1_8
<<: *TEST_ENV
Target Count: 1
test environment detail: |-
1 SSC DUT connect with PC by UART.
AP placed near DUT and PC.
PC has 1 wired NIC connected to AP.
PC has 1 WiFi NIC.
- tag: SSC_T1_9
<<: *TEST_ENV
Target Count: 1
test environment detail: |-
PC has 2 wired NIC connected to AP.
1 SSC DUT connected to AP.
1 SSC DUT connect with PC by UART.
- tag: SSC_T1_10
<<: *TEST_ENV
Target Count: 1
test environment detail: |-
PC has 1 WiFi NIC.
1 SSC DUT connect with PC by UART.
- tag: SSC_T1_ARP
<<: *TEST_ENV
Target Count: 1
test environment detail: |-
PC (linux) has 1 wired NIC connected to AP.
AP is configured as update group key every 30s.
PC has 1 WiFi NIC.
1 SSC DUT connect with PC by UART.
- tag: SSC_T1_8089
<<: *TEST_ENV
Special: Y
@ -29,7 +89,7 @@ test environment:
test environment detail: |-
PC has 1 wired NIC connected to AP.
1 8089 tablet able to run iperf test placed near SSC1.
1 SSC target connect with PC by UART.
1 SSC DUT connect with PC by UART.
- tag: SSC_T1_ADC
<<: *TEST_ENV
Special: Y
@ -38,14 +98,14 @@ test environment:
PC has 1 wired NIC connected to AP.
Analog input connect to SSC1 TOUT.
Multimeter connect to input, able to measure input voltage.
1 SSC target connect with PC by UART.
1 SSC DUT connect with PC by UART.
- tag: SSC_T1_AMSDU
<<: *TEST_ENV
Special: Y
Target Count: 1
test environment detail: |-
1 SSC target connect PC by UART.
PC 无线网卡和 SSC target 均连接到天猫魔盒AP.
1 SSC DUT connect PC by UART.
PC 无线网卡和 SSC DUT 均连接到天猫魔盒AP.
- tag: SSC_T1_APC
<<: *TEST_ENV
Special: Y
@ -55,12 +115,12 @@ test environment:
PC has 1 wired NIC connected to APC (static IP within the same subnet with APC).
APC control AP power supply.
PC has 1 WiFi NIC.
1 SSC target connect with PC by UART.
1 SSC DUT connect with PC by UART.
- tag: SSC_T1_Enterprise
<<: *TEST_ENV
Special: Y
Target Count: 1
test environment detail: "AP use WPA2-Etherprise is placed near SSC1. \n1 SSC target
test environment detail: "AP use WPA2-Etherprise is placed near SSC1. \n1 SSC DUT
connect with PC by UART."
- tag: SSC_T1_IOT1
<<: *TEST_ENV
@ -68,14 +128,14 @@ test environment:
Target Count: 1
test environment detail: |-
PC has 1 WiFi NIC.
1 SSC target connect with PC by UART.
1 SSC DUT connect with PC by UART.
AP todo IOT test are placed near SSC1.
- tag: SSC_T1_InitData
<<: *TEST_ENV
Special: Y
Target Count: 2
test environment detail: |-
2 SSC target connect with PC by UART.
2 SSC DUT connect with PC by UART.
SSC1 use 40M crystal oscillator.
SSC2 use normal 26M crystal oscillator.
SSC2 GPIO connect to SSC1 power control pin.
@ -83,7 +143,7 @@ test environment:
<<: *TEST_ENV
Special: N
Target Count: 1
test environment detail: 1 SSC target connect with PC by UART. All APs power on.
test environment detail: 1 SSC DUT connect with PC by UART. All APs power on.
- tag: SSC_T1_ShieldBox
<<: *TEST_ENV
Special: Y
@ -98,8 +158,8 @@ test environment:
Special: Y
Target Count: 1
test environment detail: |-
AP support DTIM placed with AT target.
SSC target connect with Raspberry Pi by UART.
AP support DTIM placed with AT DUT.
SSC DUT connect with Raspberry Pi by UART.
Multimeter connect with Raspberry Pi via GPIB.
Series multimeter between GND and VCC of SSC1.
SSC1's light sleep wakeup pin and wakeup indication connect with Raspberry Pi's GPIO.
@ -109,8 +169,8 @@ test environment:
Special: Y
Target Count: 1
test environment detail: |-
AP support DTIM placed with AT target.
SSC target connect with Raspberry Pi by UART.
AP support DTIM placed with AT DUT.
SSC DUT connect with Raspberry Pi by UART.
Multimeter connect with Raspberry Pi via GPIB.
Series multimeter between GND and VCC of SSC1.
SSC1's RSTB pin connect with Raspberry Pi's GPIO.
@ -119,8 +179,8 @@ test environment:
Special: Y
Target Count: 1
test environment detail: |-
AP support DTIM placed with AT target.
SSC target connect with Raspberry Pi by UART.
AP support DTIM placed with AT DUT.
SSC DUT connect with Raspberry Pi by UART.
Multimeter connect with Raspberry Pi via GPIB.
Series multimeter between GND and VCC of SSC1.
- tag: SSC_T1_Sniffer
@ -128,26 +188,26 @@ test environment:
Target Count: 1
test environment detail: |-
PC has 1 wired NIC connected to AP. PC has 1 WiFi NIC.
1 SSC target connect with PC by UART.
1 SSC DUT connect with PC by UART.
- tag: SSC_T1_TempBox
<<: *TEST_ENV
Special: Y
Target Count: 1
test environment detail: |-
1 SSC target connect with PC by UART.
Put SSC target to temperature box.
1 SSC DUT connect with PC by UART.
Put SSC DUT to temperature box.
- tag: SSC_T1_VDD33
<<: *TEST_ENV
Special: Y
Target Count: 1
test environment detail: |-
1 SSC target connect with PC by UART.
1 SSC DUT connect with PC by UART.
Multimeter connect to VDD33, able to measure voltage.
- tag: SSC_T1_WEP
<<: *TEST_ENV
Target Count: 1
test environment detail: |-
1 SSC target connect with PC by UART.
1 SSC DUT connect with PC by UART.
One WEP share key AP placed near SSC1.
- tag: SSC_T2_1
<<: *TEST_ENV
@ -155,29 +215,53 @@ test environment:
test environment detail: |-
PC has 1 wired NIC connected to AP.
PC has 1 WiFi NIC.
2 SSC target connect with PC by UART.
2 SSC DUTs connect with PC by UART.
- tag: SSC_T2_2
<<: *TEST_ENV
Target Count: 2
test environment detail: |-
PC has 1 WiFi NIC.
2 SSC DUTs connect with PC by UART.
- tag: SSC_T2_3
<<: *TEST_ENV
Target Count: 2
test environment detail: |-
2 SSC DUTs connect with PC by UART.
AP placed near SSC DUTs
- tag: SSC_T2_4
<<: *TEST_ENV
Target Count: 2
test environment detail: |-
PC has 1 wired NIC connected to AP.
AP placed near SSC DUTs and PC.
2 SSC DUTs connect with PC by UART.
- tag: SSC_T2_5
<<: *TEST_ENV
Target Count: 2
test environment detail: |-
2 SSC DUTs connect with PC by UART.
- tag: SSC_T2_JAP
<<: *TEST_ENV
Target Count: 2
test environment detail: |-
PC has 1 wired NIC connected to APC.
APC control the power supply of multiple APs.
2 SSC target connect with PC by UART.
2 SSC DUT connect with PC by UART.
- tag: SSC_T2_PhyMode
<<: *TEST_ENV
PC OS: 'linux'
Target Count: 2
test environment detail: |-
2 SSC target connect with PC by UART.
2 SSC DUT connect with PC by UART.
PC has one WiFi NIC support capture wlan packet using libpcap.
Set 4 AP with phy mode 11b, 11g, 11n HT20, 11n HT40.
Put 4 APs near SSC targets.
Put 4 APs near SSC DUTs.
- tag: SSC_T2_ShieldBox
<<: *TEST_ENV
Special: Y
Target Count: 2
test environment detail: |-
2 SSC target connect with PC by UART.
2 SSC DUT connect with PC by UART.
Put them to Shield box.
- tag: SSC_T2_ShieldBox2
<<: *TEST_ENV
@ -185,7 +269,7 @@ test environment:
Target Count: 1
test environment detail: |
refer to figure.
2 SSC target connect with PC by UART. Put target board to different Shield boxes.
2 SSC DUT connect with PC by UART. Put DUT board to different Shield boxes.
2 shield boxes are connected with programmable attenuator.
- tag: SSC_T2_Sniffer
<<: *TEST_ENV
@ -195,14 +279,14 @@ test environment:
test environment detail: |-
PC has 1 wired NIC connected to AP.
PC has 1 WiFi NIC.
2 SSC target connect with PC by UART.
2 SSC DUT connect with PC by UART.
- tag: SSC_T2_TempBox
<<: *TEST_ENV
Special: Y
Target Count: 1
test environment detail: |
refer to figure.
2 SSC target connect with PC by UART. Put 1 target board to temperature box.
2 SSC DUT connect with PC by UART. Put 1 DUT board to temperature box.
- tag: SSC_T3_1
<<: *TEST_ENV
Special: N
@ -210,34 +294,64 @@ test environment:
test environment detail: |-
PC has 1 wired NIC connected to AP.
PC has 1 WiFi NIC.
3 SSC target connect with PC by UART.
3 SSC DUT connect with PC by UART.
- tag: SSC_T3_PhyMode
<<: *TEST_ENV
PC OS: 'linux'
Target Count: 3
test environment detail: |-
3 SSC target connect with PC by UART.
3 SSC DUT connect with PC by UART.
PC has one WiFi NIC support capture wlan packet using libpcap.
Set 4 AP with (HT20, channel1), (HT20, channel2), (HT40, channel1), (HT40, channel2).
Put 4 APs near SSC targets.
Put 4 APs near SSC DUTs.
- tag: SSC_T5_1
<<: *TEST_ENV
Target Count: 5
test environment detail: 5 SSC target connect with PC by UART.
test environment detail: 5 SSC DUT connect with PC by UART.
- tag: SSC_T5_IOT1
<<: *TEST_ENV
Special: Y
Target Count: 5
test environment detail: |-
5 SSC targets connect with PC by UART.
some Android smart phone are placed near SSC targets.
5 SSC DUTs connect with PC by UART.
some Android smart phone are placed near SSC DUTs.
- tag: SSC_T6_1
<<: *TEST_ENV
Target Count: 1
Special: Y
Target Count: 6
test environment detail: |-
PC has 1 wired NIC connected to AP.
PC has 1 WiFi NIC.
6 SSC target connect with PC by UART.
6 SSC DUT connect with PC by UART.
- tag: SSC_T1_DNS
<<: *TEST_ENV
Target Count: 1
test environment detail: 1 SSC DUT connect with PC by UART,AP should Access to the Internet.
- tag: SSC_T1_SmartConfigIOT
<<: *TEST_ENV
Special: Y
Target Count: 1
test environment detail: |
1 SSC DUT connect with PC by UART.
PC has 1 wired NIC connect to Common AP.
Several AP are placed near AT DUT.
Several smart phone installed test APK are placed near SSC DUT.
- tag: SSC_T20_1
<<: *TEST_ENV
Special: Y
Target Count: 20
test environment detail: |-
PC has 1 wired NIC connected to AP.
PC has 1 WiFi NIC.
20 SSC DUT connect with PC by UART.
- tag: SSC_T35_1
<<: *TEST_ENV
Special: Y
Target Count: 35
test environment detail: |-
PC has 1 wired NIC connected to AP.
PC has 1 WiFi NIC.
37 SSC DUT connect with PC by UART.
- tag: SSC_T50_1
<<: *TEST_ENV
Special: Y
@ -245,4 +359,28 @@ test environment:
test environment detail: |-
PC has 1 wired NIC connected to AP.
PC has 1 WiFi NIC.
50 SSC target connect with PC by UART.
50 SSC DUT connect with PC by UART.
- tag: SSC_T60_1
<<: *TEST_ENV
Special: Y
Target Count: 60
test environment detail: |-
PC has 1 wired NIC connected to AP.
PC has 1 WiFi NIC.
60 SSC DUT connect with PC by UART.
- tag: SSC_T80_1
<<: *TEST_ENV
Special: Y
Target Count: 80
test environment detail: |-
PC has 1 wired NIC connected to AP.
PC has 1 WiFi NIC.
80 SSC DUT connect with PC by UART.
- tag: SSC_T100_1
<<: *TEST_ENV
Special: Y
Target Count: 100
test environment detail: |-
PC has 1 wired NIC connected to AP.
PC has 1 WiFi NIC.
100 SSC DUT connect with PC by UART.