当前仓库属于关闭状态,部分功能使用受限,详情请查阅 仓库状态说明
6 Star 6 Fork 11

OpenHarmony / test_developertest
关闭

加入 Gitee
与超过 1200万 开发者一起发现、参与优秀开源项目,私有仓库也完全免费 :)
免费加入
克隆/下载
贡献代码
同步代码
取消
提示: 由于 Git 不支持空文件夾,创建文件夹后会生成空的 .keep 文件
Loading...
README
Apache-2.0

开发自测试执行框架

OpenHarmony为开发者提供了一套全面的开发自测试框架OHA-developertest,开发者可根据测试需求开发相关测试用例,开发阶段提前发现缺陷,大幅提高代码质量。

本文从基础环境构建,用例开发,编译以及执行等方面介绍OpenHarmony开发自测试执行框架如何运行和使用。

基础环境构建

开发自测试框架依赖于python运行环境,python版本为3.8.X,在使用测试框架之前可参阅以下方式进行配置。

开发自测试框架依赖于测试调度框架test_xdevice,在使用时两个框架放在同级目录,命名为xdevice

开发自测试框架目录简介

以下是开发自测试框架的目录层级架构,在使用开发自测试框架过程中可在相应目录查找对应组件。

test  # 测试子系统
├── developertest  # 开发者自测试框架
│   ├── aw  # 测试框架的静态库
│   ├── config  # 测试框架配置
│   │   │ ...
│   │   └── user_config.xml  # 用户使用配置
│   ├── examples  # 测试用例示例
│   ├── src  # 测试框架源码
│   ├── third_party  # 测试框架依赖第三方组件适配
│   ├── reports  # 测试结果报告
│   ├── BUILD.gn  # 测试框架编译入口
│   ├── start.bat  # 开发者测试入口(Windows)
│   └── start.sh  # 开发者测试入口(Linux)
└── xdevice  # 测试框架依赖组件

功能特性

测试用例

测试用例目录规划

使用测试框架过程中,可根据以下层级关系规划测试用例目录。

subsystem  # 子系统
├── partA  # 部件A
│   ├── moduleA  # 模块A
│   │   ├── include       
│   │   ├── src  # 业务代码
│   │   └── test  # 测试目录
│   │       ├── unittest  # 单元测试
│   │       │   ├── common  # 公共用例
│   │       │   │   ├── BUILD.gn  # 测试用例编译配置
│   │       │   │   └── testA_test.cpp  # 单元测试用例源码
│   │       │   ├── phone  # 手机形态用例
│   │       │   ├── ivi  # 车机形态用例
│   │       │   └── liteos-a  # ipcamera使用liteos内核的用例
│   │       ├── moduletest  # 模块测试
│   │       ...
│   │            
│   ├── moduleB  # 模块B   
│   ├── test               
│   │   └── resource  # 依赖资源    
│   │       ├── moduleA  # 模块A
│   │       │   ├── ohos_test.xml  # 资源配置文件
│   │       ... └── 1.txt  # 资源   
│   │            
│   ├── ohos_build  # 编译入口配置  
│   ...

...

注意: 测试用例根据不同设备形态差异分为通用用例和非通用用例,建议将通用用例存放在common目录下,非通用用例存放在相应设备形态目录下。

测试用例编写

本测试框架支持多种类型测试,针对不同测试类型提供了不同的用例编写模板以供参考。

