常见典型Test Cases

第21期2023年11月无线互联科技Wireless Internet Science and TechnologyNo.21November,2023作者简介:刘萌(1989 ),女,江苏徐州人,工程师,硕士;研究方向:自动化测试㊂Andriod IVI 系统稳定性测试方案研究与自动化测试工具设计及实现刘㊀萌(南京特殊教育师范学院,江苏南京210038)摘要:基于Andriod 的车载信息娱乐系统(In -Vehicle Infotainment ,IVI )功能日益复杂,产品安全性和稳定性问题也随之增多㊂为提高产品开发及测试环节工作效率,保障产品安全性和稳定性,文章对Andriod 的IVI 娱乐系统稳定性测试方案进行了深入研究,并基于Python 语言及Monkey ㊁UIAutomator2工具设计实现了两种自动化稳定性测试工具㊂自动化测试是软件测试未来的发展方向,这些自动化工具在项目实战中切实体现出人工测试无法取代的效果㊂关键词:稳定性测试;Python ;Monkey ;UIAutomator2中图分类号:TP311㊀㊀文献标志码:A0㊀引言㊀㊀随着互联网技术的飞速发展,Andriod 系统在市场终端应用中呈现迅速扩张的趋势,如今的车载娱乐终端也大多基于Android 操作系统,人机交互界面更美观,功能也日益复杂,这也导致了系统安全性和稳定性问题日益增多,在产品开发生命周期中不得不投入更多的时间和人力资源到测试环节中㊂车载娱乐终端产品一旦产生稳定性问题,不仅后期维护和纠正成本极高,还会给驾驶人员带来潜在的安全威胁㊂为解决上述问题,本文对Monkey 及UIAutomator2两种Andriod 自动化测试工具进行了研究,制定了随机和定制功能路径两种场景的自动化稳定性测试方案,并设计实现了基于Python 二次开发的Monkey 随机场景自动化测试工具和基于Python +Pytest +UIAutomator2的定制功能路径场景自动化测试工具㊂1㊀基于Monkey 的自动化随机测试㊀㊀Monkey 是Android 系统自带的一款基于命令行的自动化测试工具,主要用于测试Android 应用程序及系统的稳定性和鲁棒性㊂Monkey 通过向系统发送随机事件流来模拟用户操作㊂Monkey 简单易用,对于发现应用程序和系统的应用程序无响应(Application Not Response,ANR)㊁Crash 等异常具有显著的效果㊂1.1㊀Monkey 测试方案及工具框架设计1.1.1㊀运行方式设计㊀㊀Monkey 测试的运行可以分为离线和在线两种运行模式㊂在离线模式下,需要将Monkey 命令参数编写成shell 脚本推送到被测设备上,本地执行㊂这种模式对测试人员编程能力有一定要求,一旦测试步骤或参数需要更改,shell 脚本就需要修改,而且在测试过程中,脚本无法实时识别到异常,不会去实时捕获日志,只能在测试结束后人工分析Monkey 测试日志,找出问题及时间点,再去查找对应时间点的日志㊂如果问题出现的时间点较早,很可能日志已被覆盖掉,导致无法分析问题,像bugreport㊁dumpsys 等实时性要求极高的日志,在测试结束后再抓取基本已经失去时效㊂另外,离线模式下Monkey 测试本身产生的日志只能本地化存储,占据被测系统的存储空间,从而影响被测系统性能,干扰测试结果㊂在线测试模式在测试过程中需要保持PC 与被测设备的Android 调试桥(Android Debug Bridge,ADB)连通,Python 程序运行于PC 上,脚本实时翻译实时下发㊂本文设计的Monkey 测试工具采用在线运行方式㊂Monkey 命令通过Python 程序下发,所有Monkey 日志重定向到本地PC,避免占用被测设备的存储空间㊂在测试过程中,Python 程序还会另起线程实时读取并分析Monkey 日志,一旦识别到异常就立即抓取系统全日志㊂这种方法一方面节省了人工分析问题的时间,一方面确保了日志的实时性和完整性㊂1.1.2㊀测试模式设计㊀㊀Monke 测试工具提供了3种测试模式:单包㊁多包组合和系统级测试模式㊂单包模式只对一个应用程序进行测试,通常应用于产品开发前期㊁应用程序逐个上线的阶段㊂不同的功能模块用户的操作习惯不同㊂因此,该模式需要根据实际操作场景设置不同的事件百分比㊂多包组合模式同时针对多个应用进行并行测试,通常会选取用户使用频率最高的几个应用随机组合,测试过程必需涉及应用间的切换㊂系统级测试模式不限定被测应用范围,对所有应用程序和系统组件进行并行测试,实现全功能联动㊂该模式主要应用于产品开发后期阶段的验收㊂1.1.3㊀测试参数设计㊀㊀Monkey 测试参数主要分为3类:基本配置参数㊁事件类型参数和调试参数㊂本方案中Monkey 测试的目的有两种:项目早期阶段的问题发现测试(测试过程中忽略异常继续执行,以尽可能发现更多问题)和项目后期阶段的验收测试(测试过程中不忽略异常,出现异常即停止执行,并将验收结果判定为不通过)㊂不同测试阶段参数制定如下㊂(1)基本配置参数设计㊂级别(-v)设为最高-v -v -v,以输出尽可能详细的日志㊂随机种子值(-s)默认为0,每轮测试更换一个随机值,代表从不同的起点开始新一轮的测试㊂动作时间间隔(--throttle)在产品初期阶段设为1s,后期平台功能稳定后设定为300ms㊂在-p 参数后指定测试包可以实现上述3种测试模式㊂每轮测试的操作次数Count 参数由计划测试时长决定,计算公式为:Count =测试时长(ms)/--throttle㊂(2)事件类型参数设计㊂操作事件类型的百分比值根据不同被测模块的功能区别设定,百分比总和不超过100%㊂(3)调试参数设计㊂在问题发现测试阶段,将异常和超时参数设置为ignore;在验收测试阶段,不设置此类参数㊂Monkey 命令示例:adb shell monkey -p xxx -p xxx -s 0--throttle 300--pct-touch 40--pct-motion 20--pct-syskeys 10--pct-anyevent 10--pct-appswitch 10--pct-flip 5--pct-pinchzoom 5--ignore-crashes --ignore-timeouts --ignore-security-exceptions --ignore-native-carshes -v -v -v 50001.1.4㊀运行过程设计㊀㊀数据交换接口通常采用xml 格式来实现㊂本工具中用户配置接口即设计为一个xml 文件,其中包含了Monkey 测试参数㊁测试模式㊁被测系统的日志路径㊁检测门限值等参数㊂用户只需在此文件中填写参数值即可实现不同测试方案的更改㊂主程序在执行测试时会首先解析该xml 文件,读取用户设置的参数㊂执行流程如图1所示㊂图1㊀Monkey 测试工具执行流程1.2㊀工具运行效果分析㊀㊀在产品开发前期阶段,系统还不稳定,Monkey 工具发现了较多黑屏㊁冻屏㊁死机等重大问题㊂在产品开发中后期阶段,系统趋于稳定,Monkey 测试可以持续运行较长时间,更全面地发现了ANR㊁Crash 等异常㊂工具在日志抓取方面做到了实时㊁全面,能够满足开发分析的需求㊂2㊀基于Python+Pytest+UIAutomator2的自动化测试工具㊀㊀Python是全球最受欢迎的编程语言之一[1],拥有丰富的测试框架和工具[2],如Robot Framework㊁Pytest㊁Unitest等,而Pytest是最受欢迎和最具影响力的一个㊂UIAutomator2是Android UI自动化测试的开源工具之一,可以对任意应用程序的任意一个控件属性进行任意操作,开发者们推出的Python-UIAutomator2提供了Python接口,支持Python编程㊂Python-UIAutomator2的运行主要涉及两个部分: Python客户端和被测设备㊂UIAutomator2的运行环境需要进行以下配置:(1)被测设备端打开开发者选项,以ADB方式连接PC㊂在PC的CMD窗口执行adb devices,查看设备是否成功连接㊂(2)PC端安装Python3.x;安装UIAutomator2,在CMD窗口执行pip install UIAutomator2;安装WEditor㊂(3)在PC端CMD窗口执行Python-UIAutomator2init,安装被测设备端的HTTP RPC服务apk㊁atx-agent等㊂这些是UIAutomator2运行的必要工具㊂2.1㊀基于UIAutmator2的自动化测试方案设计㊀㊀Monkey工具对于智能车载娱乐系统而言,无法涉及与车上其他电子控制单元(Electronic Control Unit,ECU)的控制器局域网络(Controller Area Network,CAN)[3]通信车载协议测试㊂为解决这个问题,本文引入了定制功能路径的测试方案㊂定制功能路径测试具有以下优点:(1)测试步骤根据用户实际操作设计,测试场景更接近用户行为㊂(2)支持个性化定制,可以根据不同功能模块的特点,定制个性化的测试步骤㊂(3)支持压力测试:可以通过设置Pytest装饰器的参数值重复执行指定脚本,以检查系统的稳定性㊂定制功能路径测试的目的有2个:功能验证和性能验证㊂前者重点关注系统在执行一般用户操作(如点击㊁按键㊁滑动等)后的系统反应是否正确㊂后者主要通过反复执行某一类型的操作,如蓝牙㊁Wi-Fi的开关/断连㊁系统软重启㊁休眠/唤醒等,来检查系统功能和状态在重复压力或长期运行下是否稳定㊂这种测试对于发现系统内存泄漏以及稳健性相关的问题非常有效㊂定制功能路径测试分为常规操作类㊁Can信号交互类和性能测试等场景㊂常规操作类测试涵盖了用户常见的操作行为㊂Can信号交互类测试则关注系统在与其他ECU通信时系统状态及反馈是否正确㊂性能测试则是通过大量操作后,测量系统的关键性能指标,如冷启动/热启动时长和开机时序等,对系统进行全面的性能评估,以确保产品满足出厂及市场标准㊂定制功能路径测试具体场景设计如下:(1)单App全功能链路验证,主要用于验证单个应用程序的基本功能㊂(2)多App全功能链路交互验证,主要用于验证多个应用程序之间交互是否正常㊂(3)典型单场景操作,如开关反复开闭㊁休眠唤醒等,主要用于验证系统关键功能是否稳定㊂(4)性能测试,冷/热重启㊁休眠唤醒等场景重复执行百遍后,验证启动时序㊁统计平均开机时长㊂(5)场景复现,针对一些较难复现的bug开发特定的测试脚本尝试复现,出具复现概率报告或压力测试报告㊂2.2㊀自动化测试工具设计㊀㊀(1)界面元素获取工具㊂本文使用WEditor来定位元素,WEditor基于Python,能提供辅助编写脚本和调试代码的功能,可以通过浏览器轻松打开,简单易用㊂WEditor可方便获取到元素的Xpath属性(Xpath是元素的绝对唯一属性)㊂(2)测试脚本工程架构㊂基于UIAutmator2的自动化测试工具框架及整体运行流程设计如图2所示㊂①Main.py为测试引擎,主要完成测试报告的创建㊁测试套件配置参数的获取㊁各种路参数径的获取㊁测试命令下发等㊂②Config路径下存放test_cfg.py和xpath_cfg. py㊂前者用于存储测试套件的配置参数,如测试环境㊁用例㊁数据等㊂后者用于存储测试用例用到的参数,如XPath值㊁Can信号值等㊂③TestCases路径下存放所有测试脚本文件,每个功能模块对应一个.py文件,每个测试用例对应一个函数,用例运行策略由Pytest装饰器参数值指定㊂④util.py是一个集合了所有公共函数的Python 文件,如环境恢复㊁xml文件解析㊁用户操作㊁Can信号收发㊁Log抓取㊁系统状态检查等㊂⑤TestReports路径下存放测试报告,每轮测试都会创建一个新的网页版测试报告㊂测试报告中可以包含测试结果㊁执行时间㊁测试用例的通过或失败状态等信息㊂(3)Can信号收发工具使用开发㊂本文工具针对Pcan测试仪开发Python脚本,通过对PCanBasic.dll进行二次开发来实现㊂PCan Basic.dll的原生函数有:Initialize(初始化一个PCan 设备的PCan通道)㊁Uninitialize(取消初始化)㊁GetStatus(获取当前PCan通道的Bus状态)㊁Read(从消息接收队列中读取Can消息及其时间戳)㊁Write (发送Can消息)等函数,对上述源码进行Python二次封装,编写更易于测试人员使用㊁更符合项目需求的公共方法(如Send()㊁Receive()㊁Check())等,汇集到PCanBasic.py文件,测试用例中导入PCanBasic. py即可使用封装的函数㊂图2㊀UIAutomator2自动化测试工具框架及流程2.3㊀工具运行效果分析㊀㊀在产品开发的中后期阶段,系统已逐步趋于稳定,每次软件发布版本后使用自动化脚本即可完成大部分基础功能验证,无需人工再次轮询测试用例,极大地节省了人力和时间成本㊂此外,在压力和性能测试方面,该工具获取的数据比手动测试更为科学准确,帮助了产品团队迅速准确地了解产品的性能,为产品的优化和改进提供了坚实的依据㊂UIAutomator2自动化测试工具在保证产品质量㊁提高测试效率以及节省时间和人力成本等方面都发挥了人工测试不可替代的作用㊂3㊀结语㊀㊀本文通过对智能Andriod车机系统稳定性测试方案及Monkey和UIAutomator2自动化测试工具的研究,设计并实现了2种自动化稳定性测试工具㊂这些㊀㊀工具在实际项目中切实提高了工作效率和产品质量㊂随着车联网和智能网联产品的不断发展,IVI娱乐系统的稳定性测试将越来越受到重视,类似的自动化测试工具将发挥更为广泛和重要的作用,对于推动车载智能产品的发展有着重要的意义㊂参考文献[1]CHUN W.Python核心编程[M].3版.北京:人民邮电出版社,2016.[2]蒲天杭.基于Python语言的仪器管理与测试系统研究[J].中国仪器仪表,2020(2):52-55.[3]江永聪.基于DBC的汽车CAN报文远程采集与分析系统设计[J].电子技术与软件工程,2014(14): 203-204.(编辑㊀王永超)Design and implementation of stability testing for Android IVI systems andautomation testing toolsLiu MengNanjing Normal University of Special Education Nanjing210038 ChinaAbstract With the increasing complexity of features in Android IVI entertainment systems resulting in more and more safety and stability issues occurred.In order to improve the efficiency of product development and testing ensure product stability and performance this article studied Andriod IVI system stability testing scheme designed and implemented two automation stability testing tools based on Python Monkey UIAutomator2.These tools have effectively demonstrated effects that cannot be replaced by manual testing in real-world projects.Key words stability testing Python Monkey UIAutomator2。

