# TEE Test

## Introduce

This is the test suit for the functional and compatible test of TEE.

TEE test suit is based on Open Harmony hcpptest framework, which can refer to the XTS subsystem.

## Important Folders

|  Folder   |  Introduce  |
|  ----  |  ----  |
| driver  | driver related code |
| ca  | REE related test code，which is the testcase definition. |
| ta  | TEE related test code |
| utils  | test AW and public code |

## Build
### Build CA

    # build with the system:
    hb build --gn-args build_xts=true

    # For rk3568：
    First, copy the tee directory from the ca directory to the test/xts/acts directory, then add the configuration tee directory to the test/xts/acts/test_packages.gni file, and execute the  following compile command
    cd test/xts/acts
    /build.sh product_name=rk3568 system_size=standard target_subsystem=tee
    The compiled CA in "out/rk3568/suites/acts/acts/testcases"。
### Build TA


## Test Execution
Note: The absolute path for running the CA during the test must be the same as the absolute path for running the CA specified by AddCaller_CA func in the test TA. In this example, the CA named tee_test_client_api_vendor in the TA is used as an example to describe the test command. You can specify another name in the actual test.

Place the test TA (sec file) in the same level directory as the test CA, and both can be placed in the/vendor/bin/directory.

### TEE SDK compatibility test
1. Execute all test cases.
Enter the command line window of the tested system, Enter "/vendor/bin/tee_test_client_api_vendor"

2. Execute some test cases.
For details, see the commands provided by the hcpptest framework.
Supports the use of wildcard characters "*", for example /vendor/bin/tee_test_client_api_vendor --gtest_filter=*TeeBasicTestFram.InvokeCommand*

3. Current exist tee xts test CA list:
/vendor/bin/tee_test_client_api_vendor
/system/bin/tee_test_client_api_system
/vendor/bin/tee_test_tcf_api
/vendor/bin/tee_test_time_api
/vendor/bin/tee_test_arithmetic_api
/vendor/bin/tee_test_trusted_storage_api
/vendor/bin/tee_test_crypto_api
/vendor/bin/tee_test_device_api

## Reference
    - xts_acts

# TEE Test介绍

## 简介

此目录下为TEE的测试套件代码，用于功能测试和兼容性测试。
TEE 测试套件REE侧是基于Open Harmony的hcpptest编写。测试框架可参考XTS子系统简介。

## 重要目录说明

|  目录   |  说明  |
|  ----  |  ----  |
| driver  | 驱动相关代码 |
| ca  | REE侧相关测试代码，即测试用例定义部分 |
| ta  | TEE侧相关测试代码 |
| utils  | 测试公共代码 |

## 如何编译
### CA编译
    # 跟随系统编译:
    hb build --gn-args build_xts=true

    # 对于rk3568系统：
    先将ca目录下的tee目录拷贝到test/xts/acts目录下，然后在test/xts/acts/test_packages.gni文件中添加配置tee目录，再执行下面编译命令
    cd test/xts/acts
    /build.sh product_name=rk3568 system_size=standard target_subsystem=tee
    编译出的CA在out/rk3568/suites/acts/acts/testcases目录下。

### TA编译
    将测试TA源码放到SDK目录中，参考demo TA的编译，源码和配置文件使用待编译的TA即可。

## 测试执行
注意，测试时CA运行的路径要与测试TA中AddCaller_CA指定的CA运行路径保持一致，本例以TA中CA名称为tee_test_client_api_vendor为例来介绍测试命令。
测试TA（sec文件）放到与测试CA同级目录下，可以均放在/vendor/bin/目录下。

### TEE sdk兼容性测试

1. 执行全部用例
   进入被测试系统命令行窗口，输入："/vendor/bin/tee_test_client_api_vendor"

2. 执行部分用例
   参考hcpptest框架提供的命令。支持使用通配符*，例如 /vendor/bin/tee_test_client_api_vendor --gtest_filter=*TeeBasicTestFram.InvokeCommand*

3. 当前已有的tee xts 测试CA 列表:
/vendor/bin/tee_test_client_api_vendor
/system/bin/tee_test_client_api_system
/vendor/bin/tee_test_tcf_api
/vendor/bin/tee_test_time_api
/vendor/bin/tee_test_arithmetic_api
/vendor/bin/tee_test_trusted_storage_api
/vendor/bin/tee_test_crypto_api
/vendor/bin/tee_test_device_api
## 参考仓
    - xts_acts