TDD测试(C++)

  • 用例源文件命名规范

    测试用例源文件名称和测试套内容保持一致,文件命名采用全小写+下划线方式命名,以test结尾,具体格式为:[功能]_[子功能]_test,子功能支持向下细分。 示例:

    calculator_sub_test.cpp
  • 用例示例

    /*
     * Copyright (c) 2021 XXXX Device Co., Ltd.
     * Licensed under the Apache License, Version 2.0 (the "License");
     * you may not use this file except in compliance with the License.
     * You may obtain a copy of the License at
     *
     *     http://www.apache.org/licenses/LICENSE-2.0
     *
     * Unless required by applicable law or agreed to in writing, software
     * distributed under the License is distributed on an "AS IS" BASIS,
     * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
     * See the License for the specific language governing permissions and
     * limitations under the License.
     */
    
    #include "calculator.h"
    #include <gtest/gtest.h>
    
    using namespace testing::ext;
    
    class CalculatorSubTest : public testing::Test {
    public:
        static void SetUpTestCase(void);
        static void TearDownTestCase(void);
        void SetUp();
        void TearDown();
    };
    
    void CalculatorSubTest::SetUpTestCase(void)
    {
        // input testsuit setup step,setup invoked before all testcases
    }
    
    void CalculatorSubTest::TearDownTestCase(void)
    {
        // input testsuit teardown step,teardown invoked after all testcases
    }
    
    void CalculatorSubTest::SetUp(void)
    {
        // input testcase setup step,setup invoked before each testcases
    }
    
    void CalculatorSubTest::TearDown(void)
    {
        // input testcase teardown step,teardown invoked after each testcases
    }
    
    /**
     * @tc.name: integer_sub_001
     * @tc.desc: Verify the sub function.
     * @tc.type: FUNC
     * @tc.require: issueNumber
     */
    HWTEST_F(CalculatorSubTest, integer_sub_001, TestSize.Level1)
    {
        // step 1:调用函数获取结果
        int actual = Sub(4,0);
    
        // Step 2:使用断言比较预期与实际结果
        EXPECT_EQ(4, actual);
    }

    详细内容介绍:

    1. 添加测试用例文件头注释信息

      /*
       * Copyright (c) 2021 XXXX Device Co., Ltd.
       * Licensed under the Apache License, Version 2.0 (the "License");
       * you may not use this file except in compliance with the License.
       * You may obtain a copy of the License at
       *
       *     http://www.apache.org/licenses/LICENSE-2.0
       *
       * Unless required by applicable law or agreed to in writing, software
       * distributed under the License is distributed on an "AS IS" BASIS,
       * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
       * See the License for the specific language governing permissions and
       * limitations under the License.
       */
    2. 引用测试框架头文件和命名空间

      #include <gtest/gtest.h>
      
      using namespace testing::ext;
    3. 添加被测试类的头文件

      #include "calculator.h"
    4. 定义测试套(测试类)

      class CalculatorSubTest : public testing::Test {
      public:
          static void SetUpTestCase(void);
          static void TearDownTestCase(void);
          void SetUp();
          void TearDown();
      };
      
      void CalculatorSubTest::SetUpTestCase(void)
      {
          // input testsuit setup step,setup invoked before all testcases
      }
      
      void CalculatorSubTest::TearDownTestCase(void)
      {
          // input testsuit teardown step,teardown invoked after all testcases
      }
      
      void CalculatorSubTest::SetUp(void)
      {
          // input testcase setup step,setup invoked before each testcases
      }
      
      void CalculatorSubTest::TearDown(void)
      {
          // input testcase teardown step,teardown invoked after each testcases
      }

      注意: 在定义测试套时,测试套名称应与编译目标保持一致,采用大驼峰风格。

    5. 测试用例实现,包含用例注释和逻辑实现

      /**
       * @tc.name: integer_sub_001
       * @tc.desc: Verify the sub function.
       * @tc.type: FUNC
       * @tc.require: issueNumber
       */
      HWTEST_F(CalculatorSubTest, integer_sub_001, TestSize.Level1)
      {
          //step 1:调用函数获取结果
          int actual = Sub(4,0);
      
          //Step 2:使用断言比较预期与实际结果
          EXPECT_EQ(4, actual);
      }

      注意: @tc.require: 格式必须以AR/SR或issue开头: 如:issueI56WJ7

      在编写用例时,我们提供了三种用例模板供您选择。

      类型 描述
      HWTEST(A,B,C) 用例执行不依赖Setup&Teardown时,可选取
      HWTEST_F(A,B,C) 用例执行(不含参数)依赖于Setup&Teardown时,可选取
      HWTEST_P(A,B,C) 用例执行(含参数)依赖于Set&Teardown时,可选取

      其中,参数A,B,C的含义如下:

    • 参数A为测试套名。

    • 参数B为测试用例名,其命名必须遵循[功能点]_[编号]的格式,编号为3位数字,从001开始。

    • 参数C为测试用例等级,具体分为门禁level0 以及非门禁level1-level4共五个等级,其中非门禁level1-level4等级的具体选取规则为:测试用例功能越重要,level等级越低。

      注意:

    • 测试用例的预期结果必须有对应的断言。

    • 测试用例必须填写用例等级。

    • 测试体建议按照模板分步实现。

    • 用例描述信息按照标准格式@tc.xxx value书写,注释信息必须包含用例名称,用例描述,用例类型,需求编号四项。其中用例测试类型@tc.type参数的选取,可参考下表。

      测试类型名称 类型编码
      功能测试 FUNC
      性能测试 PERF
      可靠性测试 RELI
      安全测试 SECU
      模糊测试 FUZZ

TDD测试(JS)

  • 用例源文件命名规范

    测试用例原文件名称采用大驼峰风格,以TEST结尾,具体格式为:[功能][子功能]TEST,子功能支持向下细分。 示例:

    AppInfoTest.js
  • 用例示例

    /*
     * Copyright (C) 2021 XXXX Device Co., Ltd.
     * Licensed under the Apache License, Version 2.0 (the "License");
     * you may not use this file except in compliance with the License.
     * You may obtain a copy of the License at
     *
     *     http://www.apache.org/licenses/LICENSE-2.0
     *
     * Unless required by applicable law or agreed to in writing, software
     * distributed under the License is distributed on an "AS IS" BASIS,
     * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
     * See the License for the specific language governing permissions and
     * limitations under the License.
     */
    import app from '@system.app'
    
    import {describe, beforeAll, beforeEach, afterEach, afterAll, it, expect} from 'deccjsunit/index'
    
    describe("AppInfoTest", function () {
        beforeAll(function() {
            // input testsuit setup step,setup invoked before all testcases
             console.info('beforeAll caled')
        })
        
        afterAll(function() {
             // input testsuit teardown step,teardown invoked after all testcases
             console.info('afterAll caled')
        })
        
        beforeEach(function() {
            // input testcase setup step,setup invoked before each testcases
             console.info('beforeEach caled')
        })
        
        afterEach(function() {
            // input testcase teardown step,teardown invoked after each testcases
             console.info('afterEach caled')
        })
    
        /*
         * @tc.name:appInfoTest001
         * @tc.desc:verify app info is not null
         * @tc.type: FUNC
         * @tc.require: issueNumber
         */
        it("appInfoTest001", 0, function () {
            //step 1:调用函数获取结果
            var info = app.getInfo()
    
            //Step 2:使用断言比较预期与实际结果
            expect(info != null).assertEqual(true)
        })
    })

    详细内容介绍:

    1. 添加测试用例文件头注释信息
      /*
       * Copyright (C) 2021 XXXX Device Co., Ltd.
       * Licensed under the Apache License, Version 2.0 (the "License");
       * you may not use this file except in compliance with the License.
       * You may obtain a copy of the License at
       *
       *     http://www.apache.org/licenses/LICENSE-2.0
       *
       * Unless required by applicable law or agreed to in writing, software
       * distributed under the License is distributed on an "AS IS" BASIS,
       * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
       * See the License for the specific language governing permissions and
       * limitations under the License.
       */
    2. 导入被测api和jsunit测试库
      import app from '@system.app'
      
      import {describe, beforeAll, beforeEach, afterEach, afterAll, it, expect} from 'deccjsunit/index'
    3. 定义测试套(测试类)
      describe("AppInfoTest", function () {
          beforeAll(function() {
              // input testsuit setup step,setup invoked before all testcases
               console.info('beforeAll caled')
          })
          
          afterAll(function() {
               // input testsuit teardown step,teardown invoked after all testcases
               console.info('afterAll caled')
          })
          
          beforeEach(function() {
              // input testcase setup step,setup invoked before each testcases
               console.info('beforeEach caled')
          })
          
          afterEach(function() {
              // input testcase teardown step,teardown invoked after each testcases
               console.info('afterEach caled')
          })
    4. 测试用例实现
      /*
       * @tc.name:appInfoTest001
       * @tc.desc:verify app info is not null
       * @tc.type: FUNC
       * @tc.require: issueNumber
       */
       it("appInfoTest001", 0, function () {
          //step 1:调用函数获取结果
          var info = app.getInfo()
      
          //Step 2:使用断言比较预期与实际结果
          expect(info != null).assertEqual(true)
       })

      注意: @tc.require: 格式必须以AR/SR或issue开头: 如:issueI56WJ7

Fuzz测试

Fuzz用例编写规范

Benchmark测试

Benchmark用例编写规范

测试用例编译文件编写

根据测试用例目录规划,当执行某一用例时,测试框架会根据编译文件逐层查找,最终找到所需用例进行编译。下面通过不同示例来讲解gn文件如何编写。

TDD测试

针对不同语言,下面提供不同的编译模板以供参考。

  • C++用例编译配置示例

    # Copyright (c) 2021 XXXX Device Co., Ltd.
    
    import("//build/test.gni")
    
    module_output_path = "developertest/calculator"
    
    config("module_private_config") {
      visibility = [ ":*" ]
    
      include_dirs = [ "../../../include" ]
    }
    
    ohos_unittest("CalculatorSubTest") {
      module_out_path = module_output_path
    
      sources = [
        "../../../include/calculator.h",
        "../../../src/calculator.cpp",
      ]
    
      sources += [ "calculator_sub_test.cpp" ]
    
      configs = [ ":module_private_config" ]
    
      deps = [ "//third_party/googletest:gtest_main" ]
    }
    
    group("unittest") {
      testonly = true
      deps = [":CalculatorSubTest"]
    }

    详细内容如下:

    1. 添加文件头注释信息

      # Copyright (c) 2021 XXXX Device Co., Ltd.
    2. 导入编译模板文件

      import("//build/test.gni")
    3. 指定文件输出路径

      module_output_path = "developertest/calculator"

      说明: 此处输出路径为部件/模块名。

    4. 配置依赖包含目录

      config("module_private_config") {
        visibility = [ ":*" ]
         
        include_dirs = [ "../../../include" ]
      }

      说明: 一般在此处对相关配置进行设置,在测试用例编译脚本中可直接引用。

    5. 指定测试用例编译目标输出的文件名称

      ohos_unittest("CalculatorSubTest") {
      }
    6. 编写具体的测试用例编译脚本(添加需要参与编译的源文件、配置和依赖)

      ohos_unittest("CalculatorSubTest") {
        module_out_path = module_output_path
        sources = [
          "../../../include/calculator.h",
          "../../../src/calculator.cpp",
          "../../../test/calculator_sub_test.cpp"
        ]
        sources += [ "calculator_sub_test.cpp" ]
        configs = [ ":module_private_config" ]
        deps = [ "//third_party/googletest:gtest_main" ]
      }

      说明:根据测试类型的不同,在具体编写过程中可选择不同的测试类型:

      • ohos_unittest:单元测试
      • ohos_moduletest:模块测试
      • ohos_systemtest:系统测试
      • ohos_performancetest:性能测试
      • ohos_securitytest:安全测试
      • ohos_reliabilitytest:可靠性测试
      • ohos_distributedtest:分布式测试
    7. 对目标测试用例文件进行条件分组

      group("unittest") {
        testonly = true
        deps = [":CalculatorSubTest"]
      }

      说明: 进行条件分组的目的在于执行用例时可以选择性的执行某一种特定类型的用例。

  • JavaScript用例编译配置示例

    # Copyright (C) 2021 XXXX Device Co., Ltd.
    
    import("//build/test.gni")
    
    module_output_path = "developertest/app_info"
    
    ohos_js_unittest("GetAppInfoJsTest") {
      module_out_path = module_output_path
    
      hap_profile = "./config.json"
      certificate_profile = "//test/developertest/signature/openharmony_sx.p7b"
    }
    
    group("unittest") {
      testonly = true
      deps = [ ":GetAppInfoJsTest" ]
    }

    详细内容如下:

    1. 添加文件头注释信息

      # Copyright (C) 2021 XXXX Device Co., Ltd.
    2. 导入编译模板文件

      import("//build/test.gni")
    3. 指定文件输出路径

      module_output_path = "developertest/app_info"

      说明: 此处输出路径为部件/模块名。

    4. 指定测试用例编译目标输出的文件名称

      ohos_js_unittest("GetAppInfoJsTest") {
      }

      说明:

      • 使用模板ohos_js_unittest定义js测试套,注意与C++用例区分。
      • js测试套编译输出文件为hap类型,hap名为此处定义的测试套名,测试套名称必须以JsTest结尾。
    5. 指定hap包配置文件config.json和签名文件,两个配置为必选项

      ohos_js_unittest("GetAppInfoJsTest") {
        module_out_path = module_output_path
         
        hap_profile = "./config.json"
        certificate_profile = "//test/developertest/signature/openharmony_sx.p7b"
      }

      config.json为hap编译所需配置文件,需要开发者根据被测sdk版本配置“target”项,其余项可默认,具体如下所示:

      {
        "app": {
          "bundleName": "com.example.myapplication",
          "vendor": "example",
          "version": {
            "code": 1,
            "name": "1.0"
          },
          "apiVersion": {
                 "compatible": 4,
               "target": 5     // 根据被测sdk版本进行修改,此例为sdk5
          }
        },
        "deviceConfig": {},
        "module": {
          "package": "com.example.myapplication",
          "name": ".MyApplication",
          "deviceType": [
            "phone"
          ],
          "distro": {
            "deliveryWithInstall": true,
            "moduleName": "entry",
            "moduleType": "entry"
          },
          "abilities": [
            {
            "skills": [
                {
                  "entities": [
                    "entity.system.home"
                  ],
                  "actions": [
                    "action.system.home"
                  ]
                }
              ],
              "name": "com.example.myapplication.MainAbility",
              "icon": "$media:icon",
              "description": "$string:mainability_description",
              "label": "MyApplication",
              "type": "page",
              "launchType": "standard"
            }
          ],
          "js": [
            {
              "pages": [
                "pages/index/index"
              ],
              "name": "default",
                "window": {
                   "designWidth": 720,
                   "autoDesignWidth": false
                }
              }
            ]
          }
        }
    6. 对目标测试用例文件进行条件分组

      group("unittest") {
        testonly = true
        deps = [ ":GetAppInfoJsTest" ]
      }

      说明: 进行条件分组的目的在于执行用例时可以选择性的执行某一种特定类型的用例。

Fuzz测试

Fuzz编译文件编写规范

Benchmark测试

Benchmark编译文件编写规范

编译入口配置文件ohos.build

当完成用例编译配置文件编写后,需要进一步编写部件编译配置文件,以关联到具体的测试用例。

"partA": {
    "module_list": [
          
    ],
    "inner_list": [
          
    ],
    "system_kits": [
          
    ],
    "test_list": [ //配置模块calculator下的test
      "//system/subsystem/partA/calculator/test:unittest",  
      "//system/subsystem/partA/calculator/test:fuzztest",
      "//system/subsystem/partA/calculator/test:benchmarktest"
 }

说明: test_list中配置的是对应模块的测试用例。

测试用例资源配置

测试依赖资源主要包括测试用例在执行过程中需要的图片文件,视频文件、第三方库等对外的文件资源。

依赖资源文件配置步骤如下:

  1. 在部件的test目录下创建resource目录,在resource目录下创建对应的模块,在模块目录中存放该模块所需要的资源文件

  2. 在resource目录下对应的模块目录中创建一个ohos_test.xml文件,文件内容格式如下:

    <?xml version="1.0" encoding="UTF-8"?>
    <configuration ver="2.0">
        <target name="CalculatorSubTest">
            <preparer>
                <option name="push" value="test.jpg -> /data/test/resource" src="res"/>
                <option name="push" value="libc++.z.so -> /data/test/resource" src="out"/>
            </preparer>
        </target>
    </configuration>
  3. 在测试用例的编译配置文件中定义resource_config_file进行指引,用来指定对应的资源文件ohos_test.xml

    ohos_unittest("CalculatorSubTest") {
      resource_config_file = "//system/subsystem/partA/test/resource/calculator/ohos_test.xml"
    }

    说明:

    • target_name: 测试套的名称,定义在测试目录的BUILD.gn中。preparer: 表示该测试套执行前执行的动作。
    • src="res": 表示测试资源位于test目录下的resource目录下,src="out":表示位于out/release/$(部件)目录下。

测试用例执行

在执行测试用例之前,针对用例使用设备的不同,需要对相应配置进行修改,修改完成即可执行测试用例。

user_config.xml配置

<user_config>
  <build>
    <!-- 是否编译demo用例, 默认为false,如果需要编译demo可修改为true -->
    <example>false</example>
    <!-- 是否编译版本, 默认为false -->
    <version>false</version>
    <!-- 是否编译测试用例, 默认为true,若已完成编译,再执行用例之前可修改为false,防止重新编译 -->
    <testcase>true</testcase>
	<!-- 在编译测试用例的情况下,选择编译target_cpu是64位的还是32位的,默认为空(32bit)可以选择: arm64 -->
    <parameter>
       <target_cpu></target_cpu>
    </parameter>
  </build>
  <environment>
    <!-- 配置远程映射机器的IP及端口,以支持HDC连接的设备 -->
    <device type="usb-hdc">
      <ip></ip>
      <port></port>
      <sn></sn>
    </device>
    <!-- 配置设备的串口信息,以支持串口连接的设备 -->
    <device type="com" label="ipcamera">
      <serial>
        <com></com>
        <type>cmd</type>
        <baud_rate>115200</baud_rate>
        <data_bits>8</data_bits>
        <stop_bits>1</stop_bits>
        <timeout>1</timeout>
      </serial>
    </device>
  </environment>
  <!-- 配置测试用例路径,若测试用例未编译,即<testcase>标签属性为true时,此处默认不填写;若编译已完成,需在此处指定测试用例的实际路径 -->
  <test_cases>
    <dir></dir>
  </test_cases>
  <!-- 配置覆盖率编译路径 -->
  <coverage>
    <outpath></outpath>
  </coverage>
  <!-- NFS挂载信息配置,被测设备仅支持串口连接时配置,指定NFS的映射路径,host_dir为PC侧的NFS目录,board_dir为板侧创建的目录 -->
  <NFS>
    <host_dir></host_dir>
    <mnt_cmd></mnt_cmd>
    <board_dir></board_dir>
  </NFS>
</user_config>

说明: 在执行测试用例之前,若使用HDC连接设备,用例仅需配置设备IP和端口号即可,其余信息均默认不修改。

Windows环境执行

测试用例编译

由于Windows环境下无法实现用例编译,因此执行用例前需要在Linux环境下进行用例编译,用例编译命令:

./build.sh --product-name {product_name} --build-target make_test

说明:

  • product-name:指定编译产品名称。
  • build-target:指定所需编译用例,make_test表示指定全部用例,实际开发中可指定特定用例。

编译完成后,测试用例将自动保存在out/ohos-arm-release/packages/phone/tests目录下。

搭建执行环境
  1. 在Windows环境创建测试框架目录Test,并在此目录下创建testcase目录

  2. 从Linux环境拷贝测试框架developertest和xdevice到创建的Test目录下,拷贝编译好的测试用例到testcase目录下

    说明: 将测试框架及测试用例从Linux环境移植到Windows环境,以便后续执行。

  3. 修改user_config.xml

    <build>
      <!-- 由于测试用例已编译完成,此标签属性需改为false -->
      <testcase>false</testcase>
    </build>
    <test_cases>
      <!-- 由于已将测试用例拷贝到Windows环境下,测试用例输出路径发生改变,需要修改为拷贝后所存放的路径 -->
      <dir>D:\Test\testcase\tests</dir>
    </test_cases>

    说明: <testcase>标签表示是否需要编译用例;<dir>标签表示测试用例查找路径。

执行用例
  1. 启动测试框架

    start.bat
  2. 选择产品形态

    进入测试框架,系统会自动提示您选择产品形态,请根据实际的开发板进行选择。

    如需手动添加,请在config/framework_config.xml的<productform>标签内增加产品项。

  3. 执行测试用例

    当选择完产品形态,可参考如下指令执行测试用例。

    run -t UT -ts CalculatorSubTest -tc interger_sub_00l

    执行命令参数说明:

    -t [TESTTYPE]: 指定测试用例类型,有UT,MST,ST,PERF,FUZZ,BENCHMARK等。(必选参数)
    -tp [TESTPART]: 指定部件,可独立使用。
    -tm [TESTMODULE]: 指定模块,不可独立使用,需结合-tp指定上级部件使用。
    -ts [TESTSUITE]: 指定测试套,可独立使用。
    -tc [TESTCASE]: 指定测试用例,不可独立使用,需结合-ts指定上级测试套使用。
    -h : 帮助命令。

Linux环境执行

远程端口映射

为了在Linux远程服务器以及Linux虚拟机两种环境下执行测试用例,需要对端口进行远程映射,以实现与设备的数据通路连接。具体操作如下:

  1. HDC Server指令:

    hdc_std kill
    hdc_std -m -s 0.0.0.0:8710

    说明: IP和端口号为默认值。

  2. HDC Client指令:

    hdc_std -s xx.xx.xx.xx:8710 list targets

    说明: 此处IP填写设备侧IP地址。

执行用例
  1. 启动测试框架

    ./start.sh
  2. 选择产品形态

    进入测试框架,系统会自动提示您选择产品形态,请根据实际的开发板进行选择。

    如需手动添加,请在config/framework_config.xml的<productform>标签内增加产品项。

  3. 执行测试用例

    测试框架在执行用例时会根据指令找到所需用例,自动实现用例编译,执行过程,完成自动化测试。

    run -t UT -ts CalculatorSubTest -tc interger_sub_00l

    执行命令参数说明:

    -t [TESTTYPE]: 指定测试用例类型,有UT,MST,ST,PERF,FUZZ,BENCHMARK等。(必选参数)
    -tp [TESTPART]: 指定部件,可独立使用。
    -tm [TESTMODULE]: 指定模块,不可独立使用,需结合-tp指定上级部件使用。
    -ts [TESTSUITE]: 指定测试套,可独立使用。
    -tc [TESTCASE]: 指定测试用例,不可独立使用,需结合-ts指定上级测试套使用。
    -h : 帮助命令。

测试报告日志

当执行完测试指令,控制台会自动生成测试结果,若需要详细测试报告您可在相应的数据文档中进行查找。

测试结果

测试结果输出根路径如下:

test/developertest/reports/xxxx_xx_xx_xx_xx_xx

说明: 测试报告文件目录将自动生成。

该目录中包含以下几类结果:

类型 描述
result/ 测试用例格式化结果
log/plan_log_xxxx_xx_xx_xx_xx_xx.log 测试用例日志
summary_report.html 测试报告汇总
details_report.html 测试报告详情

测试框架日志

reports/platform_log_xxxx_xx_xx_xx_xx_xx.log

最新测试报告

reports/latest

涉及仓

test_xdevice

发布版本说明

发布版本号 发布功能说明
3.2.1.0 1、增加框架对接执行ACTS测试用例能力
2、增加ACTS多种颗粒度执行能力,如子系统、部件等
3.2.2.0 1、增加测试任务统计能力,最多统计10个任务
2、增加按照指定测试任务ID执行测试任务能力
3、增加复测上次任务失败用例能力
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS

简介

Development self-test framework | 开发者自测试框架 展开 收起
Apache-2.0
取消

发行版

暂无发行版

贡献者

全部

近期动态

加载更多
不能加载更多了
1
https://gitee.com/openharmony/test_developertest.git
git@gitee.com:openharmony/test_developertest.git
openharmony
test_developertest
test_developertest
master

搜索帮助

14c37bed 8189591 565d56ea 8189591