软件测试常用英语词汇静态测试：Non-Execution-Based Testing或Static testing代码走查：Walkthrough代码审查：Code Inspection技术评审：Review动态测试：Execution-Based Testing白盒测试：White-Box Testing黑盒测试：Black-Box Testing灰盒测试：Gray-Box Testing软件质量保证SQA：Software Quality Assurance软件开发生命周期：Software Development Life Cycle冒烟测试：Smoke Test回归测试：Regression Test功能测试：Function Testing性能测试：Performance Testing压力测试：Stress Testing负载测试：Volume Testing易用性测试：Usability Testing安装测试：Installation Testing界面测试：UI Testing配置测试：Configuration Testing文档测试：Documentation Testing兼容性测试：Compatibility Testing安全性测试：Security Testing恢复测试：Recovery Testing单元测试：Unit Test集成测试：Integration Test系统测试：System Test验收测试：Acceptance Test测试计划应包括：测试对象：The Test Objectives测试范围： The Test Scope测试策略： The Test Strategy测试方法： The Test Approach;测试过程： The test procedures;测试环境： The Test Environment;测试完成标准：The test Completion criteria 测试用例：The Test Cases测试进度表：The Test Schedules风险：Risks接口：Interface最终用户：The End User正式的测试环境：Formal Test Environment确认需求：Verifying The Requirements有分歧的需求：Ambiguous Requirements运行和维护：Operation and Maintenance.可复用性：Reusability可靠性： Reliability/Availability电机电子工程师协会IEEE：The Institute of Electrical and Electronics Engineers正确性：Correctness实用性：Utility健壮性：Robustness可靠性：Reliability软件需求规格说明书：SRS software requirement specification概要设计：HLD high level design详细设计：LLD low level design统一开发流程：RUP rational unified process集成产品开发：IPD integrated product development能力成熟模型：CMM capability maturity model能力成熟模型集成：CMMI capability maturity model integration戴明环：PDCA plan do check act软件工程过程组：SEPG software engineering process group集成测试：IT integration testing系统测试：ST system testing关键过程域：KPA key process area同行评审：PR peer review用户验收测试：UAT user acceptance testing验证和确认：V&V verification & validation控制变更委员会：CCB change control board图形用户界面：GUI graphic user interface配置管理员：CMO configuration management officer 平均失效间隔时间：MTBF mean time between failures 平均修复时间：MTTR mean time to restoration平均失效时间：MTTF mean time to failure工作任务书：SOW statement of workα测试：alpha testingβ测试：beta testing适应性：Adaptability可用性：Availability功能规格说明书：Functional Specification软件开发中常见英文缩写和各类软件开发文档的英文缩写：英文简写文档名称MRD market requirement document 市场需求文档PRD product requirement document 产品需求文档SOW 工作任务说明书PHB Process Handbook 项目过程手册EST Estimation Sheet 估计记录PPL Project Plan 项目计划CMP Software Management Plan 配置管理计划QAP Software Quality Assurance Plan 软件质量保证计划RMP Software Risk Management Plan 软件风险管理计划TST Test Strategy测试策略WBS Work Breakdown Structure 工作分解结构BRS Business Requirement Specification业务需求说明书SRS Software Requirement Specification软件需求说明书STP System Testing plan 系统测试计划STC System Testing Cases 系统测试用例HLD High Level Design 概要设计说明书ITP Integration Testing plan 集成测试计划ITC Integration Testing Cases 集成测试用例LLD Low Level Design 详细设计说明书UTP Unit Testing Plan 单元测试计划UTC Unit Testing Cases 单元测试用例UTR Unit Testing Report 单元测试报告ITR Integration Testing Report 集成测试报告STR System Testing Report 系统测试报告RTM Requirements Traceability Matrix 需求跟踪矩阵CSA Configuration Status Accounting 配置状态发布CRF Change Request Form 变更申请表WSR Weekly Status Report 项目周报QSR Quality Weekly Status Report 质量工作周报QAR Quality Audit Report质量检查报告QCL Quality Check List质量检查表PAR Phase Assessment Report 阶段评估报告CLR Closure Report 项目总结报告RFF Review Finding Form 评审发现表MOM Minutes of Meeting 会议纪要MTX Metrics Sheet 度量表CCF ConsistanceCheckForm一致性检查表BAF Baseline Audit Form基线审计表PTF Program Trace Form问题跟踪表领测国际科技北京有限公司软件测试中英文对照术语表AAbstract test case High level test case ：概要测试用例 Acceptance：验收Acceptance criteria：验收标准Acceptance testing：验收测试Accessibility testing：易用性测试Accuracy：精确性Actual outcome actual result ：实际输出/实际结果 Ad hoc review informal review ：非正式评审Ad hoc testing：随机测试Adaptability：自适应性Agile testing：敏捷测试Algorithm test branch testing ：分支测试Alpha testing：alpha 测试Analyzability：易分析性Analyzer：分析员Anomaly：异常Arc testing：分支测试Attractiveness：吸引力Audit：审计Audit trail：审计跟踪Automated testware：自动测试组件Availability：可用性BBack-to-back testing：对比测试Baseline：基线Basic block：基本块Basis test set：基本测试集Bebugging：错误撒播Behavior：行为Benchmark test：基准测试Bespoke software：定制的软件Best practice：最佳实践Beta testing：Beta 测试领测国际科技北京有限公司Big-bang testing：集成测试Black-box technique：黑盒技术Black-box testing：黑盒测试Black-box test design technique：黑盒测试设计技术Blocked test case：被阻塞的测试用例Bottom-up testing：自底向上测试Boundary value：边界值Boundary value analysis：边界值分析Boundary value coverage：边界值覆盖率Boundary value testing：边界值测试Branch：分支Branch condition：分支条件Branch condition combination coverage：分支条件组合覆盖率 Branch condition combination testing：分支条件组合测试Branch condition coverage：分支条件覆盖率Branch coverage：分支覆盖率Branch testing：分支测试Bug：缺陷Business process-based testing：基于商业流程的测试CCapability Maturity Model CMM ：能力成熟度模型Capability Maturity Model Integration CMMI ：集成能力成熟度模型Capture/playback tool：捕获/回放工具Capture/replay tool：捕获/重放工具CASE Computer Aided Software Engineering ：电脑辅助软件工程 CAST Computer Aided Software Testing ：电脑辅助软件测试Cause-effect graph：因果图Cause-effect graphing：因果图技术Cause-effect analysis：因果分析Cause-effect decision table：因果判定表Certification：认证Changeability：可变性Change control：变更控制Change control board：变更控制委员会Checker：检查人员Chow's coverage metrics N-switch coverage ：N 切换覆盖率 Classification tree method：分类树方法Code analyzer：代码分析器Code coverage：代码覆盖率领测国际科技北京有限公司Code-based testing：基于代码的测试Co-existence：共存性Commercial off-the-shelf software：商用离岸软件Comparator：比较器Compatibility testing：兼容性测试Compiler：编译器Complete testing：完全测试/穷尽测试Completion criteria：完成标准Complexity：复杂性Compliance：一致性Compliance testing：一致性测试Component：组件Component integration testing：组件集成测试Component specification：组件规格说明Component testing：组件测试Compound condition：组合条件Concrete test case low level test case ：详细测试用例Concurrency testing：并发测试Condition：条件表达式Condition combination coverage：条件组合覆盖率Condition coverage：条件覆盖率Condition determination coverage：条件判定覆盖率 Condition determination testing：条件判定测试Condition testing：条件测试Condition outcome：条件结果Confidence test smoke test ：信心测试冒烟测试Configuration：配置Configuration auditing：配置审核Configuration control：配置控制Configuration control board CCB ：配置控制委员会 Configuration identification：配置标识Configuration item：配置项Configuration management：配置管理Configuration testing：配置测试Confirmation testing：确认测试Conformance testing：一致性测试Consistency：一致性Control flow：控制流Control flow graph：控制流图Control flow path：控制流路径Conversion testing：转换测试COTS Commercial Off-The-Shelf software ：商业离岸软件 Coverage：覆盖率Coverage analysis：覆盖率分析领测国际科技北京有限公司Coverage item：覆盖项Coverage tool：覆盖率工具Custom software：定制软件Cyclomatic complexity：圈复杂度Cyclomatic number：圈数DDaily build：每日构建Data definition：数据定义Data driven testing：数据驱动测试Data flow：数据流Data flow analysis：数据流分析Data flow coverage：数据流覆盖率Data flow test：数据流测试Data integrity testing：数据完整性测试Database integrity testing：数据库完整性测试Dead code：无效代码Debugger：调试器Debugging：调试Debugging tool：调试工具Decision：判定Decision condition coverage：判定条件覆盖率 Decision condition testing：判定条件测试Decision coverage：判定覆盖率Decision table：判定表Decision table testing：判定表测试Decision testing：判定测试技术Decision outcome：判定结果Defect：缺陷Defect density：缺陷密度Defect Detection Percentage DDP ：缺陷发现率 Defect management：缺陷管理Defect management tool：缺陷管理工具Defect masking：缺陷屏蔽Defect report：缺陷报告Defect tracking tool：缺陷跟踪工具Definition-use pair：定义-使用对Deliverable：交付物Design-based testing：基于设计的测试Desk checking：桌面检查领测国际科技北京有限公司Development testing：开发测试Deviation：偏差Deviation report：偏差报告Dirty testing：负面测试Documentation testing：文档测试Domain：域Driver：驱动程序Dynamic analysis：动态分析Dynamic analysis tool：动态分析工具Dynamic comparison：动态比较Dynamic testing：动态测试EEfficiency：效率Efficiency testing：效率测试Elementary comparison testing：基本组合测试 Emulator：仿真器、仿真程序Entry criteria：入口标准Entry point：入口点Equivalence class：等价类Equivalence partition：等价区间Equivalence partition coverage：等价区间覆盖率Equivalence partitioning：等价划分技术Error：错误Error guessing：错误猜测技术Error seeding：错误撒播Error tolerance：错误容限Evaluation：评估Exception handling：异常处理Executable statement：可执行的语句Exercised：可执行的Exhaustive testing：穷尽测试Exit criteria：出口标准Exit point：出口点Expected outcome：预期结果Expected result：预期结果Exploratory testing：探测测试领测国际科技北京有限公司FFail：失败Failure：失败Failure mode：失败模式Failure Mode and Effect Analysis FMEA ：失败模式和影响分析Failure rate：失败频率Fault：缺陷Fault density：缺陷密度Fault Detection Percentage FDP ：缺陷发现率Fault masking：缺陷屏蔽Fault tolerance：缺陷容限Fault tree analysis：缺陷树分析Feature：特征Field testing：现场测试Finite state machine：有限状态机Finite state testing：有限状态测试Formal review：正式评审Frozen test basis：测试基线Function Point Analysis FPA ：功能点分析Functional integration：功能集成Functional requirement：功能需求Functional test design technique：功能测试设计技术 Functional testing：功能测试Functionality：功能性Functionality testing：功能性测试Gglass box testing：白盒测试HHeuristic evaluation：启发式评估High level test case：概要测试用例Horizontal traceability：水平跟踪领测国际科技北京有限公司IImpact analysis：影响分析Incremental development model：增量开发模型 Incremental testing：增量测试Incident：事件Incident management：事件管理Incident management tool：事件管理工具Incident report：事件报告Independence：独立Infeasible path：不可行路径Informal review：非正式评审Input：输入Input domain：输入范围Input value：输入值Inspection：审查Inspection leader：审查组织者Inspector：审查人员Installability：可安装性Installability testing：可安装性测试Installation guide：安装指南Installation wizard：安装向导Instrumentation：插装Instrumenter：插装工具Intake test：入口测试Integration：集成Integration testing：集成测试Integration testing in the large：大范围集成测试 Integration testing in the small：小范围集成测试 Interface testing：接口测试Interoperability：互通性Interoperability testing：互通性测试Invalid testing：无效性测试Isolation testing：隔离测试Item transmittal report：版本发布报告Iterative development model：迭代开发模型KKey performance indicator：关键绩效指标领测国际科技北京有限公司Keyword driven testing：关键字驱动测试LLearnability：易学性Level test plan：等级测试计划Link testing：组件集成测试Load testing：负载测试Logic-coverage testing：逻辑覆盖测试 Logic-driven testing：逻辑驱动测试Logical test case：逻辑测试用例Low level test case：详细测试用例MMaintenance：维护Maintenance testing：维护测试Maintainability：可维护性Maintainability testing：可维护性测试 Management review：管理评审Master test plan：综合测试计划Maturity：成熟度Measure：度量Measurement：度量Measurement scale：度量粒度Memory leak：内存泄漏Metric：度量Migration testing：移植测试Milestone：里程碑Mistake：错误Moderator：仲裁员Modified condition decision coverage：改进的条件判定覆盖率Modified condition decision testing：改进的条件判定测试Modified multiple condition coverage：改进的多重条件判定覆盖率Modified multiple condition testing：改进的多重条件判定测试 Module：模块Module testing：模块测试Monitor：监视器Multiple condition：多重条件Multiple condition coverage：多重条件覆盖率领测国际科技北京有限公司Multiple condition testing：多重条件测试Mutation analysis：变化分析Mutation testing：变化测试NN-switch coverage：N 切换覆盖率N-switch testing：N 切换测试Negative testing：负面测试Non-conformity：不一致Non-functional requirement：非功能需求Non-functional testing：非功能测试Non-functional test design techniques：非功能测试设计技术OOff-the-shelf software：离岸软件Operability：可操作性Operational environment：操作环境Operational profile testing：运行剖面测试Operational testing：操作测试Oracle：标准Outcome：输出/结果Output：输出Output domain：输出范围Output value：输出值PPair programming：结队编程Pair testing：结队测试Partition testing：分割测试Pass：通过Pass/fail criteria：通过/失败标准Path：路径Path coverage：路径覆盖Path sensitizing：路径敏感性Path testing：路径测试领测国际科技北京有限公司Peer review：同行评审Performance：性能Performance indicator：绩效指标Performance testing：性能测试Performance testing tool：性能测试工具 Phase test plan：阶段测试计划Portability：可移植性Portability testing：移植性测试Postcondition：结果条件Post-execution comparison：运行后比较 Precondition：初始条件Predicted outcome：预期结果Pretest：预测试Priority：优先级Probe effect：检测成本Problem：问题Problem management：问题管理Problem report：问题报告Process：流程Process cycle test：处理周期测试Product risk：产品风险Project：项目Project risk：项目风险Program instrumenter：编程工具Program testing：程序测试Project test plan：项目测试计划Pseudo-random：伪随机QQuality：质量Quality assurance：质量保证Quality attribute：质量属性Quality characteristic：质量特征Quality management：质量管理领测国际科技北京有限公司RRandom testing：随机测试Recorder：记录员Record/playback tool：记录/回放工具 Recoverability：可复原性Recoverability testing：可复原性测试Recovery testing：可复原性测试Regression testing：回归测试Regulation testing：一致性测试Release note：版本说明Reliability：可靠性Reliability testing：可靠性测试Replaceability：可替换性Requirement：需求Requirements-based testing：基于需求的测试 Requirements management tool：需求管理工具 Requirements phase：需求阶段Resource utilization：资源利用Resource utilization testing：资源利用测试 Result：结果Resumption criteria：继续测试标准Re-testing：再测试Review：评审Reviewer：评审人员Review tool：评审工具Risk：风险Risk analysis：风险分析Risk-based testing：基于风险的测试Risk control：风险控制Risk identification：风险识别Risk management：风险管理Risk mitigation：风险消减Robustness：健壮性Robustness testing：健壮性测试Root cause：根本原因SSafety：安全领测国际科技北京有限公司Safety testing：安全性测试Sanity test：健全测试Scalability：可测量性Scalability testing：可测量性测试Scenario testing：情景测试Scribe：记录员Scripting language：脚本语言Security：安全性Security testing：安全性测试Serviceability testing：可维护性测试 Severity：严重性Simulation：仿真Simulator：仿真程序、仿真器Site acceptance testing：定点验收测试Smoke test：冒烟测试Software：软件Software feature：软件功能Software quality：软件质量Software quality characteristic：软件质量特征Software test incident：软件测试事件Software test incident report：软件测试事件报告Software Usability Measurement Inventory SUMI ：软件可用性调查问卷Source statement：源语句Specification：规格说明Specification-based testing：基于规格说明的测试Specification-based test design technique：基于规格说明的测试设计技术Specified input：特定输入Stability：稳定性Standard software：标准软件Standards testing：标准测试State diagram：状态图State table：状态表State transition：状态迁移State transition testing：状态迁移测试Statement：语句Statement coverage：语句覆盖Statement testing：语句测试Static analysis：静态分析Static analysis tool：静态分析工具Static analyzer：静态分析工具Static code analysis：静态代码分析Static code analyzer：静态代码分析工具Static testing：静态测试Statistical testing：统计测试领测国际科技北京有限公司Status accounting：状态统计Storage：资源利用Storage testing：资源利用测试Stress testing：压力测试Structure-based techniques：基于结构的技术Structural coverage：结构覆盖Structural test design technique：结构测试设计技术 Structural testing：基于结构的测试Structured walkthrough：面向结构的走查Stub: 桩Subpath: 子路径Suitability: 符合性Suspension criteria: 暂停标准Syntax testing: 语法测试System:系统System integration testing：系统集成测试System testing：系统测试TTechnical review：技术评审Test：测试Test approach：测试方法Test automation：测试自动化Test basis：测试基础Test bed：测试环境Test case：测试用例Test case design technique：测试用例设计技术 Test case specification：测试用例规格说明Test case suite：测试用例套Test charter：测试宪章Test closure：测试结束Test comparator：测试比较工具Test comparison：测试比较Test completion criteria：测试比较标准Test condition：测试条件Test control：测试控制Test coverage：测试覆盖率Test cycle：测试周期Test data：测试数据Test data preparation tool：测试数据准备工具领测国际科技北京有限公司Test design：测试设计Test design specification：测试设计规格说明 Test design technique：测试设计技术Test design tool: 测试设计工具Test driver: 测试驱动程序Test driven development: 测试驱动开发Test environment: 测试环境Test evaluation report: 测试评估报告Test execution: 测试执行Test execution automation: 测试执行自动化 Test execution phase: 测试执行阶段Test execution schedule: 测试执行进度表Test execution technique: 测试执行技术Test execution tool: 测试执行工具Test fail: 测试失败Test generator: 测试生成工具Test leader:测试负责人Test harness：测试组件Test incident：测试事件Test incident report：测试事件报告Test infrastructure：测试基础组织Test input：测试输入Test item：测试项Test item transmittal report：测试项移交报告 Test level：测试等级Test log：测试日志Test logging：测试记录Test manager：测试经理Test management：测试管理Test management tool：测试管理工具Test Maturity Model TMM ：测试成熟度模型Test monitoring：测试跟踪Test object：测试对象Test objective：测试目的Test oracle：测试标准Test pass：测试通过Test performance indicator：测试绩效指标Test phase：测试阶段Test plan：测试计划Test planning：测试计划Test policy：测试方针Test Point Analysis TPA ：测试点分析Test procedure：测试过程领测国际科技北京有限公司Test procedure specification：测试过程规格说明 Test process：测试流程Test Process Improvement TPI ：测试流程改进 Test record：测试记录Test recording：测试记录Test reproduceability：测试可重现性Test report：测试报告Test requirement：测试需求Test run：测试运行Test run log：测试运行日志Test result：测试结果Test scenario：测试场景Test set：测试集Test situation：测试条件Test specification：测试规格说明Test specification technique：测试规格说明技术 Test stage：测试阶段Test strategy：测试策略Test suite：测试套Test summary report：测试总结报告Test target：测试目标Test tool：测试工具Test type：测试类型Testability：可测试性Testability review：可测试性评审Testable requirements：需求可测试性Tester：测试人员Testing：测试Testware：测试组件Thread testing：组件集成测试Time behavior：性能Top-down testing：自顶向下的测试Traceability：可跟踪性UUnderstandability：易懂性Unit：单元unit testing：单元测试Unreachable code：执行不到的代码领测国际科技北京有限公司Usability：易用性Usability testing：易用性测试Use case：用户用例Use case testing：用户用例测试User acceptance testing：用户验收测试 User scenario testing：用户场景测试 User test：用户测试VV -model：V 模式Validation：确认Variable：变量Verification：验证Vertical traceability：垂直可跟踪性 Version control：版本控制Volume testing：容量测试WWalkthrough：走查White-box test design technique：白盒测试设计技术 White-box testing：白盒测试Wide Band Delphi：Delphi 估计方法。

