Test Plan.doc

XX Test PlanXX 测试计划请输入密级XX Technologies Co. Ltd.XX有限公司Product version 产品版本Confidentiality level密级请输入密级Project ID 项目IDTotal pages：共7页XX Test PlanXX 测试计划Prepared by 拟制Date日期yyyy-mm-ddReviewed by 评审人Date日期yyyy-mm-ddApproved by批准Date日期yyyy-mm-ddAuthorized by签发Date日期yyyy-mm-ddXX Technologies Co., Ltd. XX有限公司All rights reserved版权所有 侵权必究Catalog目 录1Introduction 简介31.1Purpose 目的31.2Scope 范围32Test Plan 测试计划32.1Resource Requirements 资源需求32.1.1Software Requirements 软件需求31.1.2Hardware Requirements 硬件需求31.1.2Other Materials 其它设备41.1.3Personnel Requirements 人员需求41.2Process Criteria 过程条件51.2.1Entry Criteria 启动条件51.2.2Exit Criteria 结束条件51.2.3Suspend Criteria 挂起条件51.2.4Resume Criteria 恢复条件51.3Schedule 进度计划51.4Test Topologies 测试组网图51.5Orientation/Training Plan 导向培训计划52Test Cases 测试用例61Deliverables 工作交付件71 Introduction 简介1.1 Purpose 目的This section shall state the purpose of the document. It shall also specify the intended audience. 这部分要描述文档的目的。应该指明读者。1.2 Scope 范围This section shall address areas which this document included and that are specifically excluded. Also the Modules/Sub projects/ projects covered should be specified in this Test Plan定义文档适用和不适用的范围。同时应该描述计划所覆盖的的模块、子项目、项目2 Test Plan 测试计划2.1 Resource Requirements 资源需求2.1.1 Software Requirements 软件需求2.1.1.1 Software Requirements Table软件需求表1 Software Requirements Table 软件需求表Resource资源Description描述Qty数量1.1.1.1 Software Requirements Description 软件需求说明This paragraph shall identify by name, number, and version for each software items, including operating systems, databases, compilers, preprocessors, test tools, etc., that is required to perform the planned testing activities at the test site. It shall identify the purpose and applicable method of each items.本节描述测试所需要的支撑软件的名称、数量、版本，例如：操作系统、数据库、编译器、预处理器、测试工具等等。应描述每一项的用途以及应用范围。1.1.2 Hardware Requirements 硬件需求1.1.2.1 Hardware Requirements Table硬件需求表1 Hardware Requirements Table2 硬件需求表Resource资源Description描述Qty数量1.1.1.1 Hardware Requirements Description 硬件需求说明This paragraph shall identify by name, number, and version for each hardware items, including the facilities, computers, interfacing equipment, printers, and firmware items that will be used in the software test environment at the test site, etc., that is required to perform the planned testing activities at the test site. It shall identify the purpose and applicable method of each items.本节描述测试所需要的硬件环境的名称、数量、版本，例如：硬件设备、计算机、打印机、接口设备、测试仪器、以及各种软件运行所需的硬件设备等等。应描述每一项的用途以及应用范围。1.1.2 Other Materials 其它设备This paragraph shall describe any other materials, including manual, operating instruction, related industrial standards that are necessary to perform the planned testing activities at the test site. It shall identify the purpose and applicable method of each items. It can be ignored if it is not necessary.本节描述测试中所需用到的其它材料，如：用户手册、操作指引、相关工业标准等等。应描述每一项的用途及应用范围。如果没有可忽略此节。1.1.3 Personnel Requirements 人员需求1.1.3.1 Personnel Requirements Table 人员需求表1 Table 3 Personnel Requirements Table 人员需求表Resource资源Skill Level技能级别Qty数量Date到位时间Duration工作期间1.1.1.1 Personnel Description 人员说明This paragraph shall describe other important information about the personnel, including special requirements, key skill, area experience, support from outside, etc. It shall describe other information such as multishift operation etc. 本节表述人员相关的其它信息，包括：特殊要求、关键技能、领域经验、外部支持等等。如果需要，还应描述人员相关的其它信息，如轮班制度等等。1.2 Process Criteria 过程条件1.2.1 Entry Criteria 启动条件This paragraph identifies the start criteria of test performing.本节测试执行活动开始所应具备的条件。1.2.2 Exit Criteria 结束条件This paragraph identifies the exit criteria of test performing.本节测试结束的条件或标准。1.2.3 Suspend Criteria 挂起条件Testing process shall be suspended when it cant continue for various reasons. This paragraph shall identify each criteria that cause the suspending, including dependence objects not available, entering a certain risk critical areas, or some management decision-making, etc.测试过程无法继续时应挂起测试，本节描述会导致测试挂起的各种因素。这些因素可能包括：测试依赖因素不具备、进入某项风险临界区、管理决策等等。1.2.4 Resume Criteria 恢复条件This paragraph shall identify each criteria that can resume the testing, corresponding to suspend criteria.本节描述测试挂起后恢复测试的条件，与挂起条件相对应。1.3 Schedule 进度计划Provide the Link to the schedule files.给出到进度文件的链接。1.4 Test Topologies 测试组网图Provide the topology diagram for the particular type of testing and identify the related applicable area.为特定的测试活动准备相应的组网图，注明组网应用范围。1.5 Orientation/Training Plan 导向培训计划This paragraph shall describe any orientation and training to be given before and during the testing. This training may include user instruction, operator instruction, maintenance and control group instruction, and orientation briefings to staff personnel. If extensive training is anticipated, a separate plan may be documented in PPL and referenced here.本段描述测试前或测试中需要进行的指导、培训工作。这些培训可以包括用户指引、操作指引、维护控制组指引，对成员的指导简报。如果需要提前进行大规模培训，将培训计划作为项目计划一个独立的部分，并在此处引用。2 Test Cases 测试用例Group the test cases according to the type of requirement e.g. performance, Interface etc. or according to Module Name, Feature Name etc.将测试用例按照需求类型（例如性能、接口），或者模块名、功能名等组织在一起。Test cases shall be written following the format and ID rules defined in Test Strategy.测试用例的格式应符合测试策略中对测试用例格式和编号规则的要求。For example:例如：Test Case ID测试用例编号Test cases ID shall follow the ID rules defined in Test strategy. For example, Project ID-UT(IT,ST)-nnn. 测试用例的编号应符合测试策略中对编号规则的要求。例如，“项目编码 -UT（或IT，ST）-nnn”。Test Criticality重要级别Specify High/Medium/Low.描述测试用例的重要级别：高/中/低.High - All the requirements classified as Mandatory高需求被定义为“强制性的”Medium- All the requirements classified as Required 中需求被定义为“要求的”Low- All the requirements classified as Desired 低需求被定义为“希望的”Test Title测试标题Give the Description of the Test case. It must also include the module/sub module/interface name (if any)给出测试用例的描述，必须包括模块、子模块