Merge branch 'feature/move_auto_test_script_to_new_repo_3.1' into 'release/v3.1'

ci: move auto_test_script to new repo (backport 3.1)

See merge request espressif/esp-idf!10929
This commit is contained in:
He Yin Ling 2020-10-24 09:26:28 +08:00
commit 64b0bc221f
32 changed files with 135 additions and 34181 deletions

View File

@ -31,6 +31,15 @@ variables:
APPLY_BOT_FILTER_SCRIPT: "$CI_PROJECT_DIR/tools/ci/apply_bot_filter.py"
CHECKOUT_REF_SCRIPT: "$CI_PROJECT_DIR/tools/ci/checkout_project_ref.py"
# Docker images
BOT_DOCKER_IMAGE_TAG: ":latest"
# target test repo parameters
TEST_ENV_CONFIG_REPO: "${GITLAB_SSH_SERVER}/qa/ci-test-runner-configs.git"
CI_AUTO_TEST_SCRIPT_REPO_URL: "${GITLAB_SSH_SERVER}/qa/auto_test_script.git"
CI_AUTO_TEST_SCRIPT_REPO_BRANCH: "ci/v3.1"
# When 'fetch' strategy is used, Gitlab removes untracked files before checking out
# new revision. However if the new revision doesn't include some of the submodules
# which were present in the old revision, such submodule directories would not be
@ -94,6 +103,14 @@ before_script:
- chmod 600 ~/.ssh/id_rsa
- echo -e "Host gitlab.espressif.cn\n\tStrictHostKeyChecking no\n" >> ~/.ssh/config
# for parallel jobs, CI_JOB_NAME will be "job_name index/total" (for example, "IT_001 1/2")
# we need to convert to pattern "job_name_index.yml"
.define_config_file_name: &define_config_file_name |
JOB_NAME_PREFIX=$(echo ${CI_JOB_NAME} | awk '{print $1}')
JOB_FULL_NAME="${JOB_NAME_PREFIX}_${CI_NODE_INDEX}"
CONFIG_FILE="${CONFIG_FILE_PATH}/${JOB_FULL_NAME}.yml"
build_template_app:
stage: build
image: $CI_DOCKER_REGISTRY/esp32-ci-env$BOT_DOCKER_IMAGE_TAG
@ -639,6 +656,11 @@ assign_test:
variables:
TEST_FW_PATH: "$CI_PROJECT_DIR/tools/tiny-test-fw"
EXAMPLE_CONFIG_OUTPUT_PATH: "$CI_PROJECT_DIR/examples/test_configs"
INTEGRATION_CONFIG_OUTPUT_PATH: "${CI_PROJECT_DIR}/components/idf_test/integration_test/CIConfigs"
TEST_CASE_FILE_PATH: "$CI_PROJECT_DIR/auto_test_script/TestCaseFiles"
ASSIGN_TEST_CASE_SCRIPT: "${CI_PROJECT_DIR}/auto_test_script/bin/CIAssignTestCases.py"
PYTHONPATH: "${CI_PROJECT_DIR}/auto_test_script/packages"
PYTHON_VER: 3.7.7
artifacts:
paths:
- components/idf_test/*/CIConfigs
@ -658,11 +680,11 @@ assign_test:
# assign unit test cases
- python $TEST_FW_PATH/CIAssignUnitTest.py $IDF_PATH/components/idf_test/unit_test/TestCaseAll.yml $IDF_PATH/.gitlab-ci.yml $IDF_PATH/components/idf_test/unit_test/CIConfigs
# clone test script to assign tests
- git clone $TEST_SCRIPT_REPOSITORY
- ./tools/ci/retry_failed.sh git clone ${CI_AUTO_TEST_SCRIPT_REPO_URL} -b empty_branch
- ./tools/ci/retry_failed.sh git -C auto_test_script checkout -f ${CI_AUTO_TEST_SCRIPT_REPO_BRANCH}
- python $CHECKOUT_REF_SCRIPT auto_test_script auto_test_script
- cd auto_test_script
# assgin integration test cases
- python CIAssignTestCases.py -t $IDF_PATH/components/idf_test/integration_test -c $IDF_PATH/.gitlab-ci.yml -b $IDF_PATH/SSC/ssc_bin
- python ${ASSIGN_TEST_CASE_SCRIPT} -t $TEST_CASE_FILE_PATH -c $IDF_PATH/.gitlab-ci.yml -b $IDF_PATH/SSC/ssc_bin -o $INTEGRATION_CONFIG_OUTPUT_PATH
.example_test_template: &example_test_template
stage: target_test
@ -712,7 +734,7 @@ assign_test:
# first test if config file exists, if not exist, exit 0
- test -e $CONFIG_FILE || exit 0
# clone test env configs
- git clone $TEST_ENV_CONFIG_REPOSITORY
- ./tools/ci/retry_failed.sh git clone $TEST_ENV_CONFIG_REPO
- python $CHECKOUT_REF_SCRIPT ci-test-runner-configs ci-test-runner-configs
- cd $TEST_FW_PATH
# run test
@ -767,22 +789,27 @@ assign_test:
variables:
LOCAL_ENV_CONFIG_PATH: "$CI_PROJECT_DIR/ci-test-runner-configs/$CI_RUNNER_DESCRIPTION/ESP32_IDF"
LOG_PATH: "$CI_PROJECT_DIR/$CI_COMMIT_SHA"
TEST_CASE_FILE_PATH: "$CI_PROJECT_DIR/components/idf_test/integration_test"
MODULE_UPDATE_FILE: "$CI_PROJECT_DIR/components/idf_test/ModuleDefinition.yml"
CONFIG_FILE: "$CI_PROJECT_DIR/components/idf_test/integration_test/CIConfigs/${CI_JOB_NAME}_.yml"
TEST_CASE_FILE_PATH: "$CI_PROJECT_DIR/auto_test_script/TestCaseFiles"
CONFIG_FILE_PATH: "${CI_PROJECT_DIR}/components/idf_test/integration_test/CIConfigs"
KNOWN_ISSUE_FILE: "${CI_PROJECT_DIR}/components/idf_test/integration_test/KnownIssues"
PYTHONPATH: "${CI_PROJECT_DIR}/auto_test_script/packages"
CI_RUNNER_SCRIPT: "${CI_PROJECT_DIR}/auto_test_script/bin/CIRunner.py"
PYTHON_VER: 3.7.7
before_script: *add_gitlab_key_before
script:
- *define_config_file_name
# first test if config file exists, if not exist, exit 0
- test -e $CONFIG_FILE || exit 0
# clone local test env configs
- git clone $TEST_ENV_CONFIG_REPOSITORY
- ./tools/ci/retry_failed.sh git clone $TEST_ENV_CONFIG_REPO
- python $CHECKOUT_REF_SCRIPT ci-test-runner-configs ci-test-runner-configs
# clone test bench
- git clone $TEST_SCRIPT_REPOSITORY
- ./tools/ci/retry_failed.sh git clone ${CI_AUTO_TEST_SCRIPT_REPO_URL} -b empty_branch
- ./tools/ci/retry_failed.sh git -C auto_test_script checkout -f ${CI_AUTO_TEST_SCRIPT_REPO_BRANCH}
- python $CHECKOUT_REF_SCRIPT auto_test_script auto_test_script
- cd auto_test_script
- cat ${KNOWN_ISSUE_FILE} >> ${TEST_CASE_FILE_PATH}/KnownIssues
# run test
- python CIRunner.py -l "$LOG_PATH/$CI_JOB_NAME" -c $CONFIG_FILE -e $LOCAL_ENV_CONFIG_PATH -t $TEST_CASE_FILE_PATH -m $MODULE_UPDATE_FILE
- python ${CI_RUNNER_SCRIPT} -l "$LOG_PATH/$CI_JOB_NAME" -c $CONFIG_FILE -e $LOCAL_ENV_CONFIG_PATH -t $TEST_CASE_FILE_PATH
nvs_compatible_test:
<<: *test_template
@ -796,17 +823,21 @@ nvs_compatible_test:
- ESP32_IDF
- NVS_Compatible
script:
- *define_config_file_name
# first test if config file exists, if not exist, exit 0
- test -e $CONFIG_FILE || exit 0
# clone local test env configs
- git clone $TEST_ENV_CONFIG_REPOSITORY
- ./tools/ci/retry_failed.sh git clone $TEST_ENV_CONFIG_REPO
- python $CHECKOUT_REF_SCRIPT ci-test-runner-configs ci-test-runner-configs
# clone test bench
- git clone $TEST_SCRIPT_REPOSITORY
- python $CHECKOUT_REF_SCRIPT auto_test_script auto_test_script
- cd auto_test_script
- ./tools/ci/retry_failed.sh git clone ${CI_AUTO_TEST_SCRIPT_REPO_URL} -b empty_branch
- ./tools/ci/retry_failed.sh git -C auto_test_script checkout -f ${CI_AUTO_TEST_SCRIPT_REPO_BRANCH}
- python $CHECKOUT_REF_SCRIPT auto_test_script "$CI_PROJECT_DIR/auto_test_script/TestCaseFiles"
# prepare nvs bins
- ./Tools/prepare_nvs_bin.sh
- cd auto_test_script
- ./tools/prepare_nvs_bin.sh
# run test
- python CIRunner.py -l "$LOG_PATH/$CI_JOB_NAME" -c $CONFIG_FILE -e $LOCAL_ENV_CONFIG_PATH -t $TEST_CASE_FILE_PATH -m $MODULE_UPDATE_FILE
- python ${CI_RUNNER_SCRIPT} -l "$LOG_PATH/$JOG_FULL_NAME" -c $CONFIG_FILE -e $LOCAL_ENV_CONFIG_PATH -t $TEST_CASE_FILE_PATH
example_test_001_01:
<<: *example_test_template
@ -1078,6 +1109,12 @@ UT_001_40:
- UT_T1_32kXTAL
- psram
UT_001_41:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
UT_002_01:
<<: *unit_test_template
tags:
@ -1330,236 +1367,87 @@ UT_601_03:
- ESP32_IDF
- UT_T1_1
IT_001_01:
IT_001:
<<: *test_template
parallel: 3
tags:
- ESP32_IDF
- SSC_T1_4
IT_001_02:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_4
IT_001_03:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_4
IT_002_01:
IT_002:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_2
IT_003_01:
IT_003:
<<: *test_template
parallel: 14
tags:
- ESP32_IDF
- SSC_T2_5
IT_003_02:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_5
IT_003_03:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_5
IT_003_04:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_5
IT_003_05:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_5
IT_003_06:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_5
IT_003_07:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_5
IT_003_08:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_5
IT_003_09:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_5
IT_003_10:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_5
IT_003_11:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_5
IT_003_12:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_5
IT_003_13:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_5
IT_004_01:
IT_004:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_APC
IT_005_01:
IT_005:
<<: *test_template
parallel: 2
tags:
- ESP32_IDF
- SSC_T1_5
IT_006_01:
IT_006:
<<: *test_template
parallel: 13
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_006_06:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_6
IT_006_07:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_6
IT_007_01:
IT_007:
<<: *test_template
parallel: 3
tags:
- ESP32_IDF
- SSC_T1_7
IT_007_02:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_7
IT_007_03:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_7
IT_008_01:
IT_008:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_8
IT_009_01:
IT_009:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_3
IT_011_01:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T12_MESH1
IT_012_01:
IT_018:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_9
IT_012_02:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T1_9
IT_013_01:
IT_019:
<<: *test_template
parallel: 2
tags:
- ESP32_IDF
- SSC_T2_2
IT_013_02:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_2
IT_014_01:
IT_020:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_3
IT_015_01:
IT_021:
<<: *test_template
tags:
- ESP32_IDF
- SSC_T2_4
UT_001_41:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1

View File

@ -1,228 +0,0 @@
.MESH_INIT_COND: &MESH_INIT_COND
test script: InitCondMesh
restore post cmd set:
- ''
- - 'MSSC SSC[1-<node_num>] ram'
- ['P SSC[1-<node_num>] C +FREEHEAP:']
# - - 'MSSC SSC[1-<node_num>] mesh -Q -o 1'
# - ['P SSC[1-<node_num>] C MESH_NETWORK']
.mesh_get_all_dut_mac: &mesh_get_all_dut_mac
LIST_MERGE:
- - 'MSSC SSC[1-<node_num>] mac'
- ['R SSC[1-<node_num>] A <device_mac>:\+STAMAC:(.+)\r\n']
.mesh_check_tree_num: &mesh_check_tree_num
LIST_MERGE:
- - 'MSSC SSC[1-<node_num>] mesh -Q -o 2'
- ['P SSC[1-<node_num>] T topo']
- - 'MESHTREE'
- ['R PC_COM RE "MESHTREE:%%s"%%(<tree_node_num>)']
.mesh_tree_stably: &mesh_tree_stably
LIST_MERGE:
- - 'SSC MNODE(0) mesh -Q -o 1 -t <stable_check_time>'
- ['P MNODE(0) RE "MESH_NETWORK:1,%%s"%%(<node_num>)', 'P MNODE(0) C MESH_STABLE_CHECK:PASS']
.deinit_mesh: &deinit_mesh
LIST_MERGE:
- - 'MSSC SSC[1-<node_num>] mesh -I -o 1'
- ['P SSC[1-<node_num>] C +MESH:DEINITED']
.mesh_force_reboot: &mesh_force_reboot
LIST_MERGE:
- - 'MSSC SSC[1-<node_num>] restore'
- ['P SSC[1-<node_num>] C !!!ready!!!']
.mesh_config_all_duts: &mesh_config_all_duts
LIST_MERGE:
- - 'MSSC SSC[1-<node_num>] meshset -M -o 0 -t <map_auth_mode> -e <map_password> -l 10'
- ['P SSC[1-<node_num>] C +MESHSET:MAP_AUTH,OK']
- - 'MSSC SSC[1-<node_num>] meshset -G -o 0 -m <mesh_id> -s <router_ssid> -p <router_password> -n
<router_channel> -b <router_bssid> -t <max_connect> -e <map_password> -i <ie_encrypt>'
- ['P SSC[1-<node_num>] C +MESHSET:CFG,OK']
- - 'MSSC SSC[1-<node_num>] meshset -L -o 0 -l <max_layer>'
- ['P SSC[1-<node_num>] C +MESHSET:MLAYER,OK']
- - 'MSSC SSC[1-<node_num>] meshset -W -o 0 -t <duration_ms> -n <cnx_rssi> -l <select_rssi> -i <switch_rssi> -k <backoff_rssi>'
- ['P SSC[1-<node_num>] C +MESHSET:SWITCH,OK']
- - 'MSSC SSC[1-<node_num>] meshset -K -o 0 -i <allow_roots>'
- ['P SSC[1-<node_num>] C +MESHSET:ALLOW_ROOTS,OK']
- - 'MSSC SSC[1-<node_num>] meshset -J -o 0 -t <assoc_expire>'
- ['P SSC[1-<node_num>] C +MESHSET:ASSOC,OK']
.mesh_set_same_ssid_softap: &mesh_set_same_ssid_softap
LIST_MERGE:
- - 'MSSC SSC[1-3] op -S -o 2'
- ['P SSC[1-3] C +MODE:OK']
- - 'MSSC SSC[1-3] ap -S -s <target_ssid> -p <target_password> -t <target_auth_enum> -n
[<router_channel>,<router_channel>,<wrong_channel>]'
- ['P SSC[1-3] C +SAP:OK']
initial condition:
- tag: MESH_DEINIT_STA
<<: *MESH_INIT_COND
initial condition detail: all DUTs with mesh not inited, station mode
check cmd set:
- ''
- - MSSC SSC[1-<node_num>] mesh -Q
- - P SSC[1-<node_num>] C MESH_STATE_NONE
- - MSSC SSC[1-<node_num>] op -S -o 1
- - P SSC[1-<node_num>] C +MODE:OK
- *mesh_get_all_dut_mac
restore cmd set:
- ''
- - MSSC SSC[1-<node_num>] mesh -I -o 1
- - P SSC[1-<node_num>] C +MESH_DEINITED
- - MSSC SSC[1-<node_num>] op -S -o 1
- - P SSC[1-<node_num>] C +MODE:OK
- *mesh_get_all_dut_mac
force restore cmd set:
- ''
# - - MSSC SSC[1-<node_num>] reboot
- - FREBOOT SSC[1-<node_num>]
- - P SSC[1-<node_num>] C !!!ready!!!
- *mesh_get_all_dut_mac
- tag: MESH_INIT1
<<: *MESH_INIT_COND
initial condition detail: DUTs with mesh network already established, router....
check cmd set:
- ''
- *mesh_get_all_dut_mac
- - VALUE <tree_node_num> <node_num>
- - R PC_COM L OK
- *mesh_check_tree_num
- *mesh_tree_stably
- - MSSC SSC[1-<node_num>] mesh -Q -o 3
- - P SSC[1-<node_num>] RE "MID,%%s"%%(<mesh_id>)
- P SSC[1-<node_num>] RE "MROUTER,%%s"%%(<router_ssid>)
- P SSC[1-<node_num>] RE "SWITCH_PARENT,%%s"%%(<duration_ms>)
- P SSC[1-<node_num>] C NO_SPECIFIC_SETTINGS
restore cmd set:
- ''
- - MSSC SSC[1-<node_num>] mesh -I -o 1
- - P SSC[1-<node_num>] C MESH_DEINITED
- - MSSC SSC[1-<node_num>] op -S -o 1
- - P SSC[1-<node_num>] C +MODE:OK
- *mesh_get_all_dut_mac
- - MSSC SSC[1-<node_num>] mesh -I
- - P SSC[1-<node_num>] C +MESH:INIT,OK
- *mesh_config_all_duts
- - MSSC SSC[1-<node_num>] mesh -T
- - P SSC[1-<node_num>] C +MESH:START,OK
- - DELAY <delay_time>
- - ''
- - VALUE <tree_node_num> <node_num>
- - R PC_COM L OK
- *mesh_check_tree_num
- *mesh_tree_stably
force restore cmd set:
- ''
- - MSSC SSC[1-<node_num>] reboot
- - P SSC[1-<node_num>] C !!!ready!!!
- *mesh_get_all_dut_mac
- - MSSC SSC[1-<node_num>] mesh -I
- - P SSC[1-<node_num>] C +MESH:INIT,OK
- *mesh_config_all_duts
- - MSSC SSC[1-<node_num>] mesh -T
- - P SSC[1-<node_num>] C +MESH:START,OK
- - DELAY <delay_time>
- - ''
- - VALUE <tree_node_num> <node_num>
- - R PC_COM L OK
- *mesh_check_tree_num
- *mesh_tree_stably
- tag: MESH_INIT_SWITCH
<<: *MESH_INIT_COND
initial condition detail: 3 duts in softAP mode with same ssid/password, all duts establish network
check cmd set:
- ''
- - SSC SSC[1-3] ap -Q
- - P SSC[1-3] RE "RE "APCONFIG:%%s"%%(<target_ssid>)
- - MSSC SSC[4-<node_num>] mac
- - R SSC[4-<node_num>] A <device_mac>:\+STAMAC:(.+)\r\n
- - VALUE <tree_node_num> <node_num>-3
- - R PC_COM L OK
- - MSSC SSC[4-<node_num>] mesh -Q -o 2
- - P SSC[4-<node_num>] T topo
- - MESHTREE
- - R PC_COM RE "TREE_TOTAL_NODES:%%s"%%(<tree_node_num>)
- - MSSC SSC[4-<node_num>] mesh -Q -o 3
- P SSC[4-<node_num>] RE "MROUTER,%%s"%%(<target_ssid>)
- - DELAY 5
- - P PC_COM C +DELAYDONE
- P SSC[4-<node_num>] NC MESH_EVENT_DISCONNECTED
restore cmd set:
- ''
- - ASSERT
- - ''
force restore cmd set:
- ''
- - MSSC SSC[1-<node_num>] reboot
- - P SSC[1-<node_num>] C !!!ready!!!
- *mesh_get_all_dut_mac
- *mesh_set_same_ssid_softap
- - MSSC SSC[4-<node_num>] mesh -I
- - P SSC[4-<node_num>] C +MESH:INIT,OK
- - MSSC SSC[4-<node_num>] meshset -M -o 0 -t <map_auth_mode> -e <map_password> -l 10
- - P SSC[4-<node_num>] C +MESHSET:MAP_AUTH,OK
- - MSSC SSC[4-<node_num>] meshset -G -o 0 -m <mesh_id> -s <target_ssid> -p <target_password> -n <try_channel> -h 1 -t
<max_connect> -e <map_password> -i <ie_encrypt>
- - P SSC[4-<node_num>] C +MESHSET:CFG,OK
- - MSSC SSC[4-<node_num>] meshset -L -o 0 -l <max_layer>
- - P SSC[4-<node_num>] C +MESHSET:MLAYER,OK
- - MSSC SSC[4-<node_num>] meshset -W -o 0 -t <duration_ms> -n <cnx_rssi> -l <select_rssi> -i <switch_rssi> -k <backoff_rssi>
- - P SSC[4-<node_num>] C +MESHSET:SWITCH,OK
- - MSSC SSC[4-<node_num>] meshset -K -o 0 -i <allow_roots>
- - P SSC[4-<node_num>] C +MESHSET:ALLOW_ROOTS,OK
- - MSSC SSC[4-<node_num>] mesh -T
- - P SSC[4-<node_num>] C +MESH:START,OK
- - DELAY <delay_time>
- - ''
- - VALUE <tree_node_num> <node_num>-3
- - R PC_COM L OK
- - MSSC SSC[4-<node_num>] mesh -Q -o 2
- - P SSC[4-<node_num>] T topo
- - MESHTREE
- - R PC_COM RE "TREE_TOTAL_NODES:%%s"%%(<tree_node_num>)
- - DELAY 10
- - P PC_COM C +DELAYDONE
- P SSC[4-<node_num>] NC MESH_EVENT_DISCONNECTED
- tag: MESH_NO_ROUTER
<<: *MESH_INIT_COND
initial condition detail: DUTs with mesh network already established, router....
check cmd set:
- ''
- *mesh_get_all_dut_mac
- - VALUE <tree_node_num> <node_num>
- - R PC_COM L OK
- *mesh_check_tree_num
- *mesh_tree_stably
- - MSSC SSC[1-<node_num>] mesh -Q -o 3
- - P SSC[1-<node_num>] RE "MID,%%s"%%(<mesh_id>)
- P SSC[1-<node_num>] C NO_ROUTER
restore cmd set:
- ''
- - ASSERT
- - ''
force restore cmd set:
- ''
- - ASSERT
- - ''
- tag: MESH_STABLE
<<: *MESH_INIT_COND
initial condition detail: DUTs with mesh network already established and stable, never restore
check cmd set:
- ''
- *mesh_get_all_dut_mac
- - MSSC SSC[1-<node_num>] mesh -Q -o 2
- - P SSC[1-<node_num>] T topo
- - MESHTREE stable
- - P PC_COM RE "MESHTREE:%%s%20nodes"%%(<node_num>)
restore cmd set:
- ''
- - ASSERT
- - ''
force restore cmd set:
- ''
- - ASSERT
- - ''

File diff suppressed because it is too large Load Diff

View File

@ -1,6 +1,18 @@
# BT heap size issue
BTSTK_MISC_0301
# GATT read multiple
BTSTK_GATT_27002
BTSTK_GATT_27003
# CI
ESP32.BLUEDROID_GAP_05002
ESP32.BLUEDROID_GAP_05003
ESP32.TCPIP_UDP_0301_01_02
ESP32.TCPIP_UDP_0303_01_02
ESP32.TCPIP_UDP_0303_02
ESP32.TCPIP_UDP_0304_01_02
ESP32.TCPIP_UDP_0304_02
ESP32.TCPIP_UDP_0305_01_02
ESP32.TCPIP_UDP_0305_02

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -1,607 +0,0 @@
.SMP_CASE: &SMP_CASE
SDK: ESP32_IDF
Test App: SSC_BLE
auto test: 'Yes'
category: Function
test point 1: basic function
initial condition: BLE_INIT_SMP
test environment: SSC_T2_5
execution time: 0
module: BLUEDROID
sub module: SMP
version: v1 (2017-05-26)
CI ready: 'Yes'
level: Integration
allow fail: ''
.just_work_pair: &just_work_pair
LIST_MERGE:
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ['P SSC1 C +BLECONN:GapConnect,OK', 'P SSC2 C +BLECONN:GapConnect,OK']
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['P SSC[1-2] C +BLESMP:AuthComplete,Success,0']
.slave_passkey_entry_pair: &slave_passkey_entry_pair
LIST_MERGE:
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ['P SSC1 C +BLECONN:GapConnect,OK', 'P SSC2 C +BLECONN:GapConnect,OK']
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['P SSC2 C +BLESMP:PassKeyReq', 'P SSC1 A <key>:BLESMP:PassKeyNotify,(\d+)']
- - "SSC SSC2 blesmp -K -r <dut1_bt_mac> -a 1 -k <key>"
- ['P SSC[1-2] C +BLESMP:AuthComplete,Success,0']
.master_passkey_entry_pair: &master_passkey_entry_pair
LIST_MERGE:
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ['P SSC1 C +BLECONN:GapConnect,OK', 'P SSC2 C +BLECONN:GapConnect,OK']
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['P SSC1 C +BLESMP:PassKeyReq', 'P SSC2 A <key>:BLESMP:PassKeyNotify,(\d+)']
- - "SSC SSC1 blesmp -K -r <dut2_bt_mac> -a 1 -k <key>"
- ['P SSC[1-2] C +BLESMP:AuthComplete,Success,0']
.both_side_passkey_entry_pair: &both_side_passkey_entry_pair
LIST_MERGE:
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ['P SSC1 C +BLECONN:GapConnect,OK', 'P SSC2 C +BLECONN:GapConnect,OK']
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['P SSC[1,2] C +BLESMP:PassKeyReq']
- - "SSC SSC[1,2] blesmp -K -r <dut[2,1]_bt_mac> -a 1 -k 123456"
- ['P SSC[1-2] C +BLESMP:AuthComplete,Success,0']
.numberic_comparision_pair: &numberic_comparision_pair
LIST_MERGE:
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ['P SSC1 C +BLECONN:GapConnect,OK', 'P SSC2 C +BLECONN:GapConnect,OK']
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['R SSC2 A <key>:BLESMP:NCReq,(\d+)', 'R SSC1 C NCReq P <key>']
- - "SSC SSC[1-2] blesmp -C -r <dut[2,1]_bt_mac> -a 1"
- ['P SSC[1-2] C +BLESMP:AuthComplete,Success,0']
.check_connection: &check_connection
LIST_MERGE:
- - "SSC SSC1 gattc -D -z primaryService -p 0x10 -r <dut2_bt_mac>"
- ["R SSC1 C +GATTC:Discover,OK"]
.disconnect: &disconnect
LIST_MERGE:
- - "SSC SSC1 bleconn -D -z all"
- ['P SSC1 C +BLECONN:GapDisconnect,OK', 'P SSC2 C +BLECONN:GapDisconnect,OK']
- - "SSC SSC2 bleadv -D -z start"
- ['P SSC2 C +BLEADV:OK']
.connect: &connect
LIST_MERGE:
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ['P SSC1 C +BLECONN:GapConnect,OK', 'P SSC2 C +BLECONN:GapConnect,OK']
.config_just_work: &config_just_work
LIST_MERGE:
- - "SSC SSC[1-2] blesmp -S -z AuthReqMode -v 0x00"
- ['P SSC[1-2] C +BLESMP:OK']
- - "SSC SSC[1-2] blesmp -S -z IOCAP -v 0x04"
- ['P SSC[1-2] C +BLESMP:OK']
.config_master_passkey_entry: &config_master_passkey_entry
LIST_MERGE:
- - "SSC SSC[1-2] blesmp -S -z AuthReqMode -v 0x0C"
- ['P SSC[1-2] C +BLESMP:OK']
- - "SSC SSC1 blesmp -S -z IOCAP -v 0x02"
- ['P SSC1 C +BLESMP:OK']
- - "SSC SSC2 blesmp -S -z IOCAP -v 0x04"
- ['P SSC2 C +BLESMP:OK']
.config_slave_passkey_entry: &config_slave_passkey_entry
LIST_MERGE:
- - "SSC SSC[1-2] blesmp -S -z AuthReqMode -v 0x04"
- ['P SSC[1-2] C +BLESMP:OK']
- - "SSC SSC[1-2] blesmp -S -z IOCAP -v 0x04"
- ['P SSC[1-2] C +BLESMP:OK']
.config_both_side_passkey_entry: &config_both_side_passkey_entry
LIST_MERGE:
- - "SSC SSC[1-2] blesmp -S -z AuthReqMode -v 0x04"
- ['P SSC[1-2] C +BLESMP:OK']
- - "SSC SSC[1-2] blesmp -S -z IOCAP -v 0x02"
- ['P SSC[1-2] C +BLESMP:OK']
.config_numberic_comparision: &config_numberic_comparision
LIST_MERGE:
- - "SSC SSC[1-2] blesmp -S -z AuthReqMode -v 0x0C"
- ['P SSC[1-2] C +BLESMP:OK']
- - "SSC SSC[1-2] blesmp -S -z IOCAP -v 0x04"
- ['P SSC[1-2] C +BLESMP:OK']
.config_bond_device: &config_bond_device
LIST_MERGE:
- - "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']
test cases:
- ID: BLUEDROID_SMP_04001
<<: *SMP_CASE
test point 2: BLE SMP key test
summary: BLE SMP set key size less than required for BLUEDROID
allow fail: 1/2
steps: |
1. set key size 7
2. set key size 6
3. do just work pair
expected result: |
1. succeed
2. LTK size is 7
3. succeed
cmd set:
- ""
- *config_numberic_comparision
- - "SSC SSC1 blesmp -S -z KeySize -v 0x07"
- ['P SSC1 C +BLESMP:OK']
- - "SSC SSC1 blesmp -S -z KeySize -v 0x06"
- ['P SSC1 C +BLESMP:OK']
- *connect
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['R SSC2 A <key>:BLESMP:NCReq,(\d+)', 'R SSC1 C NCReq P <key>']
- - "SSC SSC[1-2] blesmp -C -r <dut[2,1]_bt_mac> -a 1"
- ['P SSC[1-2] C +BLESMP:Key,LocalLTK,16 C +BLESMP:AuthComplete,Success,0']
- ID: BLUEDROID_SMP_04002
<<: *SMP_CASE
test point 2: BLE SMP key test
summary: BLE SMP set key size greater than required for BLUEDROID
allow fail: 1/2
steps: |
1. set key size 16
2. set key size 17
3. do just work pair
expected result: |
1. succeed
2. LTK size is 17
3. succeed
cmd set:
- ""
- *config_numberic_comparision
- - "SSC SSC1 blesmp -S -z KeySize -v 0x10"
- ['P SSC1 C +BLESMP:OK']
- - "SSC SSC1 blesmp -S -z KeySize -v 0x11"
- ['P SSC1 C +BLESMP:OK']
- *connect
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['R SSC2 A <key>:BLESMP:NCReq,(\d+)', 'R SSC1 C NCReq P <key>']
- - "SSC SSC[1-2] blesmp -C -r <dut[2,1]_bt_mac> -a 1"
- ['P SSC[1-2] C +BLESMP:Key,LocalLTK,16 C +BLESMP:AuthComplete,Success,0']
- ID: BLUEDROID_SMP_05001
<<: *SMP_CASE
test point 2: BLE SMP unsuccessful pair reply test
summary: BLE SMP unsuccessful passkey entry test for BLUEDROID
steps: |
1. enter passkey entry phase
2. entry incorrect passkey and accept
3. enter passkey entry phase
4. entry correct passkey and reject
5. enter passkey entry phase
6. send numberic comparision accept
7. enter passkey entry phase
8. send numberic comparision reject
expected result: |
1. succeed
2. pair failed
3. succeed
4. pair failed
5. succeed
6. pair failed
7. succeed
8. pair failed
cmd set:
- ""
- *config_slave_passkey_entry
- - LOOP 2 5 "[1,0]" "['000001','<key>']"
- ""
- *connect
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['P SSC2 C +BLESMP:PassKeyReq', 'P SSC1 A <key>:BLESMP:PassKeyNotify,(\d+)']
- - "SSC SSC2 blesmp -K -r <dut1_bt_mac> -a {%d} -k {%s}"
- ['P SSC[1-2] C +BLESMP:AuthComplete,Fail']
- *disconnect
- - LOOP 2 5 "[1,0]"
- ""
- *connect
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['P SSC2 C +BLESMP:PassKeyReq', 'P SSC1 A <key>:BLESMP:PassKeyNotify,(\d+)']
- - "SSC SSC[1-2] blesmp -C -r <dut[2,1]_bt_mac> -a {%d}"
- ['P SSC[1-2] C +BLESMP:AuthComplete,Fail']
- *disconnect
- ID: BLUEDROID_SMP_05002
<<: *SMP_CASE
test point 2: BLE SMP unsuccessful pair reply test
summary: BLE SMP unsuccessful numberic comparision test for BLUEDROID
steps: |
1. enter numberic comparision phase
2. entry passkey and accept
3. enter numberic comparision phase
4. send numberic comparision reject
expected result: |
1. succeed
2. pair failed
3. succeed
4. pair failed
cmd set:
- ""
- *config_numberic_comparision
- - LOOP 2 6 "[1,0]"
- ""
- *connect
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['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 5 "[1,0]" "[0,1]"
- ""
- *connect
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['R SSC2 A <key>:BLESMP:NCReq,(\d+)', 'R SSC1 C NCReq P <key>']
- - "SSC SSC[1,2] blesmp -C -r <dut[2,1]_bt_mac> -a [{%d},{%d}]"
- ['P SSC[1-2] C +BLESMP:AuthComplete,Fail']
- *disconnect
- ID: BLUEDROID_SMP_06001
<<: *SMP_CASE
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 for BLUEDROID
steps: |
1. set security parameter
2. send security response
3. send passkey reply
4. send confirm reply
5. init BLE
6. set security parameter
7. send security response
8. send passkey reply
9. send confirm reply
10. init BLE
11. set security parameter
12. send security response
13. send passkey reply
14. send confirm reply
expected result: |
1. failed
2. failed
3. failed
4. failed
5. succeed
6. failed
7. failed
8. failed
9. failed
10. succeed
11. failed
12. failed
13. failed
14. failed
cmd set:
- ""
- - "SSC SSC1 blesmp -S -z AuthReqMode -v 0x0C"
- ['P SSC1 C +BLESMP:ERROR']
- - "SSC SSC1 blesmp -R -a 1 -r <dut1_bt_mac>"
- ['P SSC1 C +BLESMP:ERROR']
- - "SSC SSC1 blesmp -K -r <dut1_bt_mac> -a 1 -k 123456"
- ['P SSC1 C +BLESMP:ERROR']
- - "SSC SSC1 blesmp -C -r <dut1_bt_mac> -a 1"
- ['P SSC1 C +BLESMP:ERROR']
- - SSC SSC1 bt -D -z init
- ['R SSC1 C +BT:']
- - "SSC SSC1 blesmp -S -z AuthReqMode -v 0x0C"
- ['P SSC1 C +BLESMP']
- - "SSC SSC1 blesmp -R -a 1 -r <dut1_bt_mac>"
- ['P SSC1 C +BLESMP']
- - "SSC SSC1 blesmp -K -r <dut1_bt_mac> -a 1 -k 123456"
- ['P SSC1 C +BLESMP']
- - "SSC SSC1 blesmp -C -r <dut1_bt_mac> -a 1"
- ['P SSC1 C +BLESMP']
- - SSC SSC1 bt -D -z enable
- ['R SSC1 C +BT:']
- - "SSC SSC1 blesmp -S -z AuthReqMode -v 0x0C"
- ['P SSC1 C +BLESMP']
- - "SSC SSC1 blesmp -R -a 1 -r <dut1_bt_mac>"
- ['P SSC1 C +BLESMP']
- - "SSC SSC1 blesmp -K -r <dut1_bt_mac> -a 1 -k 123456"
- ['P SSC1 C +BLESMP']
- - "SSC SSC1 blesmp -C -r <dut1_bt_mac> -a 1"
- ['P SSC1 C +BLESMP']
- ID: BLUEDROID_SMP_07002
<<: *SMP_CASE
test point 2: BLE SMP no bond test and repairing
summary: BLE SMP just work pairing and reboot for BLUEDROID
steps: |
1. DUT1 and DUT2 SMP with just work pair
2. DUT1 reboot
3. DUT1 connect to DUT2
4. DUT2 send auth request
expected result: |
1. succeed
2. succeed
3. succeed
4. failed
cmd set:
- ""
- *config_just_work
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ['P SSC1 C +BLECONN:GapConnect,OK', 'P SSC2 C +BLECONN:GapConnect,OK']
- - "SSC SSC1 blesmp -E -r <dut2_bt_mac> -z Enc"
- ['P SSC[1-2] C +BLESMP:AuthComplete,Success,0']
- - "SSC SSC1 reboot"
- ['P SSC2 C +BLECONN:GapDisconnect,OK']
- - "SSC SSC1 ble -R"
- ['R SSC1 C +BLE:']
- - "SSC SSC2 bleadv -D -z start"
- ['R SSC2 C +BLEADV:OK']
- *slave_passkey_entry_pair
- ID: BLUEDROID_SMP_07005
<<: *SMP_CASE
test point 2: BLE SMP no bond test and repairing
summary: BLE SMP initiator with master passkey entry and reconnect for BLUEDROID
steps: |
1. DUT1 and DUT2 SMP with master passkey entry
2. DUT1 disconnect
3. DUT1 connect to DUT2
4. DUT2 send auth request
expected result: |
1. succeed
2. succeed
3. connect succeed
4. succeed
cmd set:
- ""
- *config_master_passkey_entry
- *master_passkey_entry_pair
- *disconnect
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ['P SSC1 C +BLECONN:GapConnect,OK', 'P SSC2 C +BLECONN:GapConnect']
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['P SSC[1-2] C +BLESMP:AuthComplete,Success,0']
- ID: BLUEDROID_SMP_07006
<<: *SMP_CASE
test point 2: BLE SMP no bond test and repairing
summary: BLE SMP initiator with master passkey entry and reboot for BLUEDROID
steps: |
1. DUT1 and DUT2 SMP bond with lagecy pairing
2. DUT1 reboot
3. DUT1 connect to DUT2
4. DUT2 send auth requst
expected result: |
1. succeed
2. succeed
3. connect succeed
4. fail
cmd set:
- ""
- *config_master_passkey_entry
- *master_passkey_entry_pair
- - "SSC SSC1 reboot"
- ['P SSC2 C +BLECONN:GapDisconnect,OK']
- - "SSC SSC1 ble -R"
- ['R SSC1 C +BLE:']
- - "SSC SSC2 bleadv -D -z start"
- ['R SSC2 C +BLEADV:OK']
- *numberic_comparision_pair
- ID: BLUEDROID_SMP_07007
<<: *SMP_CASE
test point 2: BLE SMP no bond test and repairing
summary: BLE SMP initiator numberic comparision and reconnect for BLUEDROID
steps: |
1. DUT1 and DUT2 SMP with numberic comparision
2. DUT1 disconnect
3. DUT1 connect to DUT2
4. DUT2 send auth requst
expected result: |
1. succeed
2. succeed
3. connect succeed
4. succeed
cmd set:
- ""
- *config_numberic_comparision
- *numberic_comparision_pair
- *disconnect
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut2_bt_mac>"
- ['P SSC1 C +BLECONN:GapConnect,OK', 'P SSC2 C +BLECONN:GapConnect']
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['P SSC[1-2] C +BLESMP:AuthComplete,Success,0']
- ID: BLUEDROID_SMP_07008
<<: *SMP_CASE
test point 2: BLE SMP no bond test and repairing
summary: BLE SMP initiator numberic comparision and reboot for BLUEDROID
steps: |
1. DUT1 and DUT2 SMP with numberic comparision
2. DUT1 disconnect
3. DUT1 and DUT2 reboot
4. DUT2 send auth requst
expected result: |
1. succeed
2. succeed
3. connect succeed
4. failed
cmd set:
- ""
- *config_numberic_comparision
- *numberic_comparision_pair
- - "SSC SSC1 reboot"
- ['P SSC2 C +BLECONN:GapDisconnect,OK']
- - "SSC SSC1 ble -R"
- ['R SSC1 C +BLE:']
- - "SSC SSC2 bleadv -D -z start"
- ['R SSC2 C +BLEADV:OK']
- *numberic_comparision_pair
- ID: BLUEDROID_SMP_08001
<<: *SMP_CASE
test point 2: BLE SMP bond item management test
summary: BLE SMP get bond list and number without bond device for BLUEDROID
steps: |
1. DUT1 get bond list
2. DUT1 get bond number
expected result: |
1. succeed
2. succeed
cmd set:
- ""
- - "SSC SSC1 blesmp -B -z getlist -n 1"
- ['P SSC1 C +BLESMP:GetBondList,OK,0']
- - "SSC SSC1 blesmp -B -z getnum"
- ['P SSC1 C +BLESMP:GetBondNum,0']
- ID: BLUEDROID_SMP_08002
<<: *SMP_CASE
test point 2: BLE SMP bond item management test
summary: BLE SMP remove bond after connected
steps: |
1. DUT2 set AuthReqMode and RspKey
2. pairing
3. remove bond
expected result: |
1. Succeed
2. Succeed
3. Succeed
cmd set:
- ""
- *config_bond_device
- - "SSC SSC2 bleadv -D -z start"
- ['R SSC2 C +BLEADV:Start,OK']
- *connect
- - "SSC SSC2 blesmp -E -r <dut1_bt_mac> -z Enc"
- ['P SSC1 C +BLESMP:AuthComplete,Success,0','P SSC2 C +BLESMP:AuthComplete,Success,0']
- - "SSC SSC1 blesmp -B -z getnum"
- ['P SSC1 C +BLESMP:GetBondNum,1']
- - "SSC SSC1 blesmp -B -z remove -r <dut2_bt_mac>"
- ['P SSC1 RE "\+BLESMP:RemoveBond,Success,%%s"%%(<dut2_bt_mac>)']
- ID: BLUEDROID_SMP_08003
<<: *SMP_CASE
CI ready: 'No'
test point 2: BLE SMP bond item management test
summary: BLE SMP get bond list and number when pairing and after reboot for BLUEDROID
steps: |
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
allow fail: 3/5
cmd set:
- ""
- - "SSC SSC[2-5] blesmp -S -z AuthReqMode -v 0x01"
- ['P SSC[2-5] C +BLESMP:OK']
- - "SSC SSC[2-5] blesmp -S -z IOCAP -v 0x03"
- ['P SSC[2-5] C +BLESMP:OK']
- - "SSC SSC[2-5] blesmp -S -z RspKey -v 0x03"
- ['P SSC[2-5] C +BLESMP:OK']
- - LOOP 4 4 "[2,3,4,5]" "[2,3,4,5]" "[2,3,4,5]" "[2,3,4,5]" "[2,3,4,5]" "[2,3,4,5]" "[2,3,4,5]"
- ""
- - "SSC SSC{%d} bleadv -D -z start"
- ['R SSC{%d} C +BLEADV:Start,OK']
- - "SSC SSC1 bleconn -C -p 0x10 -a <dut{%d}_bt_mac>"
- ['P SSC1 C +BLECONN:GapConnect,OK', 'P SSC{%d} C +BLECONN:GapConnect']
- - "SSC SSC{%d} blesmp -E -r <dut1_bt_mac> -z Enc"
- ['P SSC1 C +BLESMP:SecReq']
- - "SSC SSC1 blesmp -R -a 1 -r <dut{%d}_bt_mac>"
- ['P SSC1 C +BLESMP:AuthComplete,Success,0','P SSC{%d} C +BLESMP:AuthComplete,Success,0']
- - "SSC SSC1 blesmp -B -z getlist -n 4"
- ['P SSC1 C +BLESMP:GetBondList,OK,4']
- - "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 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: BLUEDROID_SMP_08004
<<: *SMP_CASE
test point 2: BLE SMP bond item management test
summary: BLE SMP remove bond which not bond for BLUEDROID
steps: |
1. DUT1 remove bond
expected result: |
1. failed
cmd set:
- ""
- - "SSC SSC1 blesmp -B -z remove -r <dut2_bt_mac>"
- ['P SSC1 C +BLESMP:RemoveBond,Fail']
- ID: BLUEDROID_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 +BLECONN:GapConnect,OK', 'P SSC2 C +BLECONN:GapConnect']
- - "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 +BLECONN:GapDisconnect,OK']
- - "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 +BLECONN:GapConnect,OK', 'P SSC2 C +BLECONN:GapConnect']
- - "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']

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -1,529 +0,0 @@
.MISC_CASE: &MISC_CASE
SDK: ESP32_IDF
Test App: SSC_BLE_WIFI
auto test: 'Yes'
category: Function
test point 1: basic function
initial condition: BLE_DEINIT1
test environment: SSC_T1_1
execution time: 0
module: BT Stack
sub module: Misc
version: v1 (2016-12-31)
CI ready: 'Yes'
level: Integration
allow fail: ''
test cases:
- ID: BTSTK_MISC_0101
<<: *MISC_CASE
test point 2: bt host init and enable
summary: correct host init and deinit flow
steps: |
1. disable and deinit bt
2. init bt
3. deinit bt
4. init and enable bt
5. disable and deinit bt
expected result: |
1. succeed
2. succeed
3. succeed
4. succeed
5. succeed
cmd set:
- ""
- - "SSC SSC1 bt -D -z stop"
- ["R SSC1 C +BT"]
- - "SSC SSC1 bt -D -z init"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 bt -D -z deinit"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 bt -D -z start"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 bt -D -z stop"
- ["R SSC1 C +BT:OK"]
- ID: BTSTK_MISC_0102
<<: *MISC_CASE
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
3. deinit bt
4. disable bt
5. disable bt
6. deinit bt
7. deinit bt
8. disable bt
expected result: |
1. succeed
2. succeed
3. fail
4. succeed
5. fail
6. succeed
7. fail
8. fail
cmd set:
- ""
- - "SSC SSC1 bt -D -z stop"
- ["R SSC1 C +BT"]
- - "SSC SSC1 bt -D -z start"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 bt -D -z deinit"
- ["R SSC1 C +BT:ERROR"]
- - "SSC SSC1 bt -D -z disable"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 bt -D -z disable"
- ["R SSC1 C +BT:ERROR"]
- - "SSC SSC1 bt -D -z deinit"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 bt -D -z deinit"
- ["R SSC1 C +BT:ERROR"]
- - "SSC SSC1 bt -D -z disable"
- ["R SSC1 C +BT:ERROR"]
- ID: BTSTK_MISC_0103
<<: *MISC_CASE
test point 2: bt host init and enable
summary: incorrect host init enable flow
steps: |
1. disable and deinit bt
2. enable bt
3. init bt
4. init bt
5. enable bt
6. enable bt
7. init bt
expected result: |
1. succeed
2. fail
3. succeed
4. fail
5. succeed
6. fail
7. fail
cmd set:
- ""
- - "SSC SSC1 bt -D -z stop"
- ["R SSC1 C +BT"]
- - "SSC SSC1 bt -D -z enable"
- ["R SSC1 C +BT:ERROR"]
- - "SSC SSC1 bt -D -z init"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 bt -D -z init"
- ["R SSC1 C +BT:ERROR"]
- - "SSC SSC1 bt -D -z enable"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 bt -D -z enable"
- ["R SSC1 C +BT:ERROR"]
- - "SSC SSC1 bt -D -z init"
- ["R SSC1 C +BT:ERROR"]
- ID: BTSTK_MISC_0201
<<: *MISC_CASE
test point 2: bt controller init test
summary: bt controller init test
steps: |
1. bt controller init
expected result: |
1. OK
initial condition: WIFIBTSTOP
cmd set:
- ""
- - "SSC SSC1 btc -D -z init"
- ["R SSC1 C +BTC:OK"]
- ID: BTSTK_MISC_0202
<<: *MISC_CASE
test point 2: bt controller deinit test
summary: bt controller deinit test
steps: |
1. bt controller init
2. bt controller deinit
expected result: |
1. OK
2. OK
initial condition: WIFIBTSTOP
cmd set:
- ""
- - "SSC SSC1 btc -D -z init"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 btc -D -z deinit"
- ["R SSC1 C +BTC:OK"]
- ID: BTSTK_MISC_0203
<<: *MISC_CASE
test point 2: bt host init test
summary: bt host init test
steps: |
1. bt controller init
2. bt controller enable
3. bt host init
expected result: |
1. +BTC:OK
2. +BTC:OK
3. +BT:OK
initial condition: WIFIBTSTOP
cmd set:
- ""
- - "SSC SSC1 btc -D -z init"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 btc -D -z enable"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 bt -D -z init"
- ["R SSC1 C +BT:OK"]
- ID: BTSTK_MISC_0204
<<: *MISC_CASE
test point 2: bt host deinit test
summary: bt host deinit test
steps: |
1. bt controller init
2. bt controller enable
3. bt host init
4. bt host deinit
expected result: |
1. OK
2. OK
3. OK
4. OK
initial condition: WIFIBTSTOP
cmd set:
- ""
- - "SSC SSC1 btc -D -z init"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 btc -D -z enable"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 bt -D -z init"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 bt -D -z deinit"
- ["R SSC1 C +BT:OK"]
- ID: BTSTK_MISC_0301
<<: *MISC_CASE
test point 2: heap size unchanged after bt controller stop
summary: heap size unchanged after bt controller stop
steps: |
1.get current heap size
2.bt controller init
3.enable bt controller
4.bt host init
5.enable bt host
6.disable bt host
7.bt host deinit
8.disable bt controller
9.bt controller deinit
10.check current heap size
expected result: |
1. +FREEHEAP
2.OK
3.OK
4.OK
5.OK
6.OK
7.OK
8.OK
9.OK
10.heap size unchanged
initial condition: WIFIBTSTOP
cmd set:
- ""
- - "SSC SSC1 ram -Q"
- ['R SSC1 A <heapsize>:\+FREEHEAP:(\d+)\r\n']
- - "SSC SSC1 btc -D -z init"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 btc -D -z enable"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 bt -D -z init"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 bt -D -z enable"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 bt -D -z disable"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 bt -D -z deinit"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 btc -D -z disable"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 btc -D -z deinit"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 ram -Q"
- ['R SSC1 P <heapsize>']
- ID: BTSTK_MISC_0401
<<: *MISC_CASE
test point 2: bt controller init and enable
summary: incorrect controller init enable flow
steps: |
1. disable and deinit btc
2. enable btc
3. init btc
4. init btc
5. enable btc
6. enable btc
7. init btc
expected result: |
1. succeed
2. fail
3. succeed
4. fail
5. succeed
6. fail
7. fail
initial condition: WIFIBTSTOP
cmd set:
- ""
- - "SSC SSC1 btc -D -z stop"
- ["R SSC1 C +BTC"]
- - "SSC SSC1 btc -D -z enable"
- ["R SSC1 C +BTC:ERROR"]
- - "SSC SSC1 btc -D -z init"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 btc -D -z init"
- ["R SSC1 C +BTC:ERROR"]
- - "SSC SSC1 btc -D -z enable"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 btc -D -z enable"
- ["R SSC1 C +BTC:ERROR"]
- - "SSC SSC1 btc -D -z init"
- ["R SSC1 C +BTC:ERROR"]
- ID: BTSTK_MISC_0402
<<: *MISC_CASE
test point 2: bt controller init and enable
summary: correct controller init and deinit flow
steps: |
1. disable and deinit btc
2. init btc
3. deinit btc
4. init and enable btc
5. disable and deinit btc
expected result: |
1. succeed
2. succeed
3. succeed
4. succeed
5. succeed
cmd set:
- ""
- - "SSC SSC1 btc -D -z stop"
- ["R SSC1 C +BTC"]
- - "SSC SSC1 btc -D -z init"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 btc -D -z deinit"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 btc -D -z start"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 btc -D -z stop"
- ["R SSC1 C +BTC:OK"]
- ID: BTSTK_MISC_0403
<<: *MISC_CASE
test point 2: bt controller init and enable
summary: incorrect controller deinit disable flow
steps: |
1. disable and deinit btc
2. init and enable btc
3. deinit btc
4. disable btc
5. disable btc
expected result: |
1. succeed
2. succeed
3. fail
4. succeed
5. fail
cmd set:
- ""
- - "SSC SSC1 btc -D -z stop"
- ["R SSC1 C +BTC"]
- - "SSC SSC1 btc -D -z start"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 btc -D -z deinit"
- ["R SSC1 C +BTC:ERROR"]
- - "SSC SSC1 btc -D -z disable"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 btc -D -z disable"
- ["R SSC1 C +BTC:ERROR"]
- ID: BTSTK_MISC_0501
<<: *MISC_CASE
test point 2: bt mem release
summary: release BT memory
steps: |
1. DUT1 release BT mem
2. DUT1 init and enable btc
expected result: |
1. succeed
2. fail
initial condition: BTC_DEINIT1
cmd set:
- ""
- - "SSC SSC1 bt -R -m 1"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 btc -D -z start -m 2"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 btc -D -z start -m 1"
- ["R SSC1 C +BTC:ERROR"]
- ID: BTSTK_MISC_0502
<<: *MISC_CASE
test point 2: bt mem release
summary: release BLE memory
steps: |
1. DUT1 release BT mem
2. DUT1 init and enable btc
expected result: |
1. succeed
2. fail
initial condition: BTC_DEINIT1
cmd set:
- ""
- - "SSC SSC1 bt -R -m 2"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 btc -D -z start -m 1"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 btc -D -z start -m 2"
- ["R SSC1 C +BTC:ERROR"]
- ID: BTSTK_MISC_0503
<<: *MISC_CASE
test point 2: bt mem release
summary: release BT and BLE memory
steps: |
1. DUT1 release BT mem
2. DUT1 init and enable btc
expected result: |
1. succeed
2. fail
initial condition: BTC_DEINIT1
cmd set:
- ""
- - "SSC SSC1 bt -R -m 3"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 btc -D -z start -m 3"
- ["R SSC1 C +BTC:ERROR"]
- ID: BTSTK_MISC_0504
<<: *MISC_CASE
test point 2: bt mem release
summary: release BT memory after bt controller init
initial condition: BTC_DEINIT1
steps: |
1. DUT1 init bt controller
2. DUT1 release BT memory
3. DUT1 release BLE memory
4. DUT1 release BT and BLE memory
expected result: |
1. succeed
2. fail
3. fail
4. fail
cmd set:
- ""
- - "SSC SSC1 btc -D -z init"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 bt -R -m 1"
- ["R SSC1 C +BT:ERROR"]
- - "SSC SSC1 bt -R -m 2"
- ["R SSC1 C +BT:ERROR"]
- - "SSC SSC1 bt -R -m 3"
- ["R SSC1 C +BT:ERROR"]
- ID: BTSTK_MISC_0505
<<: *MISC_CASE
test point 2: bt mem release
summary: release BT memory after bt controller enable and bluedriod disable
initial condition: BTC_DEINIT1
steps: |
1. DUT1 init and enable bt controller
2. DUT1 release BT memory
3. DUT1 release BLE memory
4. DUT1 release BT and BLE memory
expected result: |
1. succeed
2. fail
3. fail
4. fail
cmd set:
- ""
- - "SSC SSC1 btc -D -z init"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 btc -D -z enable"
- ["R SSC1 C +BTC:OK"]
- - "SSC SSC1 bt -R -m 1"
- ["R SSC1 C +BT:ERROR"]
- - "SSC SSC1 bt -R -m 2"
- ["R SSC1 C +BT:ERROR"]
- - "SSC SSC1 bt -R -m 3"
- ["R SSC1 C +BT:ERROR"]
- ID: BTSTK_MISC_0506
<<: *MISC_CASE
test point 2: bt mem release
summary: release BT memory after bt controller enable and bluedriod init
steps: |
1. DUT1 init bluedriod
2. DUT1 release BT memory
3. DUT1 release BLE memory
4. DUT1 release BT and BLE memory
expected result: |
1. succeed
2. fail
3. fail
4. fail
cmd set:
- ""
- - "SSC SSC1 bt -D -z init"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 bt -R -m 1"
- ["R SSC1 C +BT:ERROR"]
- - "SSC SSC1 bt -R -m 2"
- ["R SSC1 C +BT:ERROR"]
- - "SSC SSC1 bt -R -m 3"
- ["R SSC1 C +BT:ERROR"]
- ID: BTSTK_MISC_0507
<<: *MISC_CASE
test point 2: bt mem release
summary: release BT memory after bt controller enable and bluedriod enable
steps: |
1. DUT1 init and enable bluedriod
2. DUT1 release BT memory
3. DUT1 release BLE memory
4. DUT1 release BT and BLE memory
expected result: |
1. succeed
2. fail
3. fail
4. fail
cmd set:
- ""
- - "SSC SSC1 bt -D -z init"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 bt -D -z enable"
- ["R SSC1 C +BT:OK"]
- - "SSC SSC1 bt -R -m 1"
- ["R SSC1 C +BT:ERROR"]
- - "SSC SSC1 bt -R -m 2"
- ["R SSC1 C +BT:ERROR"]
- - "SSC SSC1 bt -R -m 3"
- ["R SSC1 C +BT:ERROR"]
- ID: BTSTK_MISC_5001
<<: *MISC_CASE
category: Performance
test point 1: performance + stress
test point 2: BT Controller Performance test
summary: bt controller init and deinit Performance test
execution time: 6
steps: |
1.get current heap size
2.bt controller init
3.enable bt controller
4.bt host init
5.enable bt host
6.disable bt host
7.bt host deinit
8.disable bt controller
9.bt controller deinit
10.loop step1 to step 9
expected result: |
1. +FREEHEAP
2.OK
3.OK
4.OK
5.OK
6.OK
7.OK
8.OK
9.OK
10.heap size unchanged
cmd set:
- "BLEStress/BLEInitDeinitPerformance"
- - "test_time = 420"
- ""

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -1,81 +0,0 @@
test cases:
- CI ready: 'Yes'
ID: SYS_MISC_0101
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 reboot
- - R SSC1 C !!!ready!!!
execution time: 0.0
expected result: 重启成功
initial condition: None
level: Integration
module: System
steps: 系统重启
sub module: Misc
summary: test reboot function
test environment: SSC_T1_4
test point 1: basic function
test point 2: sw reboot
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: SYS_MISC_0201
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ram -H
- - R SSC1 RE FREEHEAP:\d+\r\n
execution time: 0.0
expected result: |2
可以查询到一个数值
initial condition: None
level: Integration
module: System
steps: 查询空闲ram
sub module: Misc
summary: get heap size test
test environment: SSC_T1_4
test point 1: basic function
test point 2: 'get heap size '
version: v1 (2016-8-15)
- CI ready: 'No'
ID: SYS_MISC_5001
SDK: |-
8266_NonOS
8266_RTOS
Test App: SSC
auto test: 'Yes'
category: Stress
cmd set: ''
execution time: 12.0
expected result: 4.target1正常运行无异常
initial condition: None
level: Integration
module: System
steps: |-
1.target1、target2通过UART与PC相连接
2.target1的晶振为40MHz晶振烧录SDK的时候选择26MHz晶振
3.target2的GPIO PIN脚通过排线与target1的电源相连接target1与target2 GND通过排线连接
4.PC发送命令控制target2使GPIO不停的拉高拉低
sub module: Misc
summary: random reboot to confirm default init data bin will not overwrite user
config
test environment: SSC_T1_InitData
test point 1: stress
test point 2: reboot when using user defined init data bin
version: v1 (2016-8-15)

View File

@ -1,57 +0,0 @@
test cases:
- CI ready: SpecialJob
ID: SYS_NVS_01001
SDK: ESP32_IDF
Test App: SSC_BLE_WIFI
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- NVSTest/NVSCompatibleWiFi
- - nvs_path = "nvs_bin_folder"
- - ''
execution time: 0
expected result: |
1. succeed
2. succeed
3. succeed
4. succeed
initial condition: None
level: Integration
module: System
steps: |
1. get NVS data from earlier released branches and last master
2. download each NVS data to target
3. check if auto connected to the same AP
4. check if SoftAP config is correct
sub module: NVS
summary: use old NVS data WIFI function test
test environment: SSC_T1_5
test point 1: compatiable test
test point 2: test if latest SDK work with pervious version of NVS data
version: v1 (2017-06-01)
- CI ready: 'No'
ID: SYS_NVS_5001
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: Reboot
auto test: 'Yes'
category: Stress
cmd set: ''
execution time: 12.0
expected result: 3.无异常发生
initial condition: None
level: Integration
module: System
steps: |-
1.target1、target2通过UART与PC相连接
2.target2的GPIO PIN脚通过排线与target1的电源相连接target1与target2 GND通过排线连接
3.PC发送命令控制target2使GPIO不停的拉高拉低
sub module: NVS
summary: random reboot when access NVS
test environment: NVS_T1_1
test point 1: stress
test point 2: reboot when accessing NVS
version: v1 (2016-8-15)

View File

@ -1,995 +0,0 @@
test cases:
- CI ready: 'Yes'
ID: TCPIP_DHCP_0101
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 dhcp -E -o 1
- - R SSC1 C +DHCP:STA,OK
- - SSC SSC1 ip -S -i 0.0.0.0
- - R SSC1 C +IP
- - SSC SSC1 sta -C -s <ap_ssid> -p <ap_password>
- - ''
- - DELAY 20
- - P PC_COM C +DELAYDONE
- P SSC1 NC +JAP:CONNECTED
- - SSC SSC1 dhcp -S -o 1
- - R SSC1 C +DHCP:STA,OK
- - SSC SSC1 ip -Q
- - R SSC1 C +STAIP:0.0.0.0
- - SSC SSC1 sta -C -s <ap_ssid> -p <ap_password>
- - R SSC1 C +JAP:CONNECTED
- - SSC SSC1 ip -Q
- - R SSC1 RE "\+STAIP:%%s"%%(<target_ip>)
execution time: 0.0
expected result: "1.target1 关闭DHCP OK\n2.target1 设置ip add OK\n3.target1 连接AP fail\n4.target1
打开DHCP OK\n5.查询到sta ip \n6.target1 连接AP ok\n7.查询到sta ip 为target_ip"
initial condition: STAM1
level: Integration
module: TCPIP
steps: "1.target1 关闭DHCP OK\n2.target1 设置ip add OK\n3.target1 连接AP fail\n4.target1
打开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_5
test point 1: basic function
test point 2: DHCP client function test
version: v2 (2016-10-19)
- CI ready: 'Yes'
ID: TCPIP_DHCP_0103
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 op -S -o 3
- - R SSC1 C +MODE:OK
- - SSC SSC1 dhcp -S -o 3
- - R SSC1 C +DHCP:AP,OK C +DHCP:STA,OK
- - SSC SSC1 dhcp -Q -o 3
- - R SSC1 C +DHCP:STA,STARTED C +DHCP:AP,STARTED
- - SSC SSC1 dhcp -Q -o 1
- - R SSC1 C +DHCP:STA,STARTED NC +DHCP:AP,STARTED
- - SSC SSC1 dhcp -Q -o 2
- - R SSC1 NC +DHCP:STA,STARTED C +DHCP:AP,STARTED
- - SSC SSC1 dhcp -E -o 3
- - R SSC1 C +DHCP:AP,OK C +DHCP:STA,OK
- - SSC SSC1 dhcp -Q -o 3
- - R SSC1 C +DHCP:STA,STOPPED C +DHCP:AP,STOPPED
execution time: 0.0
expected result: |-
1.OK
2.OK
3.STA&AP STARTED
4.STA STARTED
5.AP STARTED
6.OK
7.STA&AP STOPPED
initial condition: STAM1
level: Integration
module: TCPIP
steps: |-
1.target1 设置mode 为sta+softAP mode
2.target1 打开DHCP 3
3.target1 查询DHCP 状态
4.target1 查询sta DHCP 状态
5.target1 查询softAP DHCP 状态
6.target1 关闭 DHCP 3
7.target1 查询 DHCP 状态
sub module: DHCP
summary: dhcp status query
test environment: SSC_T1_4
test point 1: basic function
test point 2: DHCP client function test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_DHCP_0201
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 ip -S -o 2 -i <target_ap_ip>
- - R SSC1 C +IP:OK
- - SSC SSC1 dhcp -L -s 192.168.4.2 -e 192.168.4.100
- - R SSC1 C +DHCP:LEASE,OK
- - SSC SSC1 dhcp -L -s 192.168.4.1 -e 192.168.4.10
- - R SSC1 C +DHCP:LEASE,ERROR
- - SSC SSC1 dhcp -L -s 192.168.4.5 -e 192.168.4.2
- - R SSC1 C +DHCP:LEASE,ERROR
- - SSC SSC1 dhcp -L -s 192.168.2.2 -e 192.168.2.5
- - R SSC1 C +DHCP:LEASE,ERROR
- - SSC SSC1 dhcp -S -o 2
- - R SSC1 C +DHCP:AP,OK
execution time: 0.0
expected result: |-
1.target1 关闭DHCP 2 OK
2.target1 设置ip 成功
3.设置dhcp 地址池 OK
4.ERROR
5.ERROR
6.ERROR
7.target1 打开DHCP ok
initial condition: APM1
level: Integration
module: TCPIP
steps: "1.target1 关闭DHCP 2 \n2.target1 设置ip \n3.设置dhcp 地址池\n4.设置dhcp错误的参数\n5.设置dhcp错误的参数\n6.设置dhcp错误的参数\n7.target1
打开DHCP ok"
sub module: DHCP
summary: server dhcp lease test
test environment: SSC_T1_4
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_DHCP_0202
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <random_string> -p <random_string> -t 4
- - R SSC1 C +SAP:OK
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 dhcp -L -s 192.168.4.2 -e 192.168.4.100
- - R SSC1 C +DHCP:LEASE,OK
- - SSC SSC1 dhcp -S -o 2
- - R SSC1 C +DHCP:AP,OK
- - LOOP 3 4 "['01','02','03']" "[2,3,4]"
- - ''
- - SSC SSC2 sta -D
- - R SSC2 C +QAP:OK
- - SSC SSC2 mac -S -o 1 -m 10:22:33:44:55:{%s}
- - R SSC2 C +MAC:STA,OK
- - SSC SSC2 sta -C -s <random_string> -p <random_string>
- - R SSC2 C +JAP:CONNECTED
- - SSC SSC2 ip -Q -o 1
- - R SSC2 C +STAIP:192.168.4.{%s}
execution time: 0.0
expected result: |-
1. succeed
2. succeed
3,4: get IP from dhcp pool with correct sequence
initial condition: T2_1
level: Integration
module: TCPIP
steps: |-
1. config softap to a random ssid
2. config DHCP Server on Target1
3. target change mac, connect to Target1
4. Loop step3
sub module: DHCP
summary: dhcp server ip pool
test environment: SSC_T2_5
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_DHCP_0203
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <random_string> -p <random_string> -t 4
- - R SSC1 C +SAP:OK
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 dhcp -L -s 192.168.4.2 -e 192.168.4.3
- - R SSC1 C +DHCP:LEASE,OK
- - SSC SSC1 dhcp -S -o 2
- - R SSC1 C +DHCP:AP,OK
- - LOOP 2 4 "['01','02']" "[2,3]"
- - ''
- - SSC SSC2 sta -D
- - R SSC2 C +QAP:OK
- - SSC SSC2 mac -S -o 1 -m 10:22:33:44:55:{%s}
- - R SSC2 C +MAC:STA,OK
- - SSC SSC2 sta -C -s <random_string> -p <random_string>
- - R SSC2 C +JAP:CONNECTED
- - SSC SSC2 ip -Q -o 1
- - R SSC2 C +STAIP:192.168.4.{%s}
- - SSC SSC2 mac -S -o 1 -m 10:22:33:44:55:66
- - R SSC2 C +MAC:STA,OK
- - DELAY 20
- - ''
- - SSC SSC2 ip -Q -o 1
- - R SSC2 C +STAIP:0.0.0.0
execution time: 0.0
expected result: |-
1. succeed
2. succeed
3. succeed
4.1 succeed
4.2 failed
initial condition: T2_1
level: Integration
module: TCPIP
steps: |-
1. config softap to a random ssid
2. config DHCP Server on Target1(.4.2 - .4.3)
3. target change mac, connect to Target1
4. Loop step3 twice
sub module: DHCP
summary: dhcp server ip pool empty
test environment: SSC_T2_5
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_DHCP_0204
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <random_string> -p <random_string> -t 4
- - R SSC1 C +SAP:OK
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 dhcp -L -s 192.168.4.2 -e 192.168.4.3 -t 1
- - R SSC1 C +DHCP:LEASE,OK
- - SSC SSC1 dhcp -S -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC2 sta -C -s <random_string> -p <random_string>
- - R SSC2 C +JAP:CONNECTED
- - SSC SSC2 ip -Q -o 1
- - R SSC2 C +STAIP:192.168.4.2
- - DELAY 90
- - ''
- - SSC SSC2 ip -Q -o 1
- - R SSC2 C +STAIP:192.168.4.2
- - SSC SSC2 sta -D
- - R SSC2 C +JAP:DISCONNECTED
- - DELAY 60
- - ''
- - SSC SSC2 mac -S -o 1 -m 10:22:33:44:55:66
- - R SSC2 C +MAC:STA,OK
- - SSC SSC2 sta -C -s <random_string> -p <random_string>
- - R SSC2 C +JAP:CONNECTED
- - SSC SSC2 ip -Q -o 1
- - R SSC2 C +STAIP:192.168.4.2
execution time: 0.0
expected result: |-
1. succeed
2. succeed
3. get IP 192.168.4.2
5. succeed
6. succeed
8. get IP 192.168.4.2
initial condition: T2_1
level: Integration
module: TCPIP
steps: |-
1. config softap to a random ssid
2. config DHCP timeout as 1 minute
3. target2 connect to target1
4. wait 90 seconds
5. check if target2 IP is same
6. target2 disconnect
7. wait 60s
8. target2 change mac and connect to target1
sub module: DHCP
summary: dhcp server timeout test
test environment: SSC_T2_5
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_DHCP_0205
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <random_string> -p <random_string> -t 4
- - R SSC1 C +SAP:OK
- - SSC SSC2 sta -C -s <random_string> -p <random_string>
- - R SSC2 C +JAP:CONNECTED
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 dhcp -L -s 192.168.4.2 -e 192.168.4.3 -t 1
- - P SSC1 C +DHCP:LEASE,OK
- - SSC SSC1 dhcp -S -o 2
- - P SSC1 C +DHCP:AP,OK
- P SSC2 C +JAP:DISCONNECTED
execution time: 0.0
expected result: |-
1. succeed
2. succeed
3. target2 wifi disconnected
initial condition: T2_1
level: Integration
module: TCPIP
steps: |-
1. config softap to a random ssid
2. target2 connect to target1
3. disable DHCP server, do config and enable
sub module: DHCP
summary: disconnect STA if config dhcp server
test environment: SSC_T2_5
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_DHCP_0206
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <random_string> -p <random_string> -t 4
- - R SSC1 C +SAP:OK
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 dhcp -L -s 192.168.4.2 -e 192.168.4.100
- - R SSC1 C +DHCP:LEASE,OK
- - SSC SSC1 dhcp -S -o 2
- - R SSC1 C +DHCP:AP,OK
- - LOOP 4 4 "['01','02','03','01']" "[2,3,4,2]"
- - ''
- - SSC SSC2 sta -D
- - R SSC2 C +QAP:OK
- - SSC SSC2 mac -S -o 1 -m 10:22:33:44:55:{%s}
- - R SSC2 C +MAC:STA,OK
- - SSC SSC2 sta -C -s <random_string> -p <random_string>
- - R SSC2 C +JAP:CONNECTED
- - SSC SSC2 ip -Q -o 1
- - R SSC2 C +STAIP:192.168.4.{%s}
execution time: 0.0
expected result: |-
1. succeed
2. succeed
4. get IP 192.168.4.2 - 192.168.4.4
5. get IP 192.168.4.2
initial condition: T2_1
level: Integration
module: TCPIP
steps: |-
1. config softap to a random ssid
2. disable DHCP server, do config and enable
3. target2 change mac, connect to softap, disconnect
4. Loop step3 twice
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_5
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_DHCP_0207
SDK: |-
8266_NonOS
8266_RTOS
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <random_string> -p <random_string> -t 4
- - R SSC1 C +SAP:OK
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 dhcp -L -s 192.168.4.2 -e 192.168.4.100
- - 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
- - WIFI <pc_wifi_nic> DISCONN2
- - R PC_COM NC ERROR C +WIFIDISCONN:OK
- - SSC SSC2 sta -D
- - R SSC2 C +QAP:OK
- - SSC SSC2 mac -S -o 1 -m 10:22:33:44:55:66
- - R SSC2 C +MAC:STA,OK
- - SSC SSC2 sta -C -s <random_string> -p <random_string>
- - R SSC2 C +JAP:CONNECTED
- - SSC SSC2 ip -Q -o 1
- - R SSC2 C +STAIP:192.168.4.2
execution time: 0.0
expected result: |-
1. succeed
2. succeed
3. get IP 192.168.4.2
4. succeed
5. succeed
6. get IP 192.168.4.2
initial condition: T2_1
level: Integration
module: TCPIP
steps: |-
1. config softap to a random ssid
2. disable DHCP server, do config and enable
3. PC WIFI NIC connect to target1 softap
4. target2 connect to target1 softap and disnnect
5. PC release IP and disconnected
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_2
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_DHCP_0207
SDK: ESP32_IDF
Test App: SSC
allow fail: '1/2'
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <random_string> -p <random_string> -t 4
- - R SSC1 C +SAP:OK
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 dhcp -L -s 192.168.4.2 -e 192.168.4.100
- - 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
- - WIFI <pc_wifi_nic> DISCONN2
- - R PC_COM NC ERROR C +WIFIDISCONN:OK
- - SSC SSC2 sta -D
- - R SSC2 C +QAP:OK
- - SSC SSC2 mac -S -o 1 -m 10:22:33:44:55:66
- - R SSC2 C +MAC:STA,OK
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 dhcp -S -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC2 sta -C -s <random_string> -p <random_string>
- - R SSC2 C +JAP:CONNECTED
- - SSC SSC2 ip -Q -o 1
- - R SSC2 C +STAIP:192.168.4.2
execution time: 0.0
expected result: |-
1. succeed
2. succeed
3. get IP 192.168.4.2
4. succeed
5. succeed
6. succeed
7. get IP 192.168.4.2
initial condition: T2_1
level: Integration
module: TCPIP
steps: |-
1. config softap to a random ssid
2. disable DHCP server, do config and enable
3. PC WIFI NIC connect to target1 softap
4. target2 connect to target1 softap and disnnect
5. PC release IP and disconnected
6. disable DHCP server and enable
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_2
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_DHCP_0208
SDK: |-
8266_NonOS
8266_RTOS
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <random_string> -p <random_string> -t 4
- - R SSC1 C +SAP:OK
- - SSC SSC2 sta -C -s <random_string> -p <random_string>
- - R SSC2 C +JAP:CONNECTED
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 dhcp -L -s 192.168.4.2 -e 192.168.4.100
- - R SSC1 C +DHCP:LEASE,OK
- - SSC SSC1 dhcp -S -o 2
- - P SSC1 C +DHCP:AP,OK
- P SSC2 C +JAP:DISCONNECTED
- - SSC SSC2 sta -D
- - R SSC2 C +JAP:DISCONNECTED
- - 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 SSC1 ap -L
- - R SSC1 C 192.168.4.2 P <pc_wifi_nic_mac>
execution time: 0.0
expected result: |-
1. succeed
2. succeed
3. succeed
4. get IP 192.168.4.2
5. can only find target2 with IP 192.168.4.2
initial condition: T2_1
level: Integration
module: TCPIP
steps: |-
1. config softap to a random ssid
2. target2 connect to target1 softap
3. disable DHCP server, do config and enable
4. PC NIC connect to target1 softap
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_2
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_DHCP_0208
SDK: ESP32_IDF
Test App: SSC
allow fail: '2/3'
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <random_string> -p <random_string> -t 4
- - R SSC1 C +SAP:OK
- - SSC SSC2 sta -C -s <random_string> -p <random_string>
- - R SSC2 C +JAP:CONNECTED
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 dhcp -L -s 192.168.4.2 -e 192.168.4.100
- - R SSC1 C +DHCP:LEASE,OK
- - SSC SSC1 dhcp -S -o 2
- - P SSC1 C +DHCP:AP,OK
- P SSC2 C +JAP:DISCONNECTED
- - SSC SSC2 sta -D
- - R SSC2 C OK
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,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 SSC1 ap -L
- - R SSC1 C 192.168.4.2 P <pc_wifi_nic_mac>
execution time: 0.0
expected result: |-
1. succeed
2. succeed
3. succeed
4. succeed
5. succeed
6. succeed
7. can only find target2 with IP 192.168.4.2
initial condition: T2_1
level: Integration
module: TCPIP
steps: |-
1. config softap to a random ssid
2. target2 connect to target1 softap
3. disable DHCP server, do config and enable
4. target2 disconnect
5. disable DHCP server and enable
6. PC NIC connect to target1 softap
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_2
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_DHCP_0209
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: '2/3'
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <random_string> -p <random_string> -t 4
- - R SSC1 C +SAP:OK
- - SSC SSC2 sta -C -s <random_string> -p <random_string>
- - R SSC2 C +JAP:CONNECTED
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 dhcp -L -s 192.168.4.2 -e 192.168.4.100
- - 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
- - DELAY 20
- - ''
- - SSC SSC1 ap -L
- - R SSC1 C 192.168.4.2 C 192.168.4.3 P <pc_wifi_nic_mac> P <target2_mac>
execution time: 0.0
expected result: |-
1. succeed
2. succeed
3. succeed
4. succeed
5. find target2 and PC
initial condition: T2_1
level: Integration
module: TCPIP
steps: |-
1. config softap to a random ssid
2. target2 connect to target1 softap
3. disable DHCP server, do config and enable
4. PC NIC connect to target1 softap
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_2
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_DHCP_0210
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: '1/2'
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <random_string> -p <random_string> -t 4
- - R SSC1 C +SAP:OK
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 dhcp -L -s 192.168.4.2 -e 192.168.4.100
- - R SSC1 C +DHCP:LEASE,OK
- - SSC SSC1 dhcp -S -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC2 sta -C -s <random_string> -p <random_string>
- - R SSC2 C +JAP:CONNECTED
- - WIFI <pc_wifi_nic> CONN2 <random_string> <random_string> 192.168.4.2
- - R PC_COM NC ERROR C +WIFICONN:OK
- - SSC SSC1 ap -L
- - R SSC1 C 192.168.4.2 C 192.168.4.3 P <pc_wifi_nic_mac> P <target2_mac>
execution time: 0.0
expected result: |-
1. succeed
2. succeed
3. succeed
4. succeed
5. find target2 and PC
initial condition: T2_1
level: Integration
module: TCPIP
steps: |-
1. config softap to a random ssid
2. target2 connect to target1 softap
3. disable DHCP server, do config and enable
4. PC NIC connect to target1 softap try to renew IP 192.168.4.2
5. softap list connected station
sub module: DHCP
summary: dhcp server reconfig, old client able to get IP (discover with requested
IP)
test environment: SSC_T2_2
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_DHCP_0211
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: '1/2'
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <random_string> -p <random_string> -t 4
- - R SSC1 C +SAP:OK
- - WIFI <pc_wifi_nic> CONN <random_string> <random_string> 192.168.4.2
- - R PC_COM NC ERROR C +WIFICONN:OK
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 dhcp -L -s 192.168.4.2 -e 192.168.4.100
- - 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
- - ''
- - SSC SSC1 ap -L
- - R SSC1 C 192.168.4.2 C 192.168.4.3 P <pc_wifi_nic_mac> P <target2_mac>
execution time: 0.0
expected result: |-
1. succeed
2. succeed
3. succeed
4. succeed
5. find target2 and PC
initial condition: T2_1
level: Integration
module: TCPIP
steps: |-
1. config softap to a random ssid
2. target2 connect to target1 softap
3. disable DHCP server, do config and enable
4. PC NIC connect to target1 softap try to renew IP 192.168.4.2
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_2
test point 1: basic function
test point 2: DHCP server function test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_DHCP_0212
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <target_ssid> -p <target_password> -t <target_auth_enum>
- - R SSC1 C +SAP:OK
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password>
- - ''
- - DELAY 20
- - P PC_COM C +DELAYDONE
- P SSC2 NC +JAP:CONNECTED
- - SSC SSC1 dhcp -S -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password>
- - R SSC2 C +JAP:CONNECTED
execution time: 0.0
expected result: "1.target1 set AP OK \n2.target1 关闭DHCP OK\n3.target2 jap target
1,FAIL \n4.target1 打开DHCP OK\n5.target2 jap target 1,ok"
initial condition: T2_1
level: Integration
module: TCPIP
steps: "1.target1 set AP OK \n2.target1 关闭DHCP OK\n3.target2 jap target 1,FAIL \n4.target1
打开DHCP OK\n5.target2 jap target 1,ok"
sub module: DHCP
summary: dhcp server function test
test environment: SSC_T2_5
test point 1: basic function
test point 2: DHCP server function test
version: v2 (2016-10-19)
- CI ready: 'Yes'
ID: TCPIP_DHCP_0301
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 dhcp -E -o 1
- - R SSC1 C +DHCP:STA,OK
- - SSC SSC1 ip -S -i 192.168.123.123 -o 1
- - R SSC1 C +IP:OK
- - SSC SSC1 sta -C -s <ap_ssid> -p <ap_password>
- - R SSC1 C +JAP:CONNECTED
- - SSC SSC1 ip -S -i 0.0.0.0 -o 1
- - R SSC1 C +IP
- - SSC SSC1 sta -C -s <ap_ssid> -p <ap_password>
- - ''
- - DELAY 10
- - P PC_COM C +DELAYDONE
- P SSC1 NC +JAP:CONNECTED
execution time: 0.0
expected result: |-
1.OK
2.OK
3.JAP CONNETED
4.OK
5.等待10sJAP fail
initial condition: STAM1
level: Integration
module: TCPIP
steps: |-
1.target1 关闭DHCP 1
2.target1 设置sta ip 192.168.123.123
4.target1 jap AP
5.target1 设置sta ip 0.0.0.0
6.target1 jap AP
sub module: DHCP
summary: sta dhcp static ip interaction
test environment: SSC_T1_5
test point 1: interaction
test point 2: static IP and DHCP interaction test
version: v2 (2016-10-19)
- CI ready: 'Yes'
ID: TCPIP_DHCP_0302
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 dhcp -S -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 ip -S -i 192.168.123.123 -o 2
- - R SSC1 C +IP:ERROR
- - SSC SSC1 dhcp -L -s 192.168.2.2 -e 192.168.2.10
- - R SSC1 C +DHCP:LEASE,ERROR
- - SSC SSC1 ap -S -s <target_ssid> -p <target_password> -t <target_auth_enum>
- - ''
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password>
- - P SSC2 C +JAP:CONNECTED
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 ip -S -i 192.168.4.1 -o 2
- - R SSC1 C +IP:OK
- - SSC SSC1 dhcp -L -s 192.168.4.2 -e 192.168.4.10
- - R SSC1 C +DHCP:LEASE,OK
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password>
- - ''
- - DELAY 10
- - P PC_COM C +DELAYDONE
- P SSC2 NC +JAP:CONNECTED
execution time: 0.0
expected result: |-
1.target 1 OK
2.target1 ERROR
3.target1 ERROR
4.target2 jap target1 OK
5.target1 OK
6.target1 OK
7.target1 OK
8.target2 jap target1 OK
initial condition: T2_1
level: Integration
module: TCPIP
steps: "1.target1 打开DHCP 2\n2.target1 设置softAP ip 192.168.123.123\n3.target1 设置地址池\n4.target1下设置ssid
和pwd 加密方式\n5.target2 连接target1 \n6.target1 关闭DHCP 2\n7.target1 设置softAP ip \n8.target1
设置正确的地址池\n9.target2 连接target1 "
sub module: DHCP
summary: ap dhcp static ip interaction
test environment: SSC_T2_5
test point 1: interaction
test point 2: static IP and DHCP interaction test
version: v1 (2016-8-15)
- CI ready: 'No'
ID: TCPIP_DHCP_5001
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stress
cmd set:
- WiFiStress/SoftAPNSTA
- - sta_num = 4
- - dummy
- - max_sta = 3
- - ''
- - test_time = 300
- - ''
- - delay1 = [5, 60]
- - ''
- - delay2 = [1, 10]
- - ''
- - change_mac = False
- - ''
- - channel = 11
- - ''
execution time: 5.0
expected result: "1. succeed\n2. succeed\n3. JAP succeed except: \nsoftap reach
max connected AP \nor all address in dhcp pool not available"
initial condition: None
level: Integration
module: TCPIP
steps: |-
1. 1 target set to softap mode and rest set to sta mode
2. set a short dhcp server lease time
2. all sta set random mac, random join and disconnect from softap
Loop step 2
sub module: DHCP
summary: max sta connect to SotfAP and disconnect, sta number more than sta allowed
test environment: SSC_T5_1
test point 1: stress
test point 2: DHCP server stress test
version: v1 (2016-8-15)
- CI ready: 'No'
ID: TCPIP_DHCP_5101
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
auto test: 'No'
category: IOT
cmd set: ''
execution time: 0.1
expected result: |-
2. 成功
3. 成功
4. 断开连接并开始重连
5. WIFI连上但无法获取 IP等大概1分钟后发生 DHCP TIMEOUT断开连接并重连成功获取到 IP
initial condition: STAM1
level: Integration
module: TCPIP
steps: |-
1. 使用小米路由器青春版进行测试
2. 设置DHCP timeoutdhcp -T -n 6
3. target 连上 AP
4. 路由器断电
5. 路由器上电
sub module: DHCP
summary: DHCP timeout test on sepcial router
test environment: SSC_T1_IOT1
test point 1: interoperability
test point 2: DHCP timeout test
version: v1 (2016-8-15)

View File

@ -1,447 +0,0 @@
test cases:
- CI ready: 'Yes'
ID: TCPIP_DNS_0101
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: 1/2
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 soc -H -d gbot.espressif.cn
- - R SSC1 C +HOSTIP:OK,118.31.185.120
execution time: 0.0
expected result: 1.OK
initial condition: STAM2
level: Integration
module: TCPIP
steps: 1. get host name "gbot.espressif.cn"
sub module: DNS
summary: get host by name test
test environment: SSC_T1_2
test point 1: basic function
test point 2: DNS function test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_DNS_0102
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: 1/2
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 soc -H -d gbot.espressif.cn
- - R SSC1 A <ip_addr>:\+HOSTIP:OK,(.+)\r\n
- - SSC SSC1 soc -B -t TCP
- - R SSC1 A <sock1>:\+BIND:(\d+),OK
- - SSC SSC1 soc -C -s <sock1> -i <ip_addr> -p 9001
- - R SSC1 RE \+CONNECT:\d+,OK
- - SSC SSC1 soc -S -s <sock1> -l 10
- - P SSC1 RE \+SEND:\d+,OK
- P SSC1 SL <sock1>+10
execution time: 0.0
expected result: |-
1.OK
2.OK
initial condition: STAM2
level: Integration
module: TCPIP
steps: |-
1. get host name "gbot.espressif.cn"
2. connect, send, recv
sub module: DNS
summary: TCP connect to gbot.espressif.cn
test environment: SSC_T1_2
test point 1: basic function
test point 2: DNS function test
version: v2 (2016-10-19)
- CI ready: 'Yes'
ID: TCPIP_DNS_0103
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: 1/2
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 soc -H -d gbot.espressif.cn
- - R SSC1 A <ip_addr>:\+HOSTIP:OK,(.+)\r\n
- - SSC SSC1 soc -B -t UDP
- - R SSC1 A <sock1>:\+BIND:(\d+),OK
- - SSC SSC1 soc -S -s <sock1> -i <ip_addr> -p 9003 -l 10 -n 3 -j 1000
- - P SSC1 RE \+SEND:\d+,OK
- P SSC1 SL <sock1>+10
execution time: 0.0
expected result: |-
1.OK
2.send OK and recv at least one echo
initial condition: STAM2
level: Integration
module: TCPIP
steps: |-
1. get host name "espressif.cn"
2. sendto echo server 3 times
sub module: DNS
summary: UDP send to gbot.espressif.cn
test environment: SSC_T1_2
test point 1: basic function
test point 2: DNS function test
version: v2 (2016-10-19)
- CI ready: 'No'
ID: TCPIP_DNS_0201
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'No'
category: Function
cmd set: ''
execution time: 0.1
expected result: 2. failed
initial condition: None
level: Integration
module: TCPIP
steps: |-
1.AP的主、备用DNS server均设置为错误
2.target连接上AP 并访问正确的域名
sub module: DNS
summary: get host name with error DNS server
test environment: SSC_T1_2
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_0202
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'No'
category: Function
cmd set: ''
execution time: 0.1
expected result: 2. succeed
initial condition: None
level: Integration
module: TCPIP
steps: |-
1.AP的主DNS server设置为错误备用DNS server设置为正确
2.target连接上AP 并访问正确的域名
sub module: DNS
summary: get host name with error main DNS server and correct backup DNS server
test environment: SSC_T1_2
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

@ -1,68 +0,0 @@
test cases:
- CI ready: 'No'
ID: TCPIP_ICMP_0101
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: 1/5
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ping -i <pc_ip>
- - R SSC1 C +PING:OK
- - SSC SSC1 ping -i <pc_ip> -c 2
- - R SSC1 C +PING:OK
execution time: 0.0
expected result: |-
1.ok
2.ok
initial condition: STAM2
level: Integration
module: TCPIP
steps: |-
1.ping -i <pc_ip>
2.ping -i <pc_ip> -c 2
sub module: ICMP
summary: ping function test
test environment: SSC_T1_5
test point 1: basic function
test point 2: ping function test
version: v1 (2016-8-15)
- CI ready: 'No'
ID: TCPIP_ICMP_5001
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stress
cmd set:
- TCPIPStress/PingStress
- - test_time = 300
- - dummy
- - test_freq = 0.2
- - ''
- - ping_len = 64
- - ''
- - target_mode = "STA"
- - ''
execution time: 5.0
expected result: |-
1. send succeed
2. recv ping reply
initial condition: STAM2
level: Integration
module: TCPIP
steps: |-
1. PC send ping request to target
2. PC check if received ping reply
sub module: ICMP
summary: ping target and check for ping reply
test environment: SSC_T1_1
test point 1: stress
test point 2: ICMP ping stress test
version: v1 (2016-11-15)

File diff suppressed because it is too large Load Diff

View File

@ -1,85 +0,0 @@
test cases:
- CI ready: 'Yes'
ID: TCPIP_IP_0101
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 dhcp -S -o 1
- - R SSC1 C +DHCP:STA,OK
- - SSC SSC1 ip -S -o 1 -i 192.168.123.123
- - R SSC1 C +IP:ERROR
- - SSC SSC1 dhcp -E -o 1
- - R SSC1 C +DHCP:STA,OK
- - SSC SSC1 ip -S -o 1 -i 192.168.123.123
- - R SSC1 C +IP:OK
- - SSC SSC1 ip -Q -o 1
- - R SSC1 C +STAIP:192.168.123.123
execution time: 0.0
expected result: |-
1.OK
2.ERROR
3.OK
4.OK
5.STAIP:192.168.123.123
initial condition: STAM1
level: Integration
module: TCPIP
steps: "1.target1 打开DHCP 1\n2.target1 设置sta ip 192.168.123.123\n4.target1 关闭DHCP
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_4
test point 1: basic function
test point 2: set and query static IP
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: TCPIP_IP_0102
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 dhcp -S -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 ip -S -o 2 -i 192.168.123.123
- - R SSC1 C +IP:ERROR
- - SSC SSC1 dhcp -E -o 2
- - R SSC1 C +DHCP:AP,OK
- - SSC SSC1 ip -S -o 2 -i 192.168.123.123
- - R SSC1 C +IP:OK
- - SSC SSC1 ip -Q -o 2
- - R SSC1 C +APIP:192.168.123.123
- - SSC SSC1 ip -S -o 2 -i <target_ap_ip>
- - R SSC1 C +IP:OK
execution time: 0.0
expected result: |-
1.OK
2.ERROR
3.OK
4.OK
5.APIP:192.168.123.123
6.OK
initial condition: APM1
level: Integration
module: TCPIP
steps: "1.target1 打开DHCP 2\n2.target1 设置softAP ip 192.168.123.123\n4.target1 关闭DHCP
2\n5.target1 设置softAP ip 192.168.123.123\n6.target1 查询 当前sta ip \n7.target1 设置softAP
ip 为target_ap_ip"
sub module: IP
summary: ap set and query static ip test
test environment: SSC_T1_4
test point 1: basic function
test point 2: set and query static IP
version: v1 (2016-8-15)

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -1,99 +0,0 @@
test cases:
- CI ready: 'Yes'
ID: WIFI_ADDR_0101
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 op -S -o 3
- - R SSC1 C +MODE:OK
- - SSC SSC1 mac -S -o 1 -m 44:55:66:77:88:99
- - R SSC1 C +MAC:STA,OK
- - SSC SSC1 mac -S -o 2 -m 22:33:44:55:66:77
- - R SSC1 C +MAC:AP,OK
- - SSC SSC1 mac -Q -o 3
- - R SSC1 C +STAMAC:44:55:66:77:88:99 C +APMAC:22:33:44:55:66:77
- - SSC SSC1 mac -S -o 1 -m <target_mac>
- - R SSC1 C +MAC:STA,OK
- - SSC SSC1 mac -S -o 2 -m <target_ap_mac>
- - R SSC1 C +MAC:AP,OK
execution time: 0.0
expected result: |-
1.OK
2.ok
3.ok
4.ok
5.ok
6.ok
initial condition: T2_1
level: Integration
module: WIFI MAC
steps: "1.target1 设置mode 为sta+softAP mode\n2.target1 设置sta mode 下的mac \n3.target1
设置softAP mode 下的mac\n4.target1 查询softAP+sta 下的mac\n5.target1 设置sta mode 下的mac
为target1_mac\n6.target1 设置softAP mode 下的mac 为target1_ap_mac\n"
sub module: MAC Address
summary: set mac, query mac
test environment: SSC_T2_5
test point 1: basic function
test point 2: mac address function test
version: v1 (2016-8-15)
- CI ready: 'No'
ID: WIFI_ADDR_0102
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 mac -S -o 2 -m 44:55:66:77:88:99
- - R SSC1 C +MAC:AP,OK
- - SSC SSC1 ap -S -s <target_ssid> -p <target_password> -t <target_auth_enum>
- - ''
- - SSC SSC2 sta -S -b 44:55:66:77:88:99
- - R SSC2 RE \+SCAN:.+,44:55:66:77:88:99,
- - SSC SSC1 mac -S -o 2 -m <target_ap_mac>
- - R SSC1 C +MAC:AP,OK
- - SSC SSC2 mac -Q -o 1
- - R SSC2 A <target2_mac_tmp>:\+STAMAC:(.+)\r\n
- - SSC SSC2 mac -S -o 1 -m 22:33:44:55:66:77
- - R SSC2 C +MAC:STA,OK
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password>
- - P SSC2 C +JAP:CONNECTED
- - SSC SSC1 ap -L
- - R SSC1 C +LSTA:22:33:44:55:66:77
- - SSC SSC2 mac -S -o 1 -m <target2_mac>
- - R SSC2 C +MAC:STA,OK
execution time: 0.0
expected result: |-
1.OK
2.ok
3.ok
4.ok
5.ok
6.ok
7.ok
8.ok
9.ok
initial condition: T2_1
level: Integration
module: WIFI MAC
steps: "1.target1 设置sta mode下的mac 44:55:66:77:88:99\n2.target1下设置ssid 和pwd 加密方式\n3.target2
查询mac为44:55:66:77:88:99的ssid\n4.target1 设置sta mode下的mac target_ap_mac\n5.target2
查询sta mode 下的mac 为target2_mac_tmp\n6.target2 设置sta mode 下的mac 为22:33:44:55:66:77\n7.target2
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_5
test point 1: basic function
test point 2: mac address function test
version: v1 (2016-8-15)

View File

@ -1,29 +0,0 @@
test cases:
- CI ready: 'Yes'
ID: WIFI_AMSDU_5001
SDK: ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stress
cmd set:
- TCPStress/TCPAMSDUsendrecv
- - delay_config = [0, 0.01, 0.1, 0.5, 1]
- - dummy
- - send_count = 1000
- - ''
- - test_time = 300
- - ''
execution time: 12.0
expected result: 1. do not disconnect
initial condition: STAM2
level: Integration
module: WIFI MAC
steps: |-
1. PC and SSC1 connected to 天猫魔盒,do TCP pkts send/recv for a long time.
2.Loop executing step 1
sub module: A-MSDU
summary: test AMSDU send/rev
test environment: SSC_T1_AMSDU
test point 1: function + stress
test point 2: AMSDU send recv
version: v2 (2016-11-15)

File diff suppressed because it is too large Load Diff

View File

@ -1,135 +0,0 @@
test cases:
- CI ready: 'Yes'
ID: WIFI_MODE_0101
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <target_ssid> -p <target_password> -t <target_auth_enum>
- - R SSC1 C +SAP:OK
- - SSC SSC1 op -S -o 1
- - R SSC1 C +MODE:OK
- - SSC SSC1 dhcp -S -o 1
- - R SSC1 C +DHCP:STA,OK
- - SSC SSC1 sta -C -s <ap_ssid> -p <ap_password>
- - R SSC1 RE "\+JAP:CONNECTED,%%s"%%(<ap_ssid>)
- - SSC SSC2 sta -S
- - R SSC2 NP <target_ssid> C +SCANDONE
- - SSC SSC1 sta -D
- - R SSC1 C +QAP:OK
execution time: 0.0
expected result: |-
1.target1下设置ssid 和pwd 、加密方式成功
2.修改target 1的mode 为sta mode
3.target1的dhcp打开
4.target1成功连接上AP
5.target2上不能查询到target_ssid
6.target1断开AP
initial condition: T2O_1
level: Integration
module: WIFI MAC
steps: |-
1.target1下设置ssid 和pwd 加密方式
2.修改target1的mode 为sta mode
3.target1的dhcp打开
4.target1连接AP
5.target2查询target_ssid
6.target1断开AP
sub module: WIFI Mode
summary: mode switch test (sta mode)
test environment: SSC_T2_3
test point 1: basic function
test point 2: wifi mode fucntion
version: v1 (2016-8-15)
- CI ready: 'No'
ID: WIFI_MODE_0102
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <target_ssid> -p <target_password> -t <target_auth_enum>
- - R SSC1 C +SAP:OK
- - SSC SSC2 sta -S
- - R SSC2 P <target_ssid>
- R SSC2 C +SCANDONE
- - SSC SSC1 sta -C -s <ap_ssid> -p <ap_password>
- - R SSC1 C +JAP:ERROR
- - SSC SSC1 sta -D
- - R SSC1 C +QAP:ERROR
execution time: 0.0
expected result: |-
1. target1 set AP
2.target 2 上查询到target_ssid
3. target1 can't join AP
4. target1 can't QAP
initial condition: T2O_1
level: Integration
module: WIFI MAC
steps: |-
1.target1下设置ssid 和pwd 加密方式
2.target 2 上查询target_ssid
3.target1 join AP
4.target1 DISCONN AP
sub module: WIFI Mode
summary: mode switch test (AP mode)
test environment: SSC_T2_3
test point 1: basic function
test point 2: wifi mode fucntion
version: v1 (2016-8-15)
- CI ready: 'No'
ID: WIFI_MODE_0103
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 op -S -o 3
- - R SSC1 C +MODE:OK
- - SSC SSC1 ap -S -s <target_ssid> -p <target_password> -t <target_auth_enum>
- - R SSC1 C +SAP:OK
- - SSC SSC1 dhcp -S -o 1
- - R SSC1 C +DHCP:STA,OK
- - SSC SSC1 sta -C -s <ap_ssid> -p <ap_password>
- - R SSC1 RE "\+JAP:CONNECTED,%%s"%%(<ap_ssid>)
- - SSC SSC2 sta -S
- - R SSC2 P <target_ssid>
- R SSC2 C +SCANDONE
execution time: 0.0
expected result: |-
1.target1 change to AP mode
2.target1 set AP
3.target 1 的dhcp 打开
4.target 1 成功连接上AP
5.target 2 上查询到target_ssid
initial condition: T2O_1
level: Integration
module: WIFI MAC
steps: |-
1.target1 change to AP mode
2.target1下设置ssid 和pwd 加密方式
3.target1 的dhcp 打开
4.target1 连接AP
5.target2 上查询target_ssid
sub module: WIFI Mode
summary: mode switch test (STA+AP mode)
test environment: SSC_T2_3
test point 1: basic function
test point 2: wifi mode fucntion
version: v1 (2016-8-15)

View File

@ -1,931 +0,0 @@
test cases:
- CI ready: 'Yes'
ID: WIFI_SCAN_0101
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC2 sta -S -s .,juhg123
- - 'R SSC2 NC +SCAN: C +SCANDONE'
- - SSC SSC1 ap -S -s <target_tmp_ssid> -p 123456789 -t 3
- - R SSC1 C +SAP:OK
- - SSC SSC2 sta -S -s <target_tmp_ssid>
- - 'R SSC2 C +SCAN:'
- R SSC2 P <target_tmp_ssid>
- 'R SSC2 NC +SCAN: C +SCANDONE'
execution time: 0.0
expected result: |-
1.target 2上不能scan .,juhg123
2.target1 set AP
3.target2上查询到<target_tmp_ssid>
initial condition: T2_1
level: Integration
module: WIFI MAC
steps: |-
1.target 2 scan .,juhg123
2.target1下设置ssid 和pwd 加密方式
3.target2 scan <target_tmp_ssid>
sub module: WIFI Scan
summary: scan with scan config ssid
test environment: SSC_T2_5
test point 1: basic function
test point 2: scan with different config
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: WIFI_SCAN_0102
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC2 sta -S -b ff:ff:ff:ff:ff:11
- - 'R SSC2 NC +SCAN: C +SCANDONE'
- - SSC SSC2 sta -S -b <target_ap_mac>
- - R SSC2 RE "\+SCAN:.+,%%s"%%(<target_ap_mac>)
- 'R SSC2 NC +SCAN: C +SCANDONE'
execution time: 0.0
expected result: |-
1.target2 上不能查询到此mac
2.target2上查询到<target_ap_mac>
initial condition: T2_1
level: Integration
module: WIFI MAC
steps: |-
1.target2 上查询此macff:ff:ff:ff:ff:11
2.target2上查询<target_ap_mac>
sub module: WIFI Scan
summary: scan with scan config bssid
test environment: SSC_T2_5
test point 1: basic function
test point 2: scan with different config
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: WIFI_SCAN_0103
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 sta -D
- - 'R SSC1 C +QAP:'
- - SSC SSC1 ap -S -s <target_tmp_ssid> -p 123456789 -t 3 -n 6
- - R SSC1 C +SAP:OK
- - SSC SSC2 sta -S -n 5
- - R SSC2 NP <target_tmp_ssid> C +SCANDONE
- - SSC SSC2 sta -S -n 6
- - 'R SSC2 C +SCAN:'
- R SSC2 P <target_tmp_ssid>
execution time: 0.0
expected result: |-
1.target1 QAP
2. target1 set AP,set channel 6
3.target2 上scan不到 channel 5
4.target2 上查询channel 6的<target_tmp_ssid>
initial condition: T2_1
level: Integration
module: WIFI MAC
steps: |-
1.target1 断开连接AP
2.target1下设置ssid 和pwd 加密方式,set channel 6
3.target2 上scan channel 5
4.target2 上查询channel 6的<target_tmp_ssid>
sub module: WIFI Scan
summary: scan with scan config channel
test environment: SSC_T2_5
test point 1: basic function
test point 2: scan with different config
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: WIFI_SCAN_0104
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <target_tmp_ssid> -p 123456789 -t 3 -h 0
- - R SSC1 C +SAP:OK
- - SSC SSC2 sta -D
- - R SSC2 C OK
- - SSC SSC2 sta -S -h 0
- - R SSC2 P <target_tmp_ssid> C +SCANDONE
- - SSC SSC2 sta -S -h 1
- - R SSC2 P <target_tmp_ssid> C +SCANDONE
- - SSC SSC1 ap -S -s <target_tmp_ssid> -p 123456789 -h 1
- - R SSC1 C +SAP:OK
- - SSC SSC2 sta -S -h 0
- - R SSC2 NP <target_tmp_ssid> C +SCANDONE
- - SSC SSC2 sta -S -h 1
- - R SSC2 P <target_ap_mac> C +SCANDONE
execution time: 0.0
expected result: |-
1.target1 set AP,set ssid broad cast
2.target 2上scan <target_tmp_ssid>
3.target 2上scan <target_tmp_ssid>
4.target1 set AP,set ssid hidden,
5.target 2上不能查询到 <target_tmp_ssid>
6.target 2上查询到<target_ap_mac>
initial condition: T2_1
level: Integration
module: WIFI MAC
steps: |-
1.target1下设置ssid 和pwd 加密方式,set ssid broad cast
2.target 2上scan <target_tmp_ssid>
3.target 2上scan <target_tmp_ssid>
4.target1下设置ssid 和pwd 加密方式,set ssid hidden,
5.target 2上查询 <target_tmp_ssid>
6.target 2上查询<target_ap_mac>
sub module: WIFI Scan
summary: scan with scan config show hidden
test environment: SSC_T2_5
test point 1: basic function
test point 2: scan with different config
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: WIFI_SCAN_0105
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 sta -D
- - 'R SSC1 C +QAP:'
- - SSC SSC1 ap -S -s <target_tmp_ssid> -p 123456789 -t 3 -h 0 -n 11
- - R SSC1 C +SAP:OK
- - SSC SSC2 sta -S -s <target_tmp_ssid> -b <target_ap_mac> -n 11
- - R SSC2 P <target_tmp_ssid> C +SCANDONE
- - SSC SSC2 sta -S -s <target_ssid> -b <target_ap_mac> -n 11
- - R SSC2 NP <target_tmp_ssid> C +SCANDONE
- - SSC SSC2 sta -S -s <target_tmp_ssid> -b ff:ff:ff:ff:ff:11 -n 11
- - R SSC2 P <target_tmp_ssid>
- R SSC2 NP <target_tmp_ssid> C +SCANDONE
- - SSC SSC2 sta -S -s <target_tmp_ssid> -b <target_ap_mac> -n 10
- - R SSC2 P <target_tmp_ssid>
- R SSC2 NP <target_tmp_ssid> C +SCANDONE
execution time: 0.0
expected result: |-
1.target1 QAP
2. target1 set AP,set ssid broad cast,set channel 11
3.target2 上查询到<target_tmp_ssid>
4.target2 上查询不到<target_tmp_ssid>
5.target2 上查询不到<target_tmp_ssid>
6.target2 上查询不到<target_tmp_ssid>
initial condition: T2_1
level: Integration
module: WIFI MAC
steps: |-
1.target1 QAP
2. target1 set AP,set ssid broad cast,set channel 11
3.target2 上查询到<target_tmp_ssid>
4.target2 上查询不到<target_tmp_ssid>
5.target2 上查询不到<target_tmp_ssid>
6.target2 上查询不到<target_tmp_ssid>
sub module: WIFI Scan
summary: scan with several configs
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: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <target_ssid> -p <target_password> -t <target_auth_enum>
- - R SSC1 C +SAP:OK
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -d 0 -b <target1_ap_mac>
- - P SSC2 C +JAP:CONNECTED
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -d 1 -b <target1_ap_mac>
- - P SSC2 C +JAP:CONNECTED
execution time: 0.0
expected result: |-
1.OK
2.ok
3.ok
initial condition: T2_1
level: Integration
module: WIFI MAC
steps: |-
1.target1下设置ssid 和pwd 加密方式
2.target2 jap
3.target2 conn target1 by bssid
sub module: WIFI Scan
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)
- CI ready: 'No'
ID: WIFI_SCAN_0203
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <target_ssid> -p <target_password> -t 3
- - R SSC1 C +SAP:OK
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 0 -j 0
- - P SSC2 C +JAP:CONNECTED
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 0 -j 1
- - P SSC2 C +JAP:CONNECTED
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 0 -j 2
- - P SSC2 C +JAP:CONNECTED
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 0 -j 3
- - P SSC2 C +JAP:CONNECTED
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 0 -j 5
- - ''
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 1 -j 1
- - P SSC2 C +JAP:CONNECTED
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 1 -j 2
- - P SSC2 C +JAP:CONNECTED
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 1 -j 3
- - P SSC2 C +JAP:CONNECTED
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 1 -j 0
- - P SSC2 C +JAP:CONNECTED
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 1 -j 4
- - ''
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 3 -j 0
- - P SSC2 C +JAP:CONNECTED
execution time: 0.0
expected result: |-
1.OK 2.ok
3.ok
4.ok
5.ok
7.ok
8.ok
9.ok
10.ok
12.ok
initial condition: T2_1
level: Integration
module: WIFI MAC
steps: |-
1.target1下设置ssid 和pwd 加密方式
2.target2 fast scan and jap target1
3.target2 jap target1 except open encrypt
4.target2 jap target1 except open and wep encrypt
5.target2 jap target1 only wpa2 encrypt can be connect
6.target2 scan all channel jap target1 except open encrypt
7.target2 scan all channel jap target1 except open encrypt
8.target2 scan all channel jap target1 except open and wep encrypt
9.target2 scan all channel jap target1 only wpa2 encrypt can be connected
10.target2 scan all channel jap target1
11.target2 scan all channel jap target1
12.target2 jap target1
sub module: WIFI Scan
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)
- CI ready: 'No'
ID: WIFI_SCAN_0204
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <target_ssid> -p <target_password> -t 2
- - R SSC1 C +SAP:OK
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 0 -q 0
- - ''
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 0 -q 128
- - ''
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 0 -q 80
- - P SSC2 C +JAP:CONNECTED
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 1 -q 128
- - ''
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 1 -q 0
- - ''
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 1 -q 80
- - P SSC2 C +JAP:CONNECTED
execution time: 0.0
expected result: |-
1.OK
2.no exception
3.no exception
4.ok
5.no exception
6.no exception
7.ok
initial condition: T2_1
level: Integration
module: WIFI MAC
steps: |-
1.target1下设置ssid 和pwd 加密方式
2.target2 fast scan and jap target1 rssi>-1
3.target2 fast scan and jap rssi>-127
4.target2 scan all channel and jap target1 rssi>-80
5.target2 scan all channel and jap rssi > -127
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 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)
- CI ready: 'No'
ID: WIFI_SCAN_0205
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <target_ssid> -p <target_password> -t 3
- - R SSC1 C +SAP:OK
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 1 -x 0
- - P SSC2 C +JAP:CONNECTED
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 1 -x 1
- - P SSC2 C +JAP:CONNECTED
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password> -f 1 -x 2
- - P SSC2 C +JAP:CONNECTED
execution time: 0.0
expected result: |-
1.OK
2.ok
3.ok
4.ok
initial condition: T2_1
level: Integration
module: WIFI MAC
steps: |-
1.target1下设置ssid 和pwd 加密方式
2.target2 scan ap all channel and jap target1 by rssi sort
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 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)
- CI ready: 'No'
ID: WIFI_SCAN_0206
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 op -S -o 1
- - P SSC1 C +MODE:OK
- - SSC SSC1 op -Q
- - P SSC1 C +CURMODE:1
- - SSC SSC1 sta -S -t 0 -l 0 -m 0
- - 'R SSC1 C +SCAN: C +SCANDONE'
- - SSC SSC1 sta -S -t 0 -l 1000 -m 100
- - 'R SSC1 C +SCAN: C +SCANDONE'
- - SSC SSC1 sta -S -t 1 -k 0
- - 'R SSC1 C +SCAN: C +SCANDONE'
- - SSC SSC1 sta -S -t 1 -k 2000
- - 'R SSC1 C +SCAN: C +SCANDONE'
- - SSC SSC1 sta -S -t 5 -k 100
- - 'R SSC1 C +SCAN: C +SCANDONE'
execution time: 0.0
expected result: |-
1.OK
2.ok
3.scan ok
4.scan ok
5.scan ok
6.scan ok
7.scan ok
initial condition: None
level: Integration
module: WIFI MAC
steps: |-
1.target set as sta
2.check target1 work mode
3.target1 active scan max and min time set to 0ms
4.target1 active scan max time 1000ms min time 100ms
5.target1 passive scan scan time 0ms
6.target passive scan scan time 10000ms
7.target1 scan type set to 5
sub module: WIFI Scan
summary: do active/passive scan
test environment: SSC_T1_4
test point 1: basic function
test point 2: scan function test
version: v1 (2016-8-15)
- CI ready: 'Yes'
ID: WIFI_SCAN_0301
SDK: ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 sta -S
- - ''
- - SSC SSC1 sta -S
- - P SSC1 C +SCANFAIL
- 'P SSC1 C +SCAN:'
- R SSC1 C +SCANDONE
execution time: 0.0
expected result: |-
1. second scan failed
2. first scan succeed
initial condition: STAM1
level: Integration
module: WIFI MAC
steps: |-
1. do all channel scan
2. do scan before scan finished
sub module: WIFI Scan
summary: reject scan request before scan finished
test environment: SSC_T1_5
test point 1: interaction
test point 2: Scan interact with other WiFi operation
version: v1 (2015-8-15)
- CI ready: 'Yes'
ID: WIFI_SCAN_0302
SDK: ESP32_IDF
Test App: SSC
allow fail: '2/3'
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 sta -C -s <ap_ssid> -p <ap_password>
- - R SSC1 C +JAP:CONNECTED
- - SSC SSC1 soc -B -t UDP -p <test_udp_port1>
- - R SSC1 A <sock1>:BIND:(\d+),OK
- - SSC SSC1 soc -S -s <sock1> -i <pc_ip> -p <test_udp_port1> -n 1000000 -j 5
- - ''
- - SSC SSC2 phy -S -o 1 -m b
- - R SSC2 C +SPHY:protocol
- - SSC SSC2 sta -S -n <ap_channel>
- - R SSC2 P <ap_ssid>
- - SSC SSC2 phy -S -o 1 -m g
- - R SSC2 C +SPHY:protocol
- - SSC SSC2 sta -S -n <ap_channel>
- - R SSC2 P <ap_ssid>
- - SSC SSC2 phy -S -o 1 -m n -b 20
- - R SSC2 C +SPHY:protocol
- - SSC SSC2 sta -S -n <ap_channel>
- - R SSC2 P <ap_ssid>
- - SSC SSC2 phy -S -o 1 -m n -b 40
- - R SSC2 C +SPHY:protocol
- - SSC SSC2 sta -S -n <ap_channel>
- - R SSC2 P <ap_ssid>
execution time: 0.0
expected result: 3. target 2 able to scan AP
initial condition: T2_2
level: Integration
module: WIFI MAC
steps: |-
1. target 1 connect to AP
2. target 1 start sending UDP packets
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_4
test point 1: interaction
test point 2: Scan interact with other WiFi operation
version: v1 (2015-8-15)
- CI ready: 'No'
ID: WIFI_SCAN_0303
SDK: ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 sta -C -s <ap_ssid> -p <ap_password>
- - R SSC1 C +JAP:OK
- - SSC SSC1 sta -S
- - P SSC1 C +SCANDONE
- P SSC1 C +JAP:CONNECTED
- - SSC SSC1 sta -D
- - R SSC1 C +QAP:OK
- - SSC SSC1 sta -S
- - ''
- - SSC SSC1 sta -C -s <ap_ssid> -p <ap_password>
- - P SSC1 C +SCANDONE
- P SSC1 C +JAP:CONNECTED
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 Scan
summary: scan during JAP
test environment: SSC_T1_5
test point 1: interaction
test point 2: Scan interact with other WiFi operation
version: v1 (2015-8-15)
- CI ready: 'Yes'
ID: WIFI_SCAN_0304
SDK: ESP32_IDF
Test App: SSC
allow fail: ''
auto test: 'Yes'
category: Function
cmd set:
- ''
- - SSC SSC1 ap -S -s <target_ssid> -p <target_password> -t <target_auth_enum>
- - R SSC1 C +SAP:OK
- - SSC SSC1 sta -D
- - R SSC1 C OK
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password>
- - R SSC2 C +JAP:OK
- - SSC SSC1 sta -S
- - P SSC1 C +SCANDONE
- P SSC2 C +JAP:CONNECTED
- - SSC SSC2 sta -D
- - R SSC2 C +QAP:OK
- - SSC SSC1 sta -S
- - ''
- - SSC SSC2 sta -C -s <target_ssid> -p <target_password>
- - P SSC1 C +SCANDONE
- P SSC2 C +JAP:CONNECTED
execution time: 0.0
expected result: |-
2. scan succeed, JAP succeed
5. JAP succeed, scan succeed
initial condition: T2_2
level: Integration
module: WIFI MAC
steps: |-
1. target 2 STA join target 1 SoftAP
2. target 1 STA scan before target 2 JAP succeed
3. target 2 STA QAP
4. target 1 STA scan
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_5
test point 1: interaction
test point 2: Scan interact with other WiFi operation
version: v1 (2015-8-15)
- CI ready: 'Yes'
ID: WIFI_SCAN_5101
SDK: |-
8266_NonOS
8266_RTOS
ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stress
cmd set:
- WiFiStress/WifiSCANTime
- - test_time = 300
- - ''
- - active_scan_max_time = 120
- - ''
- - active_scan_min_time = 20
- - ''
- - passive_scan_max_time = 100
- - ''
- - scan_mode_list = ["active_scan","passive_scan"]
- - ''
execution time: 5.0
expected result: "1. succeed\n3. scan time less than 1.15 test time "
initial condition: None
level: Integration
module: WIFI MAC
steps: |-
1. 1 target set to sta mode
2. set scan mode
3. start scan ap and check scan time
sub module: WIFI Scan
summary: test differnt scan mode scan time
test environment: SSC_T1_1
test point 1: stress
test point 2: Sta active/passive scan stress test
version: v2 (2017-05-10)
- CI ready: 'No'
ID: WIFI_SCAN_5201
SDK: ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stress
cmd set:
- WiFiStress/WifiScanOptimize
- - test_times = 10
- - ''
- - test_mode = "conn_by_bssid"
- - ''
execution time: 0.2
expected result: |-
1. all routers configure correctly
3. connect success
initial condition: None
level: Integration
module: WIFI MAC
steps: |-
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
test point 1: function + stress
test point 2: connect ap by bssid
version: v2 (2016-11-15)
- CI ready: 'No'
ID: WIFI_SCAN_5202
SDK: ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stress
cmd set:
- WiFiStress/WifiScanOptimize
- - test_times = 10
- - ''
- - test_mode = "conn_max_rssi_ap"
- - ''
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. 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
test point 1: function + stress
test point 2: connect max rssi ap
version: v2 (2016-11-15)
- CI ready: 'No'
ID: WIFI_SCAN_5203
SDK: ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stress
cmd set:
- WiFiStress/WifiScanOptimize
- - test_times = 10
- - ''
- - test_mode = "conn_most_security_ap"
- - ''
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. 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
test point 1: function + stress
test point 2: connect most security ap
version: v2 (2016-11-15)
- CI ready: 'No'
ID: WIFI_SCAN_5204
SDK: ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stress
cmd set:
- WiFiStress/WifiScanOptimize
- - test_times = 10
- - ''
- - test_mode = "conn_setting_ap"
- - ''
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. 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
test point 1: function + stress
test point 2: connect setting ap
version: v2 (2016-11-15)
- CI ready: 'No'
ID: WIFI_SCAN_5205
SDK: ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stress
cmd set:
- WiFiStress/WifiScanOptimize
- - test_times = 10
- - ''
- - test_mode = "reconn_same_ssid_ap"
- - ''
- - apc_num_list = [1,3]
- - ''
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. 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
test point 1: function + stress
test point 2: reconnect same ssid ap
version: v2 (2016-11-15)
- CI ready: 'No'
ID: WIFI_SCAN_5206
SDK: ESP32_IDF
Test App: SSC
auto test: 'Yes'
category: Stress
cmd set:
- WiFiStress/WifiScanOptimize
- - test_times = 10
- - ''
- - test_mode = "quick_conn_ap"
- - ''
- - rssi_threshold = 60
- - ''
- - 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. 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
test point 1: function + stress
test point 2: quick connect ap
version: v2 (2016-11-15)
- CI ready: 'No'
ID: WIFI_SCAN_5207
SDK: ESP32_IDF
Test App: SSC
auto test: 'No'
category: Stress
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. 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
test point 1: function
test point 2: connect open security mode ap
version: v2 (2016-11-15)

View File

@ -1,386 +0,0 @@
.TEST_ENV: &TEST_ENV
PC OS: ''
Special: N
test script: EnvBase
test environment:
- tag: SSC_T1_1
<<: *TEST_ENV
Target Count: 1
test environment detail: |-
PC has 2 wired NIC connected to AP.
PC has 1 WiFi NIC.
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 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 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
Target Count: 1
test environment detail: |-
PC has 1 wired NIC connected to AP.
1 8089 tablet able to run iperf test placed near SSC1.
1 SSC DUT connect with PC by UART.
- tag: SSC_T1_ADC
<<: *TEST_ENV
Special: Y
Target Count: 1
test environment detail: |-
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 DUT connect with PC by UART.
- tag: SSC_T1_AMSDU
<<: *TEST_ENV
Special: Y
Target Count: 1
test environment detail: |-
1 SSC DUT connect PC by UART.
PC 无线网卡和 SSC DUT 均连接到天猫魔盒AP.
- tag: SSC_T1_APC
<<: *TEST_ENV
Special: Y
Target Count: 1
test environment detail: |-
PC has 1 wired NIC connected to AP.
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 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 DUT
connect with PC by UART."
- tag: SSC_T1_IOT1
<<: *TEST_ENV
Special: Y
Target Count: 1
test environment detail: |-
PC has 1 WiFi NIC.
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 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.
- tag: SSC_T1_SCANSPECIFIED
<<: *TEST_ENV
Special: N
Target Count: 1
test environment detail: 1 SSC DUT connect with PC by UART. All APs power on.
- tag: SSC_T1_ShieldBox
<<: *TEST_ENV
Special: Y
Target Count: 1
test environment detail: |-
refer to figure.
All APs and APC should be set to the same IP subnet.
PC wired NIC should set static IP address within the same subnet with AP.
Must use onboard wired NIC.
- tag: SSC_T1_Sleep1
<<: *TEST_ENV
Special: Y
Target Count: 1
test environment detail: |-
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.
SSC1's XPD connect with RSTB.
- tag: SSC_T1_Sleep2
<<: *TEST_ENV
Special: Y
Target Count: 1
test environment detail: |-
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.
- tag: SSC_T1_Sleep3
<<: *TEST_ENV
Special: Y
Target Count: 1
test environment detail: |-
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
<<: *TEST_ENV
Target Count: 1
test environment detail: |-
PC has 1 wired NIC connected to AP. PC has 1 WiFi NIC.
1 SSC DUT connect with PC by UART.
- tag: SSC_T1_TempBox
<<: *TEST_ENV
Special: Y
Target Count: 1
test environment detail: |-
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 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 DUT connect with PC by UART.
One WEP share key AP placed near SSC1.
- tag: SSC_T2_1
<<: *TEST_ENV
Target Count: 2
test environment detail: |-
PC has 1 wired NIC connected to AP.
PC has 1 WiFi NIC.
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 DUT connect with PC by UART.
- tag: SSC_T2_PhyMode
<<: *TEST_ENV
PC OS: 'linux'
Target Count: 2
test environment detail: |-
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 DUTs.
- tag: SSC_T2_ShieldBox
<<: *TEST_ENV
Special: Y
Target Count: 2
test environment detail: |-
2 SSC DUT connect with PC by UART.
Put them to Shield box.
- tag: SSC_T2_ShieldBox2
<<: *TEST_ENV
Special: Y
Target Count: 1
test environment detail: |
refer to figure.
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
PC OS: 'linux'
Special: N
Target Count: 2
test environment detail: |-
PC has 1 wired NIC connected to AP.
PC has 1 WiFi NIC.
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 DUT connect with PC by UART. Put 1 DUT board to temperature box.
- tag: SSC_T3_1
<<: *TEST_ENV
Special: N
Target Count: 1
test environment detail: |-
PC has 1 wired NIC connected to AP.
PC has 1 WiFi NIC.
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 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 DUTs.
- tag: SSC_T5_1
<<: *TEST_ENV
Target Count: 5
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 DUTs connect with PC by UART.
some Android smart phone are placed near SSC DUTs.
- tag: SSC_T6_1
<<: *TEST_ENV
Special: Y
Target Count: 6
test environment detail: |-
PC has 1 wired NIC connected to AP.
PC has 1 WiFi NIC.
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_T12_MESH1
<<: *TEST_ENV
Special: Y
Target Count: 50
test environment detail: |-
PC has 1 wired NIC connected to AP.
PC has 1 WiFi NIC.
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.

View File

@ -35,7 +35,7 @@ def target_branch_candidates(proj_name):
pass
# branch name read from IDF
try:
git_describe = subprocess.check_output(["git", "describe", "--tags", "HEAD"])
git_describe = subprocess.check_output(["git", "describe", "HEAD"])
match = IDF_GIT_DESCRIBE_PATTERN.search(git_describe.decode())
if match:
major_revision = match.group(1)
@ -68,7 +68,7 @@ if __name__ == "__main__":
for candidate in candidate_branches:
try:
subprocess.check_call(["git", "checkout", candidate])
subprocess.check_call(["git", "checkout", "-f", candidate], stdout=subprocess.PIPE, stderr=subprocess.PIPE) # not print the stdout nor stderr
print("CI using ref {} for project {}".format(candidate, args.project))
break
except subprocess.CalledProcessError:

View File

@ -20,6 +20,7 @@ tools/ci/get-full-sources.sh
tools/ci/mirror-submodule-update.sh
tools/ci/mirror-synchronize.sh
tools/ci/push_to_github.sh
tools/ci/retry_failed.sh
tools/ci/test_build_system.sh
tools/ci/test_configure_ci_environment.sh
tools/esp_app_trace/apptrace_proc.py

45
tools/ci/retry_failed.sh Executable file
View File

@ -0,0 +1,45 @@
#!/usr/bin/env bash
set -euo pipefail
#
# Retries a command RETRY_ATTEMPTS times in case of failure
#
# Inspired by https://stackoverflow.com/a/8351489
#
max_attempts=${RETRY_ATTEMPTS-3}
RETRY_TIMEWAIT=${RETRY_TIMEWAIT-1}
attempt=1
exitCode=0
whole_start=$(date +%s)
attempt_start=whole_start
while true; do
if "$@" ; then
exitCode=0
break
else
exitCode=$?
fi
if (( $attempt >= $max_attempts )) ; then
break
fi
echo "Failed! ("$@") Spent time $(( $(date '+%s') - ${attempt_start} )) sec. Retrying in ${RETRY_TIMEWAIT}..." 1>&2
sleep $RETRY_TIMEWAIT
attempt=$(( attempt + 1 ))
RETRY_TIMEWAIT=$(( RETRY_TIMEWAIT * 2 ))
attempt_start=$(date +%s)
done
if [[ $exitCode != 0 ]] ; then
echo -n "Totally failed! ("$@")" 1>&2
else
echo -n "Done ("$@")" 1>&2
fi
echo " Spent time $(( $(date '+%s') - ${whole_start} )) sec in total" 1>&2
exit $exitCode

View File

@ -1,11 +1,7 @@
#! /bin/bash
# Regexp for matching job names which are incompatible with Python 3
py3_incomp='assign_test|UT|IT'
if [ -z ${PYTHON_VER+x} ] || [[ $CI_JOB_NAME =~ $py3_incomp ]]; then
# Use this version of the Python interpreter if it was not defined before or
# the given job is not compatible with Python 3
if [ -z ${PYTHON_VER+x} ]; then
# Use this version of the Python interpreter if it was not defined before
PYTHON_VER=2.7.15
fi