5,177
社区成员
发帖
与我相关
我的任务
分享请发表友善的回复…
发表回复
futuredreams 2003-10-27
- 打赏
- 举报
针对每个项目和自己的需要可以选择一些项目，有些不都是必要的，如果需要通过一定标准的，例如CMM的话就去看看详细要求就可以了，国家标准的偶这也有，不过感觉那个...唉~不好说，可能从国外哪里找了一些拼凑而成，（编写的人不要骂我啊），建议需要通过CMM认证的还是不要看了，自己去外国下标准格式比较好，偶这个就是下来的国际规范，不过有些地方比一定都适用。
futuredreams 2003-10-27
- 打赏
- 举报
不一样的，一个对象是被测实体，另外一个是测试过程，zzlh(红)，偶给你回信了~呵呵~
lxf_1976 2003-10-27
- 打赏
- 举报
http://www.uml.org.cn/bzgf/bzgf.asp
有软件工程所有过程的规范文档模板！
有软件工程所有过程的规范文档模板！
Grass2000 2003-10-24
- 打赏
- 举报
这类文档都有国家标准的。
zzlh 2003-10-24
- 打赏
- 举报
请问各位大侠 测试报告跟测试分析报告是同一回事吗
futuredreams 2003-10-24
- 打赏
- 举报
555555，偶也不用QQ，sorry...
zzlh 2003-10-23
- 打赏
- 举报
我也在北京做测试 交个朋友 我的QQ51281536 zzlh_mer@263.net
futuredreams 2003-10-22
- 打赏
- 举报
偶非常乐意，但是偶不用msn的，邮件是futuredreams@sohu.com因为hotmail最近好像不能用了...偶在北京,常联系，呵呵~
yuyanyanlele 2003-10-22
- 打赏
- 举报
鱼儿，我是做测试的，在杭州一家软件公司，可以和你作朋友吗？我的msn:xiaoshuils@hotmail.com
真的很希望和同行的作更多的交流^_^
真的很希望和同行的作更多的交流^_^
futuredreams 2003-10-22
- 打赏
- 举报
不客气啊，呵呵~随时乐意帮忙~zhurongcun。
zhurongcun 2003-10-22
- 打赏
- 举报
哦，是 futuredreams(鱼儿)，太謝謝你了，剛剛搞錯了。
也謝謝樓主貼這個出來啊。
也謝謝樓主貼這個出來啊。
zhurongcun 2003-10-22
- 打赏
- 举报
太謝謝樓主了，真是幫了我的大忙啊，我正急用。哈哈
futuredreams 2003-10-22
- 打赏
- 举报
附录三 测试文档规范
1.0概述
这部分提供对整个测试文档的总体说明。文档描述了测试计划和测试过程。
1.1 目标和对象
测试过程中的所有目标和对象描述。
1.2 范围陈述
描述软件测试的范围。说明测试的功能/外观/行为和任何不被测试的功能/外观/行为。
1.3 主要系统参数
任何会对要测试的软件产生影响的商业的，产品线或者技术参数说明。
2.0 测试计划
描述测试策略和项目管理问题所需要执行的恰当有效的测试。
2.1 测试的软件(SCIís)
需要测试的软件通过名字明确的说明区别。
2.2 测试策略
描述软件测试策略。
2.2.1 单元测试
描述单元测试策略，包括一个指示需要单元测试的构件或者用来选择需要单元测试的构件的标准，不包括测试用例。
2.2.2 集成测试
描述集成测试策略，包括讨论软件功能的集成顺序，不包括测试用例。
2.2.3 确认测试（beta测试）
描述确认测试策略，包括讨论软件功能的确认测试次序，不包括测试用例。
2.2.4 系统测试（High-order测试）
描述系统测试策略，包括产品的系统测试类型，测试负担，不包括测试用例。
2.3 测试资源和人员
专用测试资源（软件）和指定人员及角色ITG描述。
2.4 测试产品
测试工作产生一系列定义的测试策略。
2.5 测试记录
对测试结果的保存和评估机构。
2.6 测试矩阵
描述所有测试活动中的测试矩阵。
2.7 测试工具和测试环境
描述测试环境，包括测试工具，模拟器，专用硬件设备，测试文件和其它使用的资源。
2.8 测试时间安排表
详细描述单元测试，集成测试，确认测试和系统测试的时间安排表。
3.0 测试过程
描述测试过程包括软件测试策略和软件测试用例。
3.1 测试的软件(SCIís)
需要测试的软件通过名字明确的说明区别。
3.2 测试过程
描述软件测试过程。
3.2.1 单元测试用例
对每个（需要测试的）软件构件描述其单元测试过程。
3.2.1.2 构件的根或者（和）驱动
3.2.1.3 构件测试用例
3.2.1.4 构件测试目的
3.2.1.5 构件测试预期结果
3.2.2 集成测试
描述集成测试过程。
3.2.2.1 集成测试过程
3.2.2.2 需要的根或者（和）驱动
3.2.2.3 测试用例和测试目的
3.2.2.4预期结果
3.2.3 确认测试
描述确认测试过程
3.2.3.1 确认测试过程
3.2.3.3预期结果
3.2.3.4 所有确认测试的通过/失败标准
3.2.4 系统测试 (High-order测试)
描述系统测试过程，对下面的每个系统测试的规定，过程，用例，目的，特殊要求和通过/失败标准进行描述。不是每个项目都需要使用所有系统测试方法。
3.2.4.1 恢复测试
3.2.4.2 安全测试
3.2.4.3 压力测试
3.2.4.4 表现测试
3.2.4.5 Alpha/beta测试
3.2.4.6 所有确认测试的通过/失败标准
3.3 测试资源和人员
专用测试资源描述和指定人员，ITG角色指定。
3.4 测试产品
测试工作产生一系列定义的测试策略。
3.5 测试存储记录和日志
对测试结果的保存和评估机构。测试日志用来保留所有测试和它们的结果的年表记录。
就是这个中文版本了，就不发邮件了，因为可能还有别的人需要用，楼上两位不用客气啊，还有其他需要尽管说，翻译的不好多多包涵哦~
1.0概述
这部分提供对整个测试文档的总体说明。文档描述了测试计划和测试过程。
1.1 目标和对象
测试过程中的所有目标和对象描述。
1.2 范围陈述
描述软件测试的范围。说明测试的功能/外观/行为和任何不被测试的功能/外观/行为。
1.3 主要系统参数
任何会对要测试的软件产生影响的商业的，产品线或者技术参数说明。
2.0 测试计划
描述测试策略和项目管理问题所需要执行的恰当有效的测试。
2.1 测试的软件(SCIís)
需要测试的软件通过名字明确的说明区别。
2.2 测试策略
描述软件测试策略。
2.2.1 单元测试
描述单元测试策略，包括一个指示需要单元测试的构件或者用来选择需要单元测试的构件的标准，不包括测试用例。
2.2.2 集成测试
描述集成测试策略，包括讨论软件功能的集成顺序，不包括测试用例。
2.2.3 确认测试（beta测试）
描述确认测试策略，包括讨论软件功能的确认测试次序，不包括测试用例。
2.2.4 系统测试（High-order测试）
描述系统测试策略，包括产品的系统测试类型，测试负担，不包括测试用例。
2.3 测试资源和人员
专用测试资源（软件）和指定人员及角色ITG描述。
2.4 测试产品
测试工作产生一系列定义的测试策略。
2.5 测试记录
对测试结果的保存和评估机构。
2.6 测试矩阵
描述所有测试活动中的测试矩阵。
2.7 测试工具和测试环境
描述测试环境，包括测试工具，模拟器，专用硬件设备，测试文件和其它使用的资源。
2.8 测试时间安排表
详细描述单元测试，集成测试，确认测试和系统测试的时间安排表。
3.0 测试过程
描述测试过程包括软件测试策略和软件测试用例。
3.1 测试的软件(SCIís)
需要测试的软件通过名字明确的说明区别。
3.2 测试过程
描述软件测试过程。
3.2.1 单元测试用例
对每个（需要测试的）软件构件描述其单元测试过程。
3.2.1.2 构件的根或者（和）驱动
3.2.1.3 构件测试用例
3.2.1.4 构件测试目的
3.2.1.5 构件测试预期结果
3.2.2 集成测试
描述集成测试过程。
3.2.2.1 集成测试过程
3.2.2.2 需要的根或者（和）驱动
3.2.2.3 测试用例和测试目的
3.2.2.4预期结果
3.2.3 确认测试
描述确认测试过程
3.2.3.1 确认测试过程
3.2.3.3预期结果
3.2.3.4 所有确认测试的通过/失败标准
3.2.4 系统测试 (High-order测试)
描述系统测试过程，对下面的每个系统测试的规定，过程，用例，目的，特殊要求和通过/失败标准进行描述。不是每个项目都需要使用所有系统测试方法。
3.2.4.1 恢复测试
3.2.4.2 安全测试
3.2.4.3 压力测试
3.2.4.4 表现测试
3.2.4.5 Alpha/beta测试
3.2.4.6 所有确认测试的通过/失败标准
3.3 测试资源和人员
专用测试资源描述和指定人员，ITG角色指定。
3.4 测试产品
测试工作产生一系列定义的测试策略。
3.5 测试存储记录和日志
对测试结果的保存和评估机构。测试日志用来保留所有测试和它们的结果的年表记录。
就是这个中文版本了，就不发邮件了，因为可能还有别的人需要用，楼上两位不用客气啊，还有其他需要尽管说，翻译的不好多多包涵哦~
gaopx 2003-10-21
- 打赏
- 举报
确实是需要中文版，希望楼上能帮忙，谢谢
gpx78@163.com
gaopx_1226@hotmail.com
gpx78@163.com
gaopx_1226@hotmail.com
futuredreams 2003-10-21
- 打赏
- 举报
TEST SPECIFICATION
1.0 Introduction
This section provides an overview of the entire test document. This document describes both the test plan and the test procedure.
1.1 Goals and objectives
Overall goals and objectives of the test process are described.
1.2 Statement of scope
A description of the scope of software testing is developed. Functionality/features/behavior to be tested is noted. In addition any functionality/features/behavior that is not to be tested is also noted.
1.3 Major constraints
Any business, product line or technical constraints that will impact the mannerin which the software is to be tested are noted here.
2.0 Test Plan
This section describes the overall testing strategy and the project management issues that are required to properly execute effective tests.
2.1 Software (SCIís) to be tested
The software to be tested is identified by name. Exclusions are noted explicitly.
2.2 Testing strategy
The overall strategy for software testing is described.
2.2.1 Unit testing
The strategy for unit tested is described. This includes an indication of the components that will undergo unit tests or the criteria to be used to select components for unit test. Test cases are NOT included here.
2.2.2 Integration testing
The integration testing strategy is specified. This section includes a discussion of the order of integration by software function. Test cases are NOT included here.
2.2.3 Validation testing
The validation testing strategy is specified. This section includes a discussion of the order of validation by software function. Test cases are NOT included here.
2.2.4 High-order testing
The high-order testing strategy is specified. This section includes a discussion of the types of high order tests to be conducted, the responsibility for those tests. Test cases are NOT included here.
2.3 Testing resources and staffing
Specialized testing resources are described and staffing is defined. The role of any ITG is also defined.
2.4 Test work products
The work products produced as a consequence of the testing strategy are identified.
2.5 Test record keeping
Mechanisms for storing and evaluating test results are specified.
2.6 Test metrics
A description of all test metrics to be used during the testing activity is noted here.
2.7 Testing tools and environment
A description of the test environment, including tools, simulators, specialized hardware, test files, and other resources is presented here.
2.8 Test schedule
A detailed schedule for unit, integration, and validation testing as well as high order tests is described.
3.0 Test Procedure
This section describes as detailed test procedure including test tactics and test cases for the software.
3.1 Software (SCIís) to be tested
The software to be tested is identified by name. Exclusions are noted explicitly.
3.2 Testing procedure
The overall procedure for software testing is described.
3.2.1 Unit test cases
The procedure for unit testing is described for each software component (that will be unit tested) is presented. This section is repeated for all components i.
3.2.1.2 Stubs and/or drivers for component i
3.2.1.3 Test cases component i
3.2.1.4 Purpose of tests for component i
3.2.1.5 Expected results for component i
3.2.2 Integration testing
The integration testing procedure is specified.
3.2.2.1 Testing procedure for integration
3.2.2.2 Stubs and drivers required
3.2.2.3 Test cases and their purpose
3.2.2.4 Expected results
3.2.3 Validation testing
The validation testing procedure is specified.
3.2.3.1 Testing procedure for validation
3.2.3.3 Expected results
3.2.3.4 Pass/fail criterion for all validation tests
3.2.4 High-order testing (a.k.a. System Testing)
The high-order testing procedure is specified. For each of the high order tests specified below, the test procedure, test cases, purpose, specialized requirements and pass/fail criteria are specified. It should be noted that not all high-order test methods noted in Sections 3.2.4.n will be conducted for every project.
3.2.4.1 Recovery testing
3.2.4.2 Security testing
3.2.4.3 Stress testing
3.2.4.4 Performance testing
3.2.4.5 Alpha/beta testing
3.2.4.6 Pass/fail criterion for all validation tests
3.3 Testing resources and staffing
Specialized testing resources are described and staffing is defined. The role of any ITG is also defined.
3.4 Test work products
The work products produced as a consequence of the testing procedure are identified.
3.5 Test record keeping and test log
Mechanisms for storing and evaluating test results are specified. The test log is used to maintain a chronological record of all tests and their results.
根据具体情况需要修改一些项目，如果需要中文版本，偶这里还有自己翻译的一份。
1.0 Introduction
This section provides an overview of the entire test document. This document describes both the test plan and the test procedure.
1.1 Goals and objectives
Overall goals and objectives of the test process are described.
1.2 Statement of scope
A description of the scope of software testing is developed. Functionality/features/behavior to be tested is noted. In addition any functionality/features/behavior that is not to be tested is also noted.
1.3 Major constraints
Any business, product line or technical constraints that will impact the mannerin which the software is to be tested are noted here.
2.0 Test Plan
This section describes the overall testing strategy and the project management issues that are required to properly execute effective tests.
2.1 Software (SCIís) to be tested
The software to be tested is identified by name. Exclusions are noted explicitly.
2.2 Testing strategy
The overall strategy for software testing is described.
2.2.1 Unit testing
The strategy for unit tested is described. This includes an indication of the components that will undergo unit tests or the criteria to be used to select components for unit test. Test cases are NOT included here.
2.2.2 Integration testing
The integration testing strategy is specified. This section includes a discussion of the order of integration by software function. Test cases are NOT included here.
2.2.3 Validation testing
The validation testing strategy is specified. This section includes a discussion of the order of validation by software function. Test cases are NOT included here.
2.2.4 High-order testing
The high-order testing strategy is specified. This section includes a discussion of the types of high order tests to be conducted, the responsibility for those tests. Test cases are NOT included here.
2.3 Testing resources and staffing
Specialized testing resources are described and staffing is defined. The role of any ITG is also defined.
2.4 Test work products
The work products produced as a consequence of the testing strategy are identified.
2.5 Test record keeping
Mechanisms for storing and evaluating test results are specified.
2.6 Test metrics
A description of all test metrics to be used during the testing activity is noted here.
2.7 Testing tools and environment
A description of the test environment, including tools, simulators, specialized hardware, test files, and other resources is presented here.
2.8 Test schedule
A detailed schedule for unit, integration, and validation testing as well as high order tests is described.
3.0 Test Procedure
This section describes as detailed test procedure including test tactics and test cases for the software.
3.1 Software (SCIís) to be tested
The software to be tested is identified by name. Exclusions are noted explicitly.
3.2 Testing procedure
The overall procedure for software testing is described.
3.2.1 Unit test cases
The procedure for unit testing is described for each software component (that will be unit tested) is presented. This section is repeated for all components i.
3.2.1.2 Stubs and/or drivers for component i
3.2.1.3 Test cases component i
3.2.1.4 Purpose of tests for component i
3.2.1.5 Expected results for component i
3.2.2 Integration testing
The integration testing procedure is specified.
3.2.2.1 Testing procedure for integration
3.2.2.2 Stubs and drivers required
3.2.2.3 Test cases and their purpose
3.2.2.4 Expected results
3.2.3 Validation testing
The validation testing procedure is specified.
3.2.3.1 Testing procedure for validation
3.2.3.3 Expected results
3.2.3.4 Pass/fail criterion for all validation tests
3.2.4 High-order testing (a.k.a. System Testing)
The high-order testing procedure is specified. For each of the high order tests specified below, the test procedure, test cases, purpose, specialized requirements and pass/fail criteria are specified. It should be noted that not all high-order test methods noted in Sections 3.2.4.n will be conducted for every project.
3.2.4.1 Recovery testing
3.2.4.2 Security testing
3.2.4.3 Stress testing
3.2.4.4 Performance testing
3.2.4.5 Alpha/beta testing
3.2.4.6 Pass/fail criterion for all validation tests
3.3 Testing resources and staffing
Specialized testing resources are described and staffing is defined. The role of any ITG is also defined.
3.4 Test work products
The work products produced as a consequence of the testing procedure are identified.
3.5 Test record keeping and test log
Mechanisms for storing and evaluating test results are specified. The test log is used to maintain a chronological record of all tests and their results.
根据具体情况需要修改一些项目，如果需要中文版本，偶这里还有自己翻译的一份。
RichardHuang 2003-10-21
- 打赏
- 举报
呵呵英文版的我要了，我在外企做QA，用的到，谢谢
renfu999 2003-10-20
- 打赏
- 举报
初学!
期待高手!
期待高手!
