XXXX
信息化建设项目-应用软件开发子项目
测试规格说明书
XXXX信息工程有限公司
版权声明
XXXX信息化建设项目—应用软件开发子项目系统及其相关文档的版权归XXXX所有。未经XXXX的书面准许，不得将XXXX信息化建设项目—应用软件开发子项目系统及其相关文档任何部分为任何目的、以任何形式、采用任何手段(电子的或机械的，包括照相复制或录制)，进行复制或扩散。
版权所有，翻制必究。
测试规格说明书
目 录
1编写目的 ························································································································· 2 2测试团队构成 ················································································································· 2 2.1职责 ······················································································································ 2 2.2角色划分 ·············································································································· 2 3工作流程及规范 ············································································································· 3 3.1计划与设计阶段 ·································································································· 3 3.1.1成立测试团队 ································································································ 3 3.1.2测试预通知 ···································································································· 3 3.1.3召开测试启动会议 ························································································ 3 3.1.4编写测试计划文档 ························································································ 4 3.1.5设计测试用例 ································································································ 4 3.2实施测试阶段 ······································································································ 5 3.2.1实施测试用例 ································································································ 5 3.2.2提交报告 ········································································································ 5 3.2.3回归测试 ········································································································ 6 3.3总结阶段 ·············································································································· 6 3.3.1编写测试报告 ································································································ 6 3.3.2测试工作总结 ································································································ 7 3.3.3测试验收 ········································································································ 7 3.3.4测试归档 ········································································································ 8 3.4缺陷跟踪 ·············································································································· 8 4缺陷类型定义 ················································································································· 9 5测试标准 ······················································································································· 10 6争议处理 ······················································································································· 10 7标准文档 ······················································································································· 10
1
测试规格说明书
1编写目的
本文档是测试团队的日常工作规范，主要侧重测试工作流程的控制，明确软件工程的各阶段测试团队应完成的工作。测试技术和策略等问题不在本文档描述范围内。
2测试团队构成
2.1职责
测试是软件开发过程中的重要组成部分，肩负着如下责任：
在项目的前景、需求文档确立基线前对文档进行测试，从用户体验和测试的角度提出自
己的看法。
编写合理的测试计划，并与项目整体计划有机地整合在一起。 编写覆盖率高的测试用例。
针对测试需求进行相关测试技术的研究。
认真仔细地实施测试工作，并提交测试报告供项目组参考。 进行缺陷跟踪与分析。
2.2角色划分
在人力资源有限的情况下，一个团队成员可能会同时承担多个角色。
2
测试规格说明书
3工作流程及规范
3.1计划与设计阶段
3.1.1成立测试团队
在项目组成立的同时，测试组也将同时成立。团队成立的工作与责任如下：
图表 1
3.1.2测试预通知
在正式测试任务下达前，开发团队应提前一周左右向测试团队下达预通知，告之较为确切的测试日期，提供当前最新的相关资料。测试部门经理可视具体情况决定是否需要调整人力。测试人员可预先熟悉必要的背景资料，协助测试经理编写《测试计划书》初稿。
图表 2
3.1.3召开测试启动会议 3
测试规格说明书
图表 3
3.1.4编写测试计划文档
需求分析文档确立后，测试组需要编写测试计划文档，为后续的测试工作提供直接的指导
图表 4
3.1.5设计测试用例
4
测试规格说明书
在需求分析文档确立基线以后，测试组需要针对项目的测试需求编写测试用例，在实际的测试中，测试用例将是唯一实施标准。在用例的编写过程中，具体的任务和责任人如下：
图表 5
3.2实施测试阶段
3.2.1实施测试用例
实施测试用例将花费测试组绝大部分时间，这些工作都是建立在前期很多计划工作的基础上。
图表 6
3.2.2提交报告
在约定的测试周期完成之后，测试经理需要总结此测试的结果，编写测试报告 5
测试规格说明书
图表7
3.2.3回归测试
在每轮测试结束之后，由测试组重新拷贝修改后的最新版本，进行回归测试。
图表 2
3.3总结阶段
测试工作结束或即将结束时，测试组就要开始着手准备进行总结的工作。 3.3.1编写测试报告
在回归测试结束之后，测试经理将要编写测试总结报告，对测试进行总结，并且提交给全体项目组，为产品的后续工作提供重要的信息支持。
6
测试规格说明书
3.3.2测试工作总结
测试总结工作是在以上的工作全部结束以后，它的目的是评估本次测试工作，总结经验，使下一次的工作做得更好。 3.3.3测试验收
测试验收工作是在以上工作全部结束后，对测试的过程，效果进行验收，宣布测试结束。
7
测试规格说明书
3.3.4测试归档
测试归档是在测试验收结束宣布测试有效，结束测试后，对测试过程中涉及到各种标准文档进行归类，存档。
3.4缺陷跟踪
测试验收结束后，跟踪产品在试运行阶段暴露出来的新缺陷，以及已提交的缺陷是否再次发生。 8
4缺陷类型定义
本规范定义以下五类缺陷：
A类——严重错误，包括：
1. 由于程序所引起的死机,非法退出
2. 死循环
3. 导致数据库发生死锁
4. 数据通讯错误
5 严重的数值计算错误
B类——较严重错误，包括：
1. 功能不符
2. 数据流错误
3. 程序接口错误
4. 轻微的数值计算错误
C类——一般性错误，包括：
1. 界面错误(详细文档)
2. 打印内容、格式错误
3. 简单的输入限制未放在前台进行控制
4. 删除操作未给出提示
D类——较小错误，包括：
1. 辅助说明描述不清楚
9
2. 显示格式不规范
3. 长时间操作未给用户进度提示
4. 提示窗口文字未采用行业术语
5. 可输入区域和只读区域没有明显的区分标志
6. 系统处理未优化
E类——测试建议（非缺陷）
5测试标准
软件测试合格须符合以下标准。
以上比例为错误占总测试模块的比例。
软件产品未经测试合格，不允许投运。
6争议处理
如开发团队对测试结论有争议，由验收组成员会议协调解决。测试团队和开发团队应无条件服从仲裁结果。
7标准文档
1. 《测试计划书》
2. 《测试用例说明书》
3. 《测试报告》
10