测试框架设计的几点原则本系列从如何构建结构良好的测试框架、高效的对象缓存机制，以及测试 Windows 应用程序的技巧和方法等方面，介绍如何运用 RFT 测试 Windows/.NET 应用程序。

∙一种高效的对象缓存机制在测试框架中的应用∙利用 Windows Domain 测试 Windows 控件∙对 TestObject.find() 方法的扩展与改进一个好的测试框架需要具备哪些元素呢？虽然对不同的项目而言，答案可能有所不同。

但总的来说，一个好的测试框架通常具有以下的共同特点：∙分层结构∙关注分离∙代码重用∙结构清晰∙易于维护∙方便调试∙可扩展性好除了以上所述的几点外，一个好的框架还应该提供相应的通用服务，以使得脚本开发者可以很容易而且快速地基于它来开发脚本。

比如象错误处理，本地化版本支持，日志服务等。

回页首定义良好的层次结构如何定义一个良好的层次结构，是我们在构建测试框架首先需要考虑的问题。

通常我们会把最基本的一些原子操作放在最底层，而在较上层封装这些操作，并开放相应的接口供最终的脚本开发者进行调用。

这样往往会使得 Case 更加简洁易读。

根据面向对象基本理论，我们首先要定义一些基础的控件类，用来代表那些需要在测试中进行操作的基本界面元素，象按钮，输入框等。

如果你使用 RFT 测试 Java 或 Web 应用，那么你可以直接使用 IBM Package，在这个包里封装了所有的在 Java 和 Web 这两个 Domain 下的基本控件。

通过在你的脚本中调用这些类，你就可以很方便地实现对被测应用的操纵。

但是，我们所测试的应用是基于 Windows .Net 的，在这个包里没有对应的控件类可以利用，因此，第一步，我们要开发自己的控件类。

其实，我们也可以不定义基础类，而直接使用 GUITestObject 来操纵每一个界面对象，但这样做的代价是显而易见的，会有很多重复且不易读的代码充斥在我们的脚本中。

idea怎么写测试用例How to Write Test Cases in IntelliJ IDEA.1. Create a New Test Class.Right-click on the source folder and select New > Java Class.Name the class appropriately, such as `MyClassTest`.Select the checkbox for Create Test Class.2. Add Test Methods.Add test methods to the test class using the following syntax:java.@Test.public void testMethodName() {。

// Arrange.// Act.// Assert.}。

The `@Test` annotation indicates that the method should be run as a test.The method name should describe the purpose of the test.The `Arrange`, `Act`, and `Assert` sections represent the three phases of a test:Arrange: Set up the necessary environment and data for the test.Act: Perform the action or operation that is being tested.Assert: Verify that the expected output matches the actual output.3. Write Assertions.Use assertion methods to verify the expected and actual results.IntelliJ IDEA provides a variety of assertion methods, such as:`assertEquals(expected, actual)`。

IMSActivity GroupTest Cases - IMS Profile for Voiceand SMSVersion 1.24 October 2013HistoryVersion Date Name Reason1.0 15-08-2011 Bo Jönsson Version 0.12 and CR 3, 4, 5, 26, 27, 32, 33, 35 and 36.1.1 21-02-2013 Bo Jönsson CR 37, 46, 47, 48, 49, 54, 55, 56, 67, 68, 69 and 70. 1.2 18-06-2013 Bo Jönsson CR 57, 58, 59, 60 and 71.Table of Contents1 Introduction (5)1.1 Scope (5)1.2 How to Read the Test Cases (5)1.2.1 Defining Test Cases (5)1.3 Abbreviations and Definitions (5)1.3.1 Definitions (5)1.3.2 Abbreviations (6)1.4 Default Endpoint Settings (6)1.5 Test Case Number Representation (6)1.5.1 Test Case Number (6)1.6 How to Use Test Cases (6)2 Interoperability Tests (7)2.0 Test Procedures (7)2.0.1 Minimum Passing Criteria (7)2.1 Registration & Authentication (7)Test Case 2.1.1 – ISIM based UE authentication to IMS core network, using IMS-AKA (7)Test Case 2.1.2 – USIM based UE authentication to IMS core network, using IMS-AKA (8)Test Case 2.1.3 – UE de-registration from IMS core network (9)2.2 Call establishment and termination (10)Test Case 2.2.1 – Originating - Voice call set-up (10)Test Case 2.2.2 – Terminating - Voice call set-up (11)Test Case 2.2.3 – Terminating - video call set-up to a UE which only supports audio (12)Test Case 2.2.4 – Terminating – audio to video upgrade to a UE which only supports audio (13)Test Case 2.2.5 – Originating - Voice call set-up (SIP precondition not used in network) (13)Test Case 2.2.6 – Terminating - Voice call set-up (SIP precondition not used in network) (15)Test Case 2.2.8 – UE originated call to Home-Local Number (16)Test Case 2.2.9 – UE originated call to Geo-Local Number (17)2.3 Supplementary Services Test Cases (17)Test Case 2.3.1 – Originating Identification Presentation not subscribed (17)Test Case 2.3.2 – Originating Identification Presentation subscribed (18)Test Case 2.3.3 – Originating Identification Restriction (18)Test Case 2.3.4 – Terminating Identification Presentation subscribed (19)Test Case 2.3.4A – Terminating Identification Presentation not subscribed (20)Test Case 2.3.5 – Terminating Identification Restriction (20)Test Case 2.3.6 – Communication Forwarding unconditional (21)Test Case 2.3.7 – Originating – Communication HOLD (22)Test Case 2.3.8 – Terminating – Communication HOLD (23)Test Case 2.3.9 – Communication Forwarding on no Reply: limited ringing duration (24)Test Case 2.3.10 – Originating – Creating a conference (25)Test Case 2.3.11 – Terminating – Joining a conference after receiving an invitation (27)Test Case 2.3.12 – Communication forwarding on busy (29)Test Case 2.3.14 – Barring of All Incoming Calls (29)Test Case 2.3.15 – Barring of All Outgoing Calls (30)Test Case 2.3.16 – Barring of Outgoing International Calls (31)Test Case 2.3.17 – Barring of Incoming Calls when Roaming (32)Test Case 2.3.18 – Communication forwarding on not Reachable (33)Test Case 2.3.19 – Communication Waiting (33)2.4 SMS over IP (34)Test Case 2.4.1 – Originating – SMS over IP (34)Test Case 2.4.2 – Terminating – SMS over IP (35)Test Case 2.4.3 – Originating – SMS over IP (more than 160 characters) (36)Test Case 2.4.4 – Terminating – SMS over IP (more than 160 characters) (37)Test Case 2.4.5 – Originating – SMS over IP: destination UE not reachable, SMS stored in SMSC. Destination UE becomes reachable, stored SMS is delivered. Delivery report is sent to originating UE. 39Test Case 2.4.6 – Terminating – SMS over IP: destination UE not reachable, SMS stored in SMSC. Destination UE becomes reachable, stored SMS is delivered. (40)2.5 SMS over SGs (42)Test Case 2.5.1 – Originating – SMS over SGs during EMM-IDLE state (42)Test Case 2.5.2 – Originating – SMS over SGs during EMM-CONNECTED state (43)Test Case 2.5.3 – Terminating – SMS over SGs during EMM-IDLE state (44)Test Case 2.5.4 – Terminating – SMS over SGs during EMM-CONNECTED state (45)2.6 DTMF (45)Test Case 2.6.1 – Originating - DTMF sending over RTP payload (45)2.7 Emergency Service (46)Test Case 2.7.1 – Emergency call (46)Test Case 2.7.2 – Emergency call in limited service (47)2.8 SRVCC (48)Test Case 2.8.1 – SRVCC from E-UTRAN to GERAN without DTM support (48)3 References (53)1 IntroductionThis document describes the Test cases for IMS Client Application interoperability tests for terminal interoperability validation. This includes common scenarios for compliance testing. The optional tests section might be enhanced by additional tests of the testing parties as only the most probable test cases are described here.For further terminal compliance test cases, please refer to the document “Test Cases – Compliance”.1.1 ScopeThe present document defines terminal interoperability test cases for VoLTE as defined by the GSMA PRD IR.92.The present document is applicable to:- The interface between the User Equipment (UE) and the Call Session Control Function (CSCF);- The interface between the User Equipment (UE) and an Application Server (AS);1.2 How to Read the Test CasesTest Number: Identifies each of the Test Cases by its unique number.Priority: Indicates if the test case is mandatory or optional if not indicated by a document section. Objective: Provides background information description about the test case.Reference: Indicates corresponding section of recommendation or specification for the test case.UE Setup: Specifies all required UE settings for the named test case.NW Setup: Specifies required network settings for the named test case.Precondition: Specifies settings and environment required before conducting the test case. Procedure: Describes how to conduct the test case.Miscellaneous: Provides additional information such as illustrations on message sequences and expected header parameters.Pass Criteria: Defines the Pass Criteria of the test case. Sub results to be performed successfully are listed. Verification of the correct behaviour may be visual, together with the aid of logging facilities available from the testing terminals.1.2.1 Defining Test CasesWhen defining a test case, all of the above fields shall be included except those that indicate “optional”. When there is no information to be provided to a non-optional field, the field shall be filled with “None”.By the time the Test Case document is updated, some fields may not have been updated and are marked with TBA. These fields are expected to be filled in in later versions of this test case document.1.3 Abbreviations and Definitions1.3.1 DefinitionsFor the purposes of the present document the following definitions apply: FFS1.3.2 AbbreviationsFor the purposes of the present document the following abbreviations apply:3GPP - Third Generation Partnership ProjectHTTP - HyperText Transfer ProtocolIMS - IP Multimedia SubsystemMTSI - Multimedia Telephony Service for IMSOIP - Originating Identity PresentationOIR - Originating Identity RestrictionCaseTC - TestEquipmentUE - UserURI - Uniform Resource IdentifierXCAP - eXtensible markup language Configuration Access ProtocolSettings1.4 DefaultEndpointTwo types of default endpoint settings are defined, which are Default Test Terminal Settings and Default Test Tool Settings. Default Test Terminal Settings are for UEUTs, which are not expected to change configurations. Default Test Tool Settings are for test reference tools, which are capable of varying a wide range of terminal configurations.1.5 Test Case Number RepresentationTest case number representation shall be used for test score sheet reporting purpose.1.5.1 Test Case NumberEach Test Case is represented by a unique number.If a new test case needs to be added for feature grouping purpose in between two existing test cases with consecutive test case numbers, a hyphen with a number is added to the test case number, e.g. Test Case 29-1 is inserted in between Test Case 29 and Test Case 30.Cancelled Test Case number will not be reused for tests different from the original context.If the terminal settings are identical for both Terminal A and Terminal B, the unique number itself is sufficient to represent the Test Case, e.g. Test Case 1.When the terminal settings are different, the test case number should be added with a postfix letter ‘a’ or ‘b’ according to the terminal settings used, e.g. Test Case 2a and Test Case 2b.1.6 How to Use Test CasesThis test case document can be used according to the need of a company. It forms the basis for all kinds of IMS client application interoperability test events hosted by IMTC and IMTC IMS AG. It may be adopted by external parties according to their needs.It is recommended all mandatory test cases should be conducted for every test event. All optional test cases are tested by priority as agreed by the two testing parties.Test cases are regarded as successful when both testing terminals follow the testing procedure and the expected behaviour is observed.All test results are recorded into test score sheet.2 Interoperability TestsProcedures2.0 TestAll tests shall be performed in that way that the device is not reset (removal of battery, shutdown) in between performing the following described tests.2.0.1 Minimum Passing CriteriaIn each test case, the following criteria shall be satisfied for passing the test case unless otherwise stated: The pass criteria are specified in each test case.& Authentication2.1 RegistrationTest Case 2.1.1 –ISIM based UE authentication to IMS core network, using IMS-AKA[1] REGISTER (Request-URI) SIP/2.0Authorization: (credentials)Expires: (value)[3] REGISTER (Request-URI) SIP/2.0Authorization: (credentials)Expires: (value)Pass Criteria: The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified.Note: UE_1 may display an IMS Registered Icon.Test Case 2.1.2 –USIM based UE authentication to IMS core network, using IMS-AKA[1] REGISTER (Request-URI) SIP/2.0Authorization: (credentials)Expires: (value)[3] REGISTER (Request-URI) SIP/2.0Authorization: (credentials)Expires: (value)Pass Criteria: The message sequence, order and header/parameters in the miscellaneous section of this test case shall be verified.Note: UE_1 may display an IMS Registered Icon.Test Case 2.1.3 –UE de-registration from IMS core networkNote: UE may indicate that it is not IMS Registered on the display.2.2 Call establishment and terminationTest Case 2.2.1 –Originating - Voice call set-upContent-Length: (value)m=audio (transport port) RTP/AVP (fmt)b=AS: (bandwidth-value)b=RS:0b=RR:0a=rtpmap:(payload type) AMR/8000/1a=fmtp:(format) mode-change-capability=2; max-red=220a=rtpmap:(payload type) telephone-eventa=ptime:20a=maxptime:240a=curr:qos local nonea=curr:qos remote nonea=des:qos mandatory local sendrecva=des:qos optional remote sendrecvPass Criteria: The voice call is established and successful speech between UE_1 and UE_2.The message sequence, order and header/parameters in the miscellaneoussection of this test case shall be verified.Test Case 2.2.2 –Terminating - Voice call set-upPriority: Mandatory TCObjective: Verify that a terminating IMS voice call is established.Reference: TS 24.173, TS 24.229 and TS 26.114UE_1 Setup: -UE_2 Setup: -NW Setup: SIP preconditions enabled.Precondition: 1.UE_1 and UE_2 are connected and registered to an IMS network.2.UE_1 and UE_2 support speech.3.UE_1_and UE_2 support SIP preconditions and reliable provisionalresponses.Procedure: 1.UE_2: dial a voice call to UE_1.2.UE_1: answer call.3.Speech.Miscellaneous: Messages SequenceTest Case 2.2.3 –Terminating - video call set-up to a UE which only supports audio Priority: Optional TCObjective: Verify that a terminating audio-only UE is able to accept a video call request and downgrade it to audio-only call.Reference: TS 24.173, TS 24.229, TS 26.114UE_1 Setup: -UE_2 Setup: -NW Setup: -Precondition: 1.UE_1 and UE_2 are connected and registered to an IMS network.2.UE_2 supports audio and video.3.UE_1 supports only audio.2.UE_1: answer call.3.UE_1: release call.Miscellaneous: -Pass Criteria: UE_1 accepts the video call request and replies with 200 OK response where the media port for video is set to zero. Successful audio call isestablished between UE_1 and UE_2.Test Case 2.2.4 –Terminating – audio to video upgrade to a UE which only supports audioPriority: Optional TCObjective: Verify that the audio-only UE will accept the re-INVITE request to updatethe session from audio to video.Reference: TS 24.173, TS 24.229, TS 26.114UE_1 Setup: -UE_2 Setup: -NW Setup: -Precondition: 1.UE_1 and UE_2 are connected and registered to an IMS network.2.UE_1 supports only audio.3.UE_2 supports audio and video.Procedure: 1.UE_2: dial an audio call to UE_1.2.UE_1: answer audio call.3.Speech.4.UE_2: adds a video to existing call.5.Speech.6.UE_1: release call.Miscellaneous: -Pass Criteria: First, a successful audio call is established between UE_1 and UE_2. WhenUE_1 receives a re-INVITE to add video to the session, UE_1 accepts thevideo call request and replies with 200 OK response where the media portfor video is set to zero. Audio session remains active.Test Case 2.2.5 –Originating - Voice call set-up (SIP precondition not used in network)Priority: Mandatory TCObjective: Verify that an originating IMS voice call is established.Reference: TS 24.173, TS 24.229, TS 26.114Test Case 2.2.6 –Terminating - Voice call set-up (SIP precondition not used in network)NOTE: A 200 OK might be the response to the INVITE or an UPDATE. Test Case 2.2.8 –UE originated call to Home-Local NumberTest Case 2.2.9 –UE originated call to Geo-Local NumberServices Test Cases2.3 SupplementaryTest Case 2.3.1 –Originating Identification Presentation not subscribedPriority: Optional TCObjective: Verify UE behaviour when originating identification presentation is notsubscribedReference: TS 24.607UE_1 Setup: UE_1 subscription does not contain the Originating IdentificationPresentation serviceUE_2 Setup: -NW Setup: -Precondition: 1.UE_1 and UE_2 are connected and registered to an IMS network.2.UE_1 and UE_2 support speech.Procedure: 1.Perform a voice call according the test case 2.2.2.Miscellaneous: -Pass Criteria: Successful restriction of the UE_2 identity in UE_1.Test Case 2.3.2 –Originating Identification Presentation subscribedPriority: Optional TCObjective: Verify UE behaviour when originating identification presentation is subscribedReference: TS 24.607UE_1 Setup: UE_1 subscription contains the Originating Identification Presentation serviceUE_2 Setup: -NW Setup: -Precondition: 1.UE_1 and UE_2 are connected and registered to an IMS network.2.UE_1 and UE_2 support speech.Procedure: 1.Perform a voice call according the test case 2.2.2.Miscellaneous: -Pass Criteria: Successful presentation of the UE_2 identity in UE_1.Test Case 2.3.3 –Originating Identification RestrictionPriority: Mandatory TCObjective: Verify originating identification restriction.Reference: TS 24.607UE_1 Setup: -UE_2 Setup: -NW Setup: Originating Identification Restriction service is provisioned for UE_1 in atemporary mode, with a default value “presentation not restricted”.Originating Identification Presentation service is provisioned for UE_2.Test Case 2.3.4 –Terminating Identification Presentation subscribedPriority: Mandatory TCObjective: Verify UE behaviour when terminating identification presentation is subscribed.Reference: TS 24.608UE_1 Setup: -UE_2 Setup: -NW Setup: Terminating Identification Presentation service is provisioned for UE_1. Precondition: 1.UE_1 and UE_2 are connected and registered to an IMS network.2.UE_1 and UE_2 support speech.Procedure: 1.Perform a voice call according the test case 2.2.1.Miscellaneous: -Pass Criteria: The voice call is established and identity information of UE_2 is present atUE_1.Test Case 2.3.4A –Terminating Identification Presentation not subscribedPriority: Mandatory TCObjective: Verify UE behaviour when terminating identification presentation is notsubscribed.Reference: TS 24.608UE_1 Setup: -UE_2 Setup: -NW Setup: Terminating Identification Presentation service is not provisioned for UE_1. Precondition: 1.UE_1 and UE_2 are connected and registered to an IMS network.2.UE_1 and UE_2 support speech.Procedure: 1.Perform a voice call according the test case 2.2.1.Miscellaneous: -Pass Criteria: The voice call is established and identity information of UE_2 is not presentat UE_1.Test Case 2.3.5 –Terminating Identification RestrictionPriority: Mandatory TCObjective: Verify terminating identification restriction.Reference: TS 24.608UE_1 Setup: -UE_2 Setup: -NW Setup: Terminating Identification Restriction service is provisioned for UE_1 in atemporary mode, with a default value “presentation not restricted”.Terminating Identification Presentation service is provisioned for UE_2. Precondition: 1.UE_1 and UE_2 are connected and registered to an IMS network.2.UE_1 and UE_2 support speech.Procedure: 1.UE_2: dial a voice call to UE_1.2.UE_1: answer call with terminating identification restriction. Miscellaneous: Messages SequenceTest Case 2.3.6 –Communication Forwarding unconditionalPriority: Mandatory TCObjective: Verify communication forwarding unconditional.Reference: TS 24.604UE_1 Setup: Configured with the XCAP Root URI representing the root resource at the XCAP server holding the user's XML document with supplementary serviceconfiguration.UE_2 Setup: -UE_3 Setup: -NW Setup: -Precondition: 1.UE_1, UE_2 and UE_3 are connected and registered to an IMS network.2.UE_1, UE_2 and UE_3 support speech.Procedure: 1.UE_1: activate communication forwarding unconditional to UE_3.2.UE_2: dial a voice call to UE_1.3.UE_3: answer call.4.Speech.5.UE_2 hangs up.6.UE_1: deactivate communication forwarding.7.Perform a voice call according test case 2.2.2.Miscellaneous: -Pass Criteria: 1.The voice call is established between UE_2 and UE_3.2.The voice call is established between UE_2 and UE_1.Order: 1,2Test Case 2.3.7 –Originating – Communication HOLDb=RR: (bandwidth-value > 0)a=sendonly[o] INVITE or UPDATE (Request-URI) SIP/2.0Content-Type: application/sdpContent-Length: (value)m=audio (transport port) RTP/AVP (fmt)b=RS:0b=RR:0a=sendrecv or not presentPass Criteria: 1.Speech is not present in UE_2.2.Successful speech between UE_1 and UE_2.Order: 1,2The message sequence, order and header/parameters in the miscellaneoussection of this test case shall be verified.Test Case 2.3.8 –Terminating – Communication HOLDPriority: Mandatory TCObjective: Verify terminating communication hold.Reference TS 24.610UE_1 Setup: -UE_2 Setup: -NW Setup: -Precondition: 1.UE_1 and UE_2 are connected and registered to an IMS network.2.UE_1 and UE_2 support speech.Procedure: 1.Perform a voice call according the test case 2.2.1.2.UE_2: put call on hold.3.Speech.4.UE_2: resume call.5.Speech.Miscellaneous: Messages SequenceTest Case 2.3.9 –Communication Forwarding on no Reply: limited ringing duration Priority: Mandatory TCObjective: Verify communication forwarding on no Reply: limited ringing duration. Reference: TS 24.604UE_1 Setup: Configured with the XCAP Root URI representing the root resource at the XCAP server holding the user's XML document with supplementary serviceconfiguration.UE_2 Setup: -UE_3 Setup: -NW Setup: NoReplyTimerPrecondition: 1.UE_1, UE_2 and UE_3 are connected and registered to an IMS network.2.UE_1, UE_2 and UE_3 support speech.Procedure: 1.UE_1: activate communication forwarding on no reply to UE_3.2.UE_2: dial a voice call to UE_1.3.Wait for the NoReplyTimer to expire.4.UE_3: answer call.5.Speech.6.UE_2: hang up.7.UE_1: deactivate communication forwarding.8.Perform a voice call according test case 2.2.2.Miscellaneous: -Pass Criteria: 1.The voice call is established between UE_2 and UE_3.2.The voice call is established between UE_2 and UE_1.Order: 1,2Test Case 2.3.10 –Originating – Creating a conferencePriority: Mandatory TCObjective: Verify that a conference can be createdReference TS 24.147UE_1 Setup: A Conference Factory URI shall be configuredUE_2 Setup: -UE_3 Setup: -NW Setup: The IMS core network shall support the conferencing procedures defined in 3GPP TS 24.605 with the clarifications in GSMA PRD IR.92 specification. Precondition: 1.UE_1, UE_2 and UE_3 are connected and registered to the current IMSnetwork.2.UE_1, UE_2 and UE_3 support speech.Procedure: 1.Perform a voice call according to TC 2.2.12.UE_1: Put UE_2 on hold.3.UE_1: Dial a voice call to UE_3.4.UE_3: Answer call5.UE_1: Create a conference6.UE_1: Invite UE_2 to the conference, by sending REFER to the conferencefocus7.UE_2: Accept the invitation.8.UE_1: Invite UE_3 to the conference9.UE_3: Accept the invitationa=maxptime:240[q] INVITE (Request-URI to conference factory) SIP/2.0Contact: +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtelAccept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"Content-Type: application/sdpContent-Length: (value)m=audio (transport port) RTP/AVP (fmt)b=AS: (bandwidth-value)b=RS: (bandwidth-value)b=RR: (bandwidth-value)a=rtpmap:(payload type) AMR/8000/1a=fmtp:(format) mode-change-capability=2; max-red=220a=ptime:20a=maxptime:240[s] REFER (Request-URI) SIP/2.0Refer-To: <addr-spec?Replaces=(dialog-id)>Referred-By: <addr-spec>[t] REFER (Request-URI) SIP/2.0Refer-To: <addr-spec?Replaces=(dialog-id)>Referred-By: <addr-spec>Pass Criteria: A conference session is established between UE_1 and the conference device.Successful speech between UE_1, UE_2 and UE_3The message sequence, order and header/parameters in the miscellaneoussection of this test case shall be verified.Test Case 2.3.11 –Terminating – Joining a conference after receiving an invitation Priority: Mandatory TCObjective: Verify that a new user can be invited to an ongoing conference.Reference 3GPP TS 24.147UE_1 Setup: -UE_2 Setup: -NW Setup: The IMS core network shall support the conferencing procedures defined in 3GPP TS 24.605 with the clarifications in the GSMA PRD IR.92 specification. Precondition: 1.UE_1 and UE_2 are connected and registered to the current IMS network.2.UE_1 and UE_2 are voice capable.Procedure: 1.UE_2: Perform a voice call to UE_3 according TC 2.2.1 (UE_2 act as UE_1, UE_3 act as UE_2)2.UE_2: Put UE_3 on hold.Test Case 2.3.12 –Communication forwarding on busyPriority: Mandatory TCObjective: Verify communication forwarding on busyReference TS 24.604UE_1 Setup: Configured with the XCAP Root URI representing the root resource at the XCAP server holding the user's XML document with supplementary serviceconfiguration.UE_2 Setup: -UE_3 Setup: -UE_4 Setup: -NW Setup: -Precondition: 1.UE_1, UE_2, UE_3 and UE_4 are connected and registered to the currentIMS network.2.UE_1, UE_2, UE_3 and UE_4 support speech.Procedure: 1.UE_1: activate communication forwarding on busy to UE_3.2.UE_1: Perform a voice call to UE_2 according test case 2.2.1.3.UE_4: while UE_1 is still engaged in the voice call of the previous bullet,dial a voice call to UE_1.4.UE_3: answer call from UE_4 that was diverted from UE_1.5.Speech6.UE_3 hangs up7.UE_1: deactivate communication forwarding.Miscellaneous: -Pass Criteria: The voice call is established between UE_1 and UE_2.The voice call is established between UE_4 and UE_3.Test Case 2.3.14 –Barring of All Incoming CallsPriority: Mandatory TCObjective: Verify Barring of all incoming callsReference: TS 24.173, TS 24.611, TS 24.628 and TS 24.229UE_1 Setup: Configured with the XCAP Root URI representing the root resource at theXCAP server holding the user's XML document with supplementary serviceconfigurationUE_2 Setup: -NW Setup: -Precondition: 1.UE_1 and UE_2 are connected and registered to an IMS network.2.UE_1 and UE_2 support speech.Procedure: 1.UE_1 activate Incoming Call Barring service2.UE_2 perform a voice call towards UE_1.3.UE_1 deactivate Incoming Call Barring service4.UE_2 perform a voice call towards UE_1 according to the test case2.2.2.Miscellaneous: -Pass Criteria: After activating Incoming Call Barring service, the voice call is not established between UE_1 and UE_2.After de-activating Incoming Call Barring service, the voice call isestablished between UE_1 and UE_2.Test Case 2.3.15 –Barring of All Outgoing CallsPriority: Mandatory TCObjective: Verify Barring of all outgoing callsReference: TS 24.173, TS 24.611, TS 24.628 and TS 24.229UE_1 Setup: Configured with the XCAP Root URI representing the root resource at theXCAP server holding the user's XML document with supplementary serviceconfiguration.UE_2 Setup: -NW Setup: -Precondition: 1.UE_1 and UE_2 are connected and registered to an IMS network.2.UE_1 and UE_2 support speech.Procedure: 1.UE_1: activate Outgoing Call Barring service2.UE_1: perform a voice call towards UE_2.3.UE_1: deactivate Outgoing Call Barring service4.UE_1: perform a voice call towards UE_2 according to the test case2.2.1.Miscellaneous: Messages Sequence for procedure 2Test Case 2.3.16 –Barring of Outgoing International CallsPriority: Mandatory TCObjective: Verify Barring of outgoing international callsReference: TS 24.173, TS 24.611, TS 24.628 and TS 24.229UE_1 Setup: Configured with the XCAP Root URI representing the root resource at the XCAP server holding the user's XML document with supplementary serviceconfiguration.UE_2 Setup: -NW Setup: -Precondition: 1.UE_1 is connected and registered to an IMS network.2.UE_2 is connected and registered to other IMS network which is locatedin different country.3.UE_1 and UE_2 support speech.Procedure: 1.UE_1: activate Outgoing International Call Barring service2.UE_1: perform a voice call towards UE_2.3.UE_1: deactivate Outgoing International Call Barring service4.UE_1: perform a voice call towards UE_2.Miscellaneous: Messages Sequence for procedure 2Test Case 2.3.17 –Barring of Incoming Calls when RoamingPriority: Mandatory TCObjective: Verify Barring of incoming calls when roamingReference: TS 24.173, TS 24.611, TS 24.628 and TS 24.229UE_1 Setup: Configured with the XCAP Root URI representing the root resource at the XCAP server holding the user's XML document with supplementary serviceconfigurationUE_2 Setup: -NW Setup: -Precondition: 1.UE_1 is connected and registered via other IMS network than home IMSnetwork.2.UE_2 is connected and registered to IMS network. UE_1 and UE_2support speech.Procedure: 1.UE_1: activate Incoming Call Barring service when roaming.2.UE_2: perform a voice call towards UE_1.3.UE_1: deactivate Incoming Call Barring service when roaming.4.UE_2: perform a voice call towards UE_1 according to the test case2.2.2.Miscellaneous: -Pass Criteria: After activating Incoming Call Barring service when roaming, the voice callis not established between UE_1 and UE_2After de-activating Incoming Call Barring service when roaming, the voicecall is established between UE_1 and UE_2.The message sequence, order and header/parameters in the miscellaneoussection of this test case shall be verified。

autoitlibrary用法AutoItLibrary用法详解1. 概述AutoItLibrary是一种用于自动化测试的关键字驱动的测试工具，基于AutoIt编写而成。

它提供了丰富的关键字，可以与Robot Framework结合使用，方便编写和执行自动化测试脚本。

2. 安装和配置安装AutoItLibrary之前，需要确保你的系统已经安装了AutoIt并配置好了相关环境变量。

AutoIt安装和配置1.前往AutoIt官网下载最新的AutoIt安装包（2.执行安装包，按照向导进行安装。

3.配置环境变量，将AutoIt的安装目录添加到系统的Path变量中。

安装AutoItLibrary1.使用pip安装AutoItLibrary：pip installrobotframework-autoitlibrary2.确认安装成功执行命令robot --version，如果能够正确显示版本号，则表示安装成功。

3. 关键字的使用AutoItLibrary提供了一系列的关键字，用于操作Windows桌面应用程序。

下面是一些常用的关键字及其用法示例：Run AutoIt Script执行AutoIt脚本文件。

示例：*** Test Cases ***Run AutoIt Script ExampleRun AutoIt Script path/to/Win Exist检查指定的窗口是否存在。

示例：*** Test Cases ***Check Window Existence Example${exist} Win Exist CalculatorShould Be True ${exist} Window 'Calculator' ex ists.Win Wait等待指定的窗口出现。

示例：*** Test Cases ***Wait For Window ExampleWin Wait CalculatorWin Close关闭指定窗口。

C语⾔单元测试对于开发来说，单元测试必不可少，对于开发来说，JUnit⾮常好，对于C++开发，也有CPPUnit可供使⽤，⽽对于传统的开发，就没有很好的⼯具可供使⽤，可以找到的有这么⼏个⼯具：1. CuTest -- CuTest(Cute Test)是⼀个⾮常简单的C语⾔单元测试⼯具。

在使⽤它的时候，只需要包含两个⽂件“CuTest.c CuTest.h”，然后就可以写测试⽤例，进⾏测试了。

它对⽤例⼏乎没有管理功能，报表输出也⾮常简单，可以⽤来试验单元测试的基本想法。

2. CUnit -- CUnit是⼀个轻型的C语⾔单元测试框架。

它提供了设计、管理、运⾏测试⽤例的功能。

它的报表功能⽐较强⼤，但是⽐较⿇烦，更适合于较⼤⼀些的项⽬。

3. Check -- 不错的⼯具。

在这⾥（）给出了各种软件测试⼯具，没事可以研究⼀下。

CUnitCUnit基本Test Registry|------------------------------| |Suite '1' . . . . Suite 'N'| |--------------- ---------------| | | |Test '11' ... Test '1M' Test 'N1' ... Test 'NM'⼀次测试（Test Registry）可以运⾏多个测试包（Test Suite），⽽每个测试包可以包括多个测试⽤例（Test Case），每个测试⽤例⼜包含⼀个或者多个断⾔类的语句。

具体到程序的结构上，⼀次测试下辖多个Test Suite，它对应于程序中各个独⽴模块；⼀个Suite管理多个Test Case，它对应于模块内部函数实现。

每个Suite可以含有setup和teardown函数，分别在执⾏suite的前后调⽤。

CUnit测试模式CUnit使⽤四种不同的接⼝，供⽤户来运⾏测试和汇报测试结果：1. ⾃动输出到XML⽂件，⾮交互式2. 基本扩展编程⽅式，⾮交互式3. 控制台⽅式，交互式4. Curses图形接⼝，交互式注意1和2是⾮交互式的,4只能在Unix下使⽤，常⽤console，⽽且console是可以⼈机交互的。

软件测试常用术语中、英文概述Acceptance Testing－－验收测试一般由用户客户进行的确认是否可以接受一个产品的验证性测试。

actual outcome－－实际结果被测对象在特定的条件下实际产生的结果。

Ad Hoc Testing－－随机测试测试人员通过随机的尝试系统的功能，试图使系统中断。

algorithm－－算法（1）一个定义好的有限规则集，用于在有限步骤内解决一个问题；（2）执行一个特定任务的任何操作序列。

algorithm analysis－－算法分析一个软件的验证确认任务，用于保证选择的算法是正确的、合适的和稳定的，并且满足所有精确性、规模和时间方面的要求。

Alpha Testing－－Alpha测试由选定的用户进行的产品早期性测试。

这个测试一般在可控制的环境下进行的。

analysis－－分析（1）分解到一些原子部分或基本原则，以便确定整体的特性；（2）一个推理的过程，显示一个特定的结果是假设前提的结果；（3）一个问题的方法研究，并且问题被分解为一些小的相关单元作进一步详细研究。

anomaly－－异常在文档或软件操作中观察到的任何与期望违背的结果。

application software－－应用软件满足特定需要的软件。

architecture－－构架一个系统或组件的组织结构。

ASQ－－自动化软件质量（Automated Software Quality）使用软件工具来提高软件的质量。

assertion－－断言指定一个程序必须已经存在的状态的一个逻辑表达式，或者一组程序变量在程序执行期间的某个点上必须满足的条件。

assertion checking－－断言检查用户在程序中嵌入的断言的检查。

audit－－审计一个或一组工作产品的独立检查以评价与规格、标准、契约或其它准则的符合程度。

audit trail－－审计跟踪系统审计活动的一个时间记录。

Automated Testing－－自动化测试使用自动化测试工具来进行测试，这类测试一般不需要人干预，通常在GUI、性能等测试中用得较多。

实验室检测报告常见问题与典型案例分析张翼舒;胡湘洪;张铮;王春川;李江燕【摘要】This paper summarizes the common problems in test reports issued by domestic third-party testing labs, lists the typical cases for analysis, and points out that the labs should attach great importance to the quality of the test report, and focus on the completeness, accuracy, scientificity and normalization for the contents in reports, in order to ensure reports without omissions and errors, trustworthy and reliable.%归纳了国内第三方检测实验室出具的检测报告中常见的问题，列举了典型案例进行分析，指出实验室应重视检测报告质量，重点注意报告内容的完整性、准确性、科学性和规范性，确保报告无误无漏、可信可靠。

【期刊名称】《环境技术》【年(卷),期】2016(034)003【总页数】5页(P40-43,47)【关键词】检测报告;常见问题;典型案例【作者】张翼舒;胡湘洪;张铮;王春川;李江燕【作者单位】工业和信息化部电子第五研究所，广州 510610;工业和信息化部电子第五研究所，广州 510610; 广东省电子信息产品可靠性技术重点实验室，广州510610;工业和信息化部电子第五研究所，广州 510610; 广东省电子信息产品可靠性与环境工程技术研究开发中心，广州 510610;工业和信息化部电子第五研究所，广州 510610;工业和信息化部电子第五研究所，广州 510610; 广东省电子信息产品可靠性技术重点实验室，广州 510610【正文语种】中文【中图分类】F406.3检测报告是实验室检测工作的终端产品，是所检产品合格与否的判决书，也是检测工作质量的终极体现。

APPENDIX BBattery Life Measurement Test ResultsGeneralRef.no Freq. Band Currentvalues/mAhCalc.oper.Times /hh:mmThroughputMbComments8509001800190085090018001900Stand-by Test SceneriosScenarios3.1GSM Idle Time3.2GSM/GPRS Idle TimeSW version Nominal Voltage End of life voltage Battery TypeBattery capacity (mAh)Model Name Marketing Name HW version Cable/Stereo Headset usedBluetooth Headset usedI II IV V VI VIII IX 8509001800190085090018001900I II IV V VI VIII IX measured band PLEASE, add the product supported and measured bands in column Dmeasured band PLEASE, add the product supported and measured bands in column Dmeasured band PLEASE, add the product supported and measured bands in column Dmeasured bandPLEASE, add the product supported and measured bands in column DIdle Time3.43.3WCMDA GSM/WCMDA Idle TimeIdle Time3.6WCMDA/GSM-GPRS Dual ModeIdle Time3.5GSM-GPRS/WCMDA Dual ModeE-UTRA FDD Idle Timemeasured band PLEASE, add the product supported and measured bands in column Dmeasured band PLEASE, add the product supported and measured bands in column Dmeasured band PLEASE, add the product supported and measured bands in column Dmeasured band PLEASE, add the product supported and measured bands in column Dmeasured band PLEASE, add the product supported and measured bands in column Dmeasured band PLEASE, add the product supported and measured bands in column Dmeasured band PLEASE, add the product supported and measured bands in column Dmeasured band PLEASE, add the product supported and measured bands in column D85090018001900850Test Only, when both WiFi frequency bands are supported900Test Only, when both WiFi frequency bands are supported 1800Test Only, when both WiFi frequency bands are supported 1900Test Only, when both WiFi frequency bands are supported85090018001900850900GSM,Wi-Fi 5 GHZ enabled,no AP3.78.2Idle Time WMM/UAPSD offIdle TimeIdle TimeGSM,Wi-Fi 2.4 GHZ enabled,device connected toAPIdle Time WMM/UAPSD onFDDE-UTRA TDD Idle TimeGSM,Wi-Fi 2.4 GHZ enabled,no AP3.8.1180********Test Only, when both WiFi frequency bands are supported 900Test Only, when both WiFi frequency bands are supported 1800Test Only, when both WiFi frequency bands are supported 1900Test Only, when both WiFi frequency bands are supported850Test Only, when both WiFi frequency bands are supported 900Test Only, when both WiFi frequency bands are supported 1800Test Only, when both WiFi frequency bands are supported 1900Test Only, when both WiFi frequency bands are supportedGAN over WLAN (2.4GHZ),GSM coverage available Idle Time 900GAN over WLAN (5 GHZ),GSM coverage availableIdle Time 900Test Only, when both WiFi frequency bands are supportedIII IV V VI VIII IX ITest Only, when both WiFi frequency bands are supportedII Test Only, when both WiFi frequency bands are supported IV Test Only, when both WiFi frequency bands are supported V Test Only, when both WiFi frequency bands are supported VITest Only, when both WiFi frequency bands are supported3.8.3Idle TimeWCDMA,Wi-Fi 5 GHZ enabled,no APGSM,Wi-Fi 5 GHZ enabled,device connected toAPIdle Time WMM/UAPSD onIdle Time WMM/UAPSD off3.8.2Idle Time WMM/UAPSD offWi-Fi 2.4 GHZ enabled,device connected toAPIdle TimeWCDMA,Wi-Fi 2.4 GHZ enabled,no AP3.8.4VIII Test Only, when both WiFi frequency bands are supported IX Test Only, when both WiFi frequency bands are supportedI II IV V VI VIII IX I II IV V VI VIII IX I Test Only, when both WiFi frequency bands are supported II Test Only, when both WiFi frequency bands are supported IV Test Only, when both WiFi frequency bands are supported V Test Only, when both WiFi frequency bands are supported VI Test Only, when both WiFi frequency bands are supported VIII Test Only, when both WiFi frequency bands are supported IX Test Only, when both WiFi frequency bands are supported I Test Only, when both WiFi frequency bands are supported II Test Only, when both WiFi frequency bands are supported IV Test Only, when both WiFi frequency bands are supported V Test Only, when both WiFi frequency bands are supported VI Test Only, when both WiFi frequency bands are supported VIII Test Only, when both WiFi frequency bands are supported IX Test Only, when both WiFi frequency bands are supported measured bandPLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedWCDMA,Wi-Fi 5 GHZ enabled,device connected toAPIdle Time WMM/UAPSD onIdle Time WMM/UAPSD off3.8.5Idle Time WMM/UAPSD onIdle Time WMM/UAPSD offWi-Fi 5 GHZ enabled,no APWCDMA,Wi-Fi 2.4 GHZ enabled,device connected toAPStandby,Wi-Fi 2.4 GHZ enabled,measured band PLEASE, add the product supported and measured bands in column Dmeasured band PLEASE, add the product supported and measured bands in column Dmeasured band PLEASE, add the product supported and measured bands in column Dmeasured band PLEASE, add the product supported and measured bands in column Dmeasured band PLEASE, add the product supported and measured bands in column Dmeasured band PLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supported measured bandPLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedmeasured bandPLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedmeasured band PLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedmeasured band PLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedmeasured band PLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedmeasured band PLEASE, add the product supported and measured bands in column Dmeasured band PLEASE, add the product supported and measured bands in column Dmeasured band PLEASE, add the product supported and measured bands in column Dmeasured band PLEASE, add the product supported and measured bands in column Dmeasured bandPLEASE, add the product supported and measured bands in column DIdle TimeE-UTRA Standby,Wi-Fi 5 GHZ enabled,no APIdle TimeIdle Time WMM/UAPSD onE-UTRA Standby,Wi-Fi 2.4 GHZ enabled,device connected to3.8.6E-UTRA Standby,Wi-Fi 2.4 GHZ enabled,no APmeasuredband PLEASE, add the product supported and measured bands in column Dmeasuredband PLEASE, add the product supported and measured bands in column Dmeasuredband PLEASE, add the product supported and measured bands in column Dmeasuredband PLEASE, add the product supported and measured bands in column Dmeasuredband PLEASE, add the product supported and measured bands in column Dmeasuredband PLEASE, add the product supported and measured bands in column Dmeasuredband PLEASE, add the product supported and measured bands in column Dmeasuredband PLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedmeasuredband PLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedmeasuredband PLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedmeasuredband PLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedmeasuredband PLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedmeasuredband PLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedmeasuredband PLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedmeasuredband PLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedE-UTRA Standby, Wi-Fi 5 GHZenabled,device connected toAPIdle Time WMM/UAPSD on WMM/UAPSD off3.8.7WMM/UAPSD onIdle TimeWMM/UAPSD off E-UTRAStandby,Wi-Fi 2.4 GHZenabled,deviceconnected toAPmeasured bandPLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedmeasured band PLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedmeasured band PLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedmeasured bandPLEASE, add the product supported and measured bands in column D. Test Only, when both WiFi frequency bands are supportedRef.noFreq. Band Currentvalues/mAhCalc.oper.Times /hh:mmThroughputMbComments850900180019008509001800190085090018001900device connected toAPIdle Time WMM/UAPSD offTalk Time Test SceneriosScenariosGSM4.1Talk time at maxTX power4.1GSMGSMTalk time at min TXpowerTalk time at PCL 1or 7 (band dependent)4.1I IIIV V VI VIIIIX I II IV V VI VIII IX 8509001800190085090018001900I II IV V VI VIII IX I II4.2WCDMATalk Time Tx level 10dBmTalk Time Power DistributionTx level4.3WLAN with GSM CoverageTalk Time WMM/UAPSD onTalk Time WMM/UAPSD off4.3WMM/UAPSD offWLAN with WCDMA CoverageTalk Time WMM/UAPSD onIV V VI VIII IX 4.3.1VoIP over WLAN No CS Talk Time-E-UTRA FDD/TDD File Transfer File Downloadmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band10 minPLEASE, add the product supported and measured bands in column DFile DownloadE-UTRA TDD File Download5.3E-UTRA FDD Talk Time WMM/UAPSD offWCDMA Coverageband10 minbands in column DFile Uploadmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band10 minPLEASE, add the product supported and measured bands in column DFile Up- & Downloadmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band10 minPLEASE, add the product supported and measured bands in column DE-UTRA TDD File Upload5.4E-UTRA FDD File Uploadband10 min bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band 10 min PLEASE, add the product supported and measured bands in column Dmeasured band10 minPLEASE, add the product supported and measured bands in column DApplication Test ScenariosBrowsingRef.no Freq. Band Currentvalues/mAhTest Executio n Time (Calc.oper.Times )Total DataTransferred(ThroughputMb)CommentsGSM/GPRS 5 minNote: Add used Freq. Band WCDMA5 minNote: Add used Freq. Band E-UTRA FDDFile Up & Download5.5E-UTRA TDDFile Up & DownloadScenarios6.1HTMLBrowsingGSM/GPRS 5 minNote: Add used Freq. BandWCDMA 5 min Note: Add used Freq. Band StreamingRef.no Freq. Band Currentvalues/mAhTestExecution Time(Calc.oper.Times )Total DataTransferred(ThroughputMb)CommentsWCMDA10 min Note: Add used Freq. BandHSDPA10 min Note: Add used Freq. BandE-UTRA10 min Note: Add used Freq. BandWCDMA10 min Note: Add used Freq. BandHSDPA10 min Note: Add used Freq. BandE-UTRA10 min Note: Add used Freq. Band ApplicationsRef.no Freq. Band Currentvalues/mAhTestExecution Time/Calc.oper.Times )ThroughputMbComments8.1Music Playback Used RAT (UTRAor EUTRA)5 minAdd used RAT and Freq.Band GSM 5 minWCDMA 5 min7.1Video Streaming7.2AudioStreamingVideo PlaybackScenariosScenarios6.2HTML Browsing with Full WebBrowser8.28.3Camera Operation Airplane Mode20 pics with 30s interval GSM 10 min WCDMA10 minVideo TelephonyRef.no Freq. Band Currentvalues/mAhTest Execution Time/Calc.oper.Times )ThroughputMbComments9.1Video TelephonyWCDMA?10 minBluetoothRef.no Freq. Band Currentvalues/mAhCalc.oper.Times /hh:mmThroughputMbComments85090018001900I II IVV VI VIII IXScenarios10.28.4GSMVideo RecordingBT Headset Talk TimeWCDMAScenarios10.3BT Headset Music PlayerUsed RAT (UTRAor EUTRA)5 minAdd used RAT and Freq.Band85090018001900I II IV V VI VIII IX 85090018001900I II IV V VI VIII IXFTP Download10.6GSMWCDMA10.5Device in BT discovery mode – IdleTimeGSMWCDMABT data transfer -Device in idlemodeRef.no Freq. Band Currentvalues/mAhTest Execution Time/Calc.oper.Times )ThroughputMbCommentsI10 min II 10 min IV 10 min V 10 min VI 10 min VIII 10 min IX 10 min I 10 min II10 min IV 10 min V 10 min VI 10 min VIII 10 min IX10 min 85010 min 90010 min 180010 min 190010 min 85010 min 90010 min 180010 min 190010 min WMM/UAPSD on -10 min WMM/UAPSD off-10 minNote (*) N/A if the charging cannot be disabled by an appropriate SW tool.11.1WLAN FTP Download11.311.2WCDMAFTP download viaBluetooth connectionScenariosFTP download via Cable connection(*)FTP download viaBluetooth connectionGSMFTP download via Cable connection(*)USB Data ModemRef.no Freq. Band Currentvalues/mAhCalc.oper.Times /hh:mmThroughputMbCommentsWCDMA FTPDownload?10 minGPRS FTPDownload?10 min GPS TrackingRef.no Freq. Band Currentvalues/mAhTestExecution Time/Calc.oper.Times )ThroughputMbComments12.1GPS Tracking Option 1: Satellitesimulator availableGSM10 min12.2GPS Tracking Option 2: Satellitesimulator notavailableGSM10 min11USB Data CardScenariosScenarios。