Test Report模版
单元测试报告
Unit Test Report
V1.0
拟制人:
学号:
审核人:
批准人:
年月日
目录（Content）
1 引言（Introduction） (2)
1.1 编写的目的(Purpose) (2)
1.2 背景说明(Background) (2)
1.3 定义(Definition) (2)
1.4 参考文献(Reference) (2)
2 测试情况概述（Test Overview） (2)
2.1 测试对象（Test Object） (2)
2.2 测试时间（Test Time） (3)
2.3 测试方法（Test Methods） (3)
2.4 测试约束（Test Constraint） (5)
2.5 测试人员（Testers） (5)
3 测试环境(Test Environment) (5)
3.1 测试硬件环境（Test Hardware Environment） (5)
3.2 测试软件环境（Test Software Environment） (5)
4 测试情况（Test Situation） (6)
4.1 测试内容（Test Content） (6)
4.2 测试完成情况(Test Completion Situation) (9)
5 测试结果及分析（Test Result and Analysis） (9)
5.1 注册(Registration) (10)
5.1.1 注册简介（Registration Instruction） (10)
5.1.2 数据约束（Data Constraint） (10)
5.1.3 无效测试案例（Invalid Test Case） (11)
5.1.4 有效测试案例（Valid Test Case） (14)
5.2 登录(Login) (18)
5.2.1 登录简介（Login Instruction） (18)
5.2.2 数据约束(Data Constraint) (18)
5.2.4 有效测试案例（Valid Test Case） (20)
5.3 用户列表(User List) (22)
5.3.1 用户列表简介（User List Instruction） (22)
5.3.2 数据约束（Data Constraint） (23)
5.3.3 无效测试案例（Invalid Test Case） (23)
5.3.4 有效测试案例（Valid Test Case） (23)
6 评价 (23)
1 引言（Introduction）
1.1 编写的目的(Purpose)
xxx小组成员对高校大学生生活信息平台进行测试后编写的单元测试报告，根据实际测试过程和测试结果进行汇总，并反映测试情况。
GLT team members living in Huai'an information platform for college students writing unit tests after the test report, according to the actual testing process and summary of test results, and reflect the test situation.
1.2 背景说明(Background)
此测试报告的阅读对象为小组成员和客户相关人员。
This test report was designed with the Huaiyin Institute of Technology, Instructor - Zhu full silver, GLT team members and customer-related personnel. Huaiyin Institute of GLT software development group consists of six members.
1.3 定义(Definition)
用户列表：记录了注册用户的姓名，IP地址，注册时间。
User list: Record the name of the registered user, IP address, registration time. 1.4 参考文献(Reference)
[1] Ron Patton.软件测试.北京：机械工业出版社，2005.3
[2] Elfriede Dustin.有效软件测试.北京：清华大学出版社，2005.7
[3] Paul C.Jorgensen. 软件测试.北京：机械工业出版社，2008.5
2 测试情况概述（Test Overview）
2.1 测试对象（Test Object）
本次单元测试的测试对象为软件开发小组开发的高校大学生生活信息平台中登录注册模块，开发人员利用Microsoft Visual Studio 2008内的https://www.wendangku.net/doc/f56383357.html,设计、C#开发，使用SQL2005。
The test object for unit testing of software development team for the development of GLT Huai'an information platform for college students living in the Login module, developers use Microsoft Visual Studio 2008 design of the https://www.wendangku.net/doc/f56383357.html,, C # development, use SQL2005.
2.2 测试时间（Test Time）
测试分两个阶段：
第一阶段---对各个子模块进行测试，导师和小组成员根据实际对各子模块的功能提出改进意见。时间：
第二阶段---集成测试。时间：
Tested in two phases:
--- first stage testing of each sub-module, mentors and team members of each
sub-module based on the actual function of suggestions for improvement. Time: 2011/4/11-2011/5/11
--- second phase of integration testing. Time: 2011/5/16-2011/5/25
2.3 测试方法（Test Methods）
2.3.1白盒测试法（White Box Testing）
英文为White Box Testing。又称结构测试或者逻辑驱动测试。
English as White Box Testing. Also known as structural testing or logic driven testing.
白盒测试是把测试对象看作一个打开的盒子。利用白盒测试法进行动态测试时，需要测试软件产品的内部结构和处理过程，不需测试软件产品的功能。
White-box testing is to test the object as an open box. White-box testing method using the dynamic test, the need to test the internal structure of software products and processes, without testing the software product's features.
白盒测试法的覆盖标准有逻辑覆盖、循环覆盖和基本路径测试。其中逻辑覆盖包括语句覆盖、判定覆盖、条件覆盖、判定/条件覆盖、条件组合覆盖和路径覆盖。
White-box testing method covers the standard logical coverage, loop coverage and the basic path testing. Covered include the logical statement coverage, decision coverage, condition coverage, decision / condition coverage, conditions, coverage and path coverage portfolio.
白盒测试是知道产品内部工作过程，可通过测试来检测产品内部动作是否按照规格说明书的规定正常进行，按照程序内部的结构测试程序，检验程序中的每条通路是否都有能按预定要求正确工作，而不顾它的功能，白盒测试的主要方法有逻辑驱动、基路测试等，主要用于软件验证。
White-box testing is to know the inner workings of the process of product, test to detect the product by the internal action is in accordance with the normal provisions of the specification, internal structure according to the procedures testing procedures, inspection procedures in each channel can be scheduled if requirements are correct Work, regardless of its functions, the main white-box testing methods are the logical drive, based road testing, mainly for software validation.
2.3.2黑盒测试法（Black Box Testing）
英文为Black Box Testing。又称功能测试或者数据驱动测试。
English as Black Box Testing. Also known as functional testing or data-driven testing.
黑盒测试是根据软件的规格对软件进行的测试，这类测试不考虑软件内部的运作原理，因此软件对用户来说就像一个黑盒子。
Black box testing is based on software specifications for software testing, such tests do not consider the principle of the internal operation of the software, so software users as a black box.
软件测试人员以用户的角度，通过各种输入和观察软件的各种输出结果来发现软件存在的缺陷，而不关心程序具体如何实现的一种软件测试方法。
Software Testers to the user's point of view, observing through a variety of input and output to a variety of software defects found in software without regard to the specific procedures for how to implement a software testing methods.
2.4 测试约束（Test Constraint）
本次测试整体测试约束如下：
a. 测试报告基于本次被测试软件版本；
b. 所有测试都基于相同的测试环境（包括主机、操作系统、数据库等）；
c. 测试方案在参考实际操作，最测试内容做了适当规整。
This test whole test restraint is as follows:
a. The test reported based on this time is tested the software edition;
b. All tests all based on same test environment (including main engine, operating system, database and so on);
c. The test plan in the reference actual operation, most tested the content to do suitably neat.
2.5 测试人员（Testers）
测试人员为xxx软件开发小组成员。
Testers are from huaiyin GLT software development teams.
3 测试环境(Test Environment)
3.1 测试硬件环境（Test Hardware Environment）
表1 测试硬件环境表
测试环境配置说明操作系统版本内存外接存储
开发环境主机PC机Windows 7 2G 无
Table1 Test hardware environment table
Test Environment Configuration Operating System
Version Memory External
storage
Host development
environment
PC machine Windows 7 2G No 3.2 测试软件环境（Test Software Environment）
表2 测试软件环境表
软件产品名
数据库SQL2005
操作系统Windows 7
Web应用服务器IE 7.0
Table2 Test software environment
Software Product Name
Database SQL2005
Operating System Windows 7
Web Application Service IE 7.0
4 测试情况（Test Situation）
4.1 测试内容（Test Content）
本次测试主要进行了界面的功能测试，界面测试主要对登录注册模块的注册、登录和用户列表三个界面进行测试。注册模块的测试见表3,登录模块的测试见表4,用户列表的测试见表5:
The test mainly for the screen function test, interface test module mainly Login register, login and user interface list of the three tests. Up the module test in Table 3, Table 4 test the login module, the test user list in Table 5:
表3 注册测试用例执行情况
测试用例测试内容执行次数测试结果
Reg-0 用户名长度5+5 第一次输入达到预期效果；
第二次输入达到预期效果；Reg-1 密码长度5+5+5 第一次输入和第二次输入不
达到预期效果；
第三次输入达到预期效果；Reg-2 密码是否为空 2 达到预期效果
Reg-3 用户名和密码为空 3 达到预期效果
Reg-4 用户名已经注册过 2 达到预期效果
Reg-5 2次输入的密码不一致 2 达到预期效果
Reg-6 用户名和密码输入特殊字符10 达到预期效果
Reg-7 用户名和密码相同10 达到预期效果
10 达到预期效果
Reg-8 密码是否在数据库中加密显
示
Reg-9 用户名是否区分大小写10 达到预期效果
Reg-10 是否支持tap和enter键等10 达到预期效果
Reg-11 密码是否可以复制10 没达到预期效果
2+2+2+2 达到预期效果
Reg-12 用户名中带空格（空格出现位
置：开始，中间，末尾）
2+2+2+2 达到预期效果
Reg-13 密码中带空格（空格出现位
置：开始，中间，末尾）
Reg-14 密码是否支持汉字10 达到预期效果
Table3 Registration Test Case Execute Situation
Execute Result
Test Case Test Content Execute
Views
Reg-0 User Name Length 5+5 First achieve the expected
result；
Second achieve the expected
result；
Reg-1 Password Length 5+5+5 First and second achieve the
expected result；
Third achieve the expected
result；
Reg-2 Whether password empty 2 Achieve the expected result Reg-3 Whether password and uer
name empty
3 Achieve the expected result
Reg-4 User Name has been registered 2 Achieve the expected result Reg-5 Two password is consistent 2 Achieve the expected result Reg-6 User name and password input
special characters
10 Achieve the expected result Reg-7 User name and password are
same
10 Achieve the expected result Reg-8 Password encrypted display in
the Database
10 Achieve the expected result Reg-9 User name is case-sensitive 10 Achieve the expected result Reg-10 Whether support tap and enter
key etc
10 Achieve the expected result
Reg-11 Whether Password can be
copied
10 Not achieve the expected result
Reg-12 Username with a space
(appear in: begin , middle, end)
2+2+2+2 Achieve the expected result
Reg-13 Password with a space (appear
in: begin , middle, end)
2+2+2+2 Achieve the expected result Reg-14 Character password whether
supported
10 Achieve the expected result
作为登录测试所用的有效数据就必须是用户已经注册过的数据,下面两组数
据为注册过的有效数据:
注册的用户名：xxxxxx 密码：xxxxx
注册的用户名：xxxxxx 密码：xxxxx
表4 登录测试用例执行情况
测试用例测试内容执行总数测试结果
Log-0 数据库中不存在的用户名 2 达到预期效果
Log-1 数据库中存在的用户名，密码
错误
10 达到预期效果
Log-2 用户名和密码为空 2 达到预期效果
Log-3 输入用户名，但不输入密码 2 达到预期效果
Log-4 不输入用户名，但输入密码 2 达到预期效果
Log-5 支持不同账户在同一机子上
登录10 8次达到预期效果；2次没达
到预期效果
Log-6 同一账户在不同机子上登录10 7次达到预期效果；3次没达
到预期效果
Log-7 登录是否可以最小化 2 达到预期效果
Log-8 忘记密码功能 5 没达到预期效果
Log-10 记住用户名和密码 2 达到预期效果
Log-11 密码是否可以区分大小写5+5 达到预期效果
Used as a login test to be valid data to the data the user has registered the following two sets of data for effective data registered:
Registered User Name：Liuxing49 Password：654321m
Registered User Name：Suwan625 Password：6543218
Table4 Login Test Case Execute Situation
Test Case Test Content Execute View Execute Result
Log-0 Username does not existed in
database
2 Achieve the expected result
Log-1 Username existed in database,
password is fault
10 Achieve the expected result
Log-2 Username and password are
empty
2 Achieve the expected result
Log-3 Input username, un-input
password
2 Achieve the expected result
Log-4 Input password, un-input
username
2 Achieve the expected result
Log-5 Whether support different
account to login on the same
machine 10 8 times achieve the expected
result；2 times not achieve the
expected result.
Log-6 Whether support same account
to login on the different
machine 10 7 times achieve the expected
result；3 times not achieve the
expected result.
Log-7 Whether login can minimize 2 Achieve the expected result Log-8 Re-get password function 5 Not achieve the expected result Log-10 Remember Username and
Password
2 Achieve the expected result Log-11 Password is case sensitive 5+5 Achieve the expected result 用户列表的功能实现是基于注册实现的,只要注册成功用户列表中便增加相应的信息。
表5 用户列表测试用例执行情况
测试用例测试内容执行总数测试结果
List-0 注册中点击“我同意”按钮 5 达到预期效果
List-1 点击“退出” 2 达到预期效果Realization of the function the user list is based on up to achieve, as long as the registered user list will increase the success of the appropriate information.
Table 5 User Name Test Case Execute Situation
Test Case Test Content Execute View Execute Result
5 Achieve the expected result
List-0 Click“我同意”button in
Registration
List-1 Click“退出”button 2 Achieve the expected result 4.2 测试完成情况(Test Completion Situation)
测试工作从xxxx年xx月xx号进行模块测试，时长近一个月。而后紧接着的是时长十天的集成测试，其间编写了测试用例。
表6 测试工作完成情况
测试任务名称具体内容完成度
制定测试计划，编写测试用例对于找到的资源用不同的格式来显示90%
准备测试数据、环境详见测试案例100%
执行功能测试，填写测试数据详见测试案例100%
整理测试数据，编写测试报告把测试数据进行整理并编写测试报告95% Testing from April 11, 2011 the module test, nearly one month duration. Then followed ten days is the length of the integration test, during the preparation of the test cases.
Table 6 Test Completion Situation
Test Task Name Content Percent
Complete
90% Test plans, writing test case Find resources for the different formats used to
display
See test case 100% Prepare test data and
environment
See test case 100% Execute function test, fill up test
data
Sorting out test data to writing test report 95% Sort out test data, writing test
report
5 测试结果及分析（Test Result and Analysis）
xxxxx小组成员用前期编写的测试用例对登录注册模块的测试。登录注册模块被分为注册、登录和用户列表三个子功能，根据测试结果对各个子功能进行详细分析。此外注册登录模块的密码均加密，实现其功能代码为“System.Web.Security.FormsAuthentication.HashPasswordForStoringInConfigFile(Password, "md5")”
GLT team members to use pre-written test cases for Login module testing. Login module is divided into registration, login and user lists three sub-functions, according to results of a detailed analysis of each sub function. Also up for the password are
encrypted login module to achieve its function code
“System.Web.Security.FormsAuthentication.HashPasswordForStoringInConfigFile(Password, "md5")”
5.1 注册(Registration)
5.1.1 注册简介（Registration Instruction）
在登录注册模块中，首先打开的是登录界面，还不是会员的用户要先注册。单击登录界面的右下方有一个注册按钮进入注册界面，用户要填写的内容有用户账户，用户姓和名，密码，还有方便以后找回密码所选择的问题和回答，输入正确的验证码，最后同意本网站的注册协议便完成了注册。注册里面的用户账号根据实际有进行约束，性别默认为“先生”，为了安全考虑-设置验证码。
In the Login module, first open the login screen, not a member of the user must first register. Click the bottom right of the login screen there is a registration button to enter the registration interface, the user must fill out the contents of a user account, the user first and last name, password, and password to facilitate future retrieve the selected questions and answers, enter the correct verification code , finally agreed to the registration agreement of this site will be completed the registration. Registered inside the user account has conducted according to the actual constraints, gender, the default is "Sir", for safety considerations - Set verification code. Implementation verification code which is called class "ValidateCode"; verification code constraint function implementation code "https://www.wendangku.net/doc/f56383357.html,pare (Session [" CheckCode "]. ToString (), tbx_chkcode.Text.Trim (), true)! = 0, return false; ".
5.1.2 数据约束（Data Constraint）
a.用户名长度最大长度为20个字符；密码长度大于等于6个字符切小于等于14个字符；
b.用户名和密码均不为空；
c.两次输入的密码必须一致；
d.不允许用户名和密码一致；
e.密码和用户名不允许出现空格。
a. length of maximum length of user name is 20 characters; password length is greater than or equal to 6 characters cut 14 characters or less;
b. the user name and password are not empty;
c. Passwords must be consistent;
d. do not allow the same user name and password;
e. password and user name does not allow spaces.
5.1.3 无效测试案例（Invalid Test Case）
a.用户名长度最大长度为20个字符；密码长度大于等于6个字符切小于等于14个字符；
表7 用户名长度约束无效案例
输入输出期望输出
liuxing4952582mu05133 报错报错
Miaolongwahinamainini1 报错报错
Dajieshisushedidiaodr22 报错报错
Shuishenshisusheyige249 报错报错
Dashenshisushewbuaixh1111 报错报错
表8 密码长度约束无效案例
输入输出期望输出
liuxi 报错报错“小于6个字符”
Miao 报错报错“小于6个字符”
D 报错报错“小于6个字符”
Shuishenshiseyige249 报错报错“大于14个字符”
Dashenshisushewbu111 报错报错“大于14个字符”
表7中给出了用户名长度大于20个字符的测试数据，实际输出均和期望输出一样；表8中给出了密码长度小于6个字符切大于14个字符的测试数据，实际输出均和期望输出一样；表中用于密码长度小于6个字符切大于14个字符的功能关键代码“pwdlength <= 5 ，return false;”，“pwdlength > 14，return false;”。
a. length of maximum length of user name is 20 characters; password length is greater than or equal to 6 characters cut 14 characters or less;
Table7 User Name Length Constraint Invalid Case
Input Output Expected Output
liuxing4952582mu05133 Error Error
Miaolongwahinamainini1 Error Error
Dajieshisushedidiaodr22 Error Error
Shuishenshisusheyige249 Error Error
Dashenshisushewbuaixh1111 Error Error
Table8 Password Length Constraint Invalid Case
Input Output Expected Output
liuxi Error Warning“Less than 6 characters”
Miao Error Warning“Less than 6 characters”
D Error Warning“Less than 6 characters”
Shuishenshiseyige249 Error Warning“More than 14 characters”
Dashenshisushewbu111 Error Warning“More than 14 characters”
Table 7 shows the user name longer than 20 characters of the test data, the actual output and expected output are the same; Table 8 shows the password length is less than 6 characters cut more than 14 characters of test data, the actual Output and expected output are the same. Table for password length is less than 6 characters cut features more than 14 characters key code “pwdlength <= 5 ，return false;”，“pwdlength > 14，return false;”.
b.用户名和密码均不为空；
表9 用户名和密码不为空约束无效案例
用户名输入密码输入输出期望输出
Liuxing4 报错报错“不为空”
Muxiaolong2 报错报错“不为空”
报错报错“不为空”
表9中给出了用户名和密码不能为空的测试数据，实际输出均和期望输出一样。
b. the user name and password are not empty;
Table 9 User Name and Password not Empty Constraint Invalid Case
Input User Name Input Password Output Expected Output
Liuxing4 Error Warning“Not Empty”
Muxiaolong2 Error Warning“Not Empty”
Error Warning“Not Empty”
Table 9 shows the user name and password can not be empty test data, the actual output and expected output are the same.
c.两次输入的密码必须一致；
表10 密码两次输入一致约束无效案例
设置密码输入确认密码输入输出期望输出
Liuxing49 Liuxing4 报错报错“不一致”
Muxiaolong2 Muxiaolong 报错报错“不一致”
Shuishen315 Liuxing49 报错报错“不一致”
表10中给出了两次输入的密码必须一致的测试数据，实际输出均和期望输出一样。
c. Passwords must be consistent;
Table10 Two Passwords Consistent Constraint Invalid Case
Input Set Password Input Affirm Password Output Expected Result
Liuxing49 Liuxing4 Error Warning“Not Consistent”Muxiaolong2 Muxiaolong Error Warning“Not Consistent”Shuishen315 Liuxing49 Error Warning“Not Consistent”
Table 10 shows the two passwords must be the same test data, the actual output and expected output are the same.
d.不允许用户名和密码一致；
表11 用户名和密码不一致约束无效案例
用户名输入密码输入输出期望输出
Liuxing49 Liuxing49 报错报错
Muxiaolong2 Muxiaolong2 报错报错
Shuishen315 Shuishen315 报错报错
表11中给出了不允许用户名和密码一致的测试数据，实际输出均和期望输出一样。
d. do not allow the same user name and password;
Table11 User Name and Password not Consistent Invalid Case User Name Input Password Input Output Expected Result
Liuxing49 Liuxing49 Error Error
Muxiaolong2 Muxiaolong2 Error Error
Shuishen315 Shuishen315 Error Error
Table 11 shows the user name and password does not allow the same test data, the actual output and expected output are the same.
e.密码和用户名不允许出现空格。
表12 用户名和密码出现空格约束无效案例
用户名输入密码输入输出期望输出
Liuxing 49 4952582 mu 报错报错
Muxiaolo ng2 82525249xin 报错报错
Shuishen315 315392 08hu 报错报错
表12中给出了不允许用户名和密码出现空格的测试数据，实际输出均和期望输出一样。
e. password and user name does not allow spaces.
Table12 User Name and Password blank space Constraint Invalid Case
Input User Name Input Password Output Expected Result
Liuxing 49 4952582 mu Error Error
Muxiaolo ng2 82525249xin Error Error
Shuishen315 315392 08hu Error Error
Table 12 shows the user name and password does not allow spaces in the test data appear, the actual output and expected output are the same.
5.1.4 有效测试案例（Valid Test Case）
a.用户名长度最大长度为20个字符；密码长度大于等于6个字符切小于等于14个字符；
表13 用户名长度约束有效案例
输入输出期望输出
liuxing2582mu 成功成功
Miaolongwahi 成功成功
Dajieshisusr22 成功成功
Shuishenshe249 成功成功
Dashenshisushexh1111 成功成功
表14 密码长度约束有效案例
输入输出期望输出
Liuxing49 成功成功
Miaolong222 成功成功
Discojiu54n 成功成功
Shuisfdsige249 成功成功
Dashen 成功成功
表13中给出了用户名长度小于20个字符的测试数据，实际输出均和期望输出一样；表14中给出了密码长度大于等于6个字符切小于等于14个字符的测试数据，实际输出均和期望输出一样。
a. length of maximum length of user name is 20 characters; password length is greater than or equal to 6 characters cut 14 characters or less;
Table13 User Name Length Constraint Valid Case
Input Output Expected Result
liuxing2582mu Success Success
Miaolongwahi Success Success
Dajieshisusr22 Success Success
Shuishenshe249 Success Success
Dashenshisushexh1111 Success Success
Table14 Password Length Constraint Valid Case
Input Output Expected Result
Liuxing49 Success Success
Miaolong222 Success Success
Discojiu54n Success Success
Shuisfdsige249 Success Success
Dashen Success Success
Table 13 shows the user name length is less than 20 characters of the test data, the actual output and expected output are the same; Table 14 shows the password length is greater than or equal to 6 characters to 14 characters or less cut the test data , the actual output and expected output are the same.
b.用户名和密码均不为空；
表15 用户名和密码不为空约束有效案例
用户名输入密码输入输出期望输出
Liuxing49 4952581mu 成功成功
Muxiaolong2 8252549mu2 成功成功
表15中给出了用户名和密码均不为空的测试数据，实际输出均和期望输出一样。
b. the user name and password are not empty;
Table15 User Name and Password Not Empty Constraint Valid Case
User Name Input Input Output Expected Output
Liuxing49 4952581mu Success Success
Muxiaolong2 8252549mu2 Success Success
Table15 shows the user name and password can not be empty test data, the actual output and expected output are the same.
c.两次输入的密码必须一致；
表16 密码两次输入一致约束有效案例
设置密码输入确认密码输入输出期望输出
Liuxing49 Liuxing49 成功成功
Muxiaolong2 Muxiaolong2 成功成功
Shuishen315 Shuishen315 成功成功
表16中给出了两次密码一致的测试数据，实际输出均和期望输出一样。
c. Passwords must be consistent;
Table16 Two Passwords Consistent Constraint valid Case Set Password Input Affirm Password Input Output Expected Result
Liuxing49 Liuxing49 Success Success
Muxiaolong2 Muxiaolong2 Success Success
Shuishen315 Shuishen315 Success Success
Table 16 shows the two passwords must be the same test data, the actual output and expected output are the same.
d.不允许用户名和密码一致；
表17 用户名和密码不一致约束有效案例
用户名输入密码输入输出期望输出
Liuxing49 4952582mu 成功成功
Muxiaolong2 Shagua49 成功成功
Shuishen315 31552539n 成功成功
表17中给出了用户名和密码不允许一致的测试数据，实际输出均和期望输出一样。
d. do not allow the same user name and password;
Table17 User Name and Password not consistent valid Case
User Name Input Password Input Output Expected
Liuxing49 4952582mu Success Success
Muxiaolong2 Shagua49 Success Success
Shuishen315 31552539n Success Success Table 17 shows the user name and password does not allow the same test data, the actual output and expected output are the same.
e.密码和用户名不允许出现空格。
表18 用户名和密码出现空格约束无效案例
用户名输入密码输入输出期望输出
Liuxing49 4952582 mu 成功成功
Muxiaolong2 82525249xin 成功成功
Shuishen315 31539208hu 成功成功
表18中给出了用户名和密码均不出现空格的测试数据，实际输出均和期望输出一样。
e. password and user name does not allow spaces.
Table 18 User Name and Password blank space Constraint Invalid Case
User Name Input Password Input Output Expected Result
Liuxing49 4952582 mu Success Success
Muxiaolong2 82525249xin Success Success
Shuishen315 31539208hu Success Success
Table 18 shows the user name and password does not allow spaces in the test data appear, the actual output and expected output are the same.
5.2 登录(Login)
5.2.1 登录简介（Login Instruction）
为享有更多的权限，用户需要登录进入平台。用户登录必须是注册过的用户；用户只要填入正确的账户名，密码和验证码后单击【登录】就以可成功登录。为了安全考虑设置时间限制。
To enjoy more privileges, users need to log into the platform. Must be a registered user logs off users; users will fill in the correct account name, password and verification code and click 【登录】to login to be successful login. Set time limits for security reasons.
5.2.2 数据约束(Data Constraint)
a.用户名与密码一致；
b.用户名和密码均不为空；
c.登录成功必须用户名，密码和验证码都正确。
a. the same user name and password;
b. the user name and password are not empty;
c. successful login to the user name, password and authentication code are correct.
5.2.3 无效测试案例（Invalid Test Case）
下面两组数据为注册过的有效数据:
注册的用户名：Liuxing49 密码：654321m
注册的用户名：Suwan625 密码：6543218
The following two sets of data valid for the registered data:
Registered User Name：Liuxing49 Password：654321m
Registered User Name：Suwan625 Password：6543218
a.用户名与密码一致；
表19 用户名和密码一致约束无效案例
用户名输入密码输入输出期望输出
Liuxing49 6543218 报错报错“不一致”
Suwan625 654321m 报错报错“不一致”
表19中给出了用户名和密码均一致的测试数据，实际输出均和期望输出一样。
a. the same user name and password;
Table 19 User Name and Password Consistent Invalid Case User Name Input Password Input Output Expected Result
Liuxing49 6543218 Error Warning“Not Consistent”
Suwan625 654321m Error Warning“Not Consistent”
Table 19 shows the user name and password are the same test data, the actual output and expected output are the same.
b.用户名和密码均不为空；
表20 用户名和密码不为空约束无效案例
用户名输入密码输入输出期望输出
Liuxing49 报错报错“不为空”
6543218 报错报错“不为空”
报错报错“不为空”
表20中给出了用户名和密码不为空的测试数据，实际输出均和期望输出一样。
b. the user name and password are not empty;
Table 20 User Name and Password Not Empty Invalid Case User Name Input Password Input Output Expected Result
Liuxing49 Error Warning“Not Empty”
6543218 Error Warning“Not Empty”
Error Warning“Not Empty”
Table 20 shows the user name and password do not empty the test data, the actual output and expected output are the same.
c.登录成功必须用户名，密码和验证码都正确。
表21 用户名、密码和验证码都一致约束无效案例
用户名输入密码输入验证码输入输出期望输出
Liuxing49 654321m （输入错误）报错报错
EMC test report
WBS QM EMC test report 1/24
1Document Change Record 2/24
Table of Contents (1) 1DOCUMENT CHANGE RECORD (2) 2DOCUMENT REFERENCES (4) 2.1A PPLICABLE D OCUMENTS (4) 2.2R EFERENCED D OCUMENTS (4) 3INTRODUCTION (5) 4EIT-01 (POWER) (6) 5EIT-02 (DATA/HK INTERFACE) (7) 6EIT-03 (ZERO & COMB) (9) 7OPT-03 (ATTENUATOR STEP SIZES) (11) 8PET-01 (COMB ANALYSIS) (12) 9CS ON POWER LINES / COMMON AND DIFFERENTIAL MODE (13) 10CS ON SIGNAL LINES / COMMON MODE (15) 11CS TRANSIENTS ON POWER LINES (16) 11.1C OMMON MODE (16) 11.2D IFFERENTIAL MODE (18) 12RS WITH E-FIELD (20) 13RS WITH H-FIELD (23) 14SUMMARY OF TEST RESULTS (24) 3/24
2Document References 2.1Applicable Documents 2.2Referenced Documents 4/24
连接器群组测试报告connectortestreport
连接器群组测试报告 c o n n e c t o r t e s t r e p o r t Document serial number【NL89WT-NY98YT-NC8CB-NNUUT-NUT108】
DESCRIPTION：产品说明 CONNECTOR 高度连接器 PART NO.： 料号 DATE： 日期 2012/12/28 DOCUMENT NO.： 文件号码 REV.： 版本 A INDEX 索引 1.SCOPE 3 适用范围 2.APPLICABLE DOCUMENTS 3 适用的文件 3.TEST CONDITIONS AND SEQUENCE 3 5 测试条件与次序
4.TEST METHOD OF INSPECTION 5 10 测试检验方法 5.SUMMARY OF THE QUALIFICATION 11 27 TEST RESULT 测试结果 6. APPENDIX 28 附件 1. SCOPE 适用范围 1.1TESTED SAMPLES: 85 pcs. 测试样品数: 85个 1.2PURPOSE This qualification test report contains the quality requirements, test procedures and test results of a qualification test program on the part no: 目的 这个合格检验报告针对泰强料号: 进行测试，测试内容包含合格测 验规范、测验程序和测验的结果 2.APPLICABLE DOCUMENTS 适用的文件 2.1EIA-RS-364 2.2Test report of FCN: 3. TEST CONDITIONS AND SEQUENCE 测试条件与次序 3.1TEST CONDITIONS Unless otherwise specified, tests and examinations were conducted under conditions within the following ranges: Temperature: 20±5℃ Atmospheric Pressure: 650 to 800 millimeters to inches) of Mercury
抗老化测试报告TEST REPORT
TEST REPORT NO:DECAI20170710 Date:AUG 10,2017 Page:1of 3 CUSTOMER NAME: DECAI PLASTIC TECHNOLOGY CO;LTD.DONGGUAN ADDRESS: NO.75.LIANYAN STREET YANWU VILLAGE DALINGSHAN TOWN DONGGUAN CITY CHINA The following sample(s) was/were submitted and identified on behalf of the client as: Sample Name : UV MATERIAL Ref.No. : 20170701 Sample Information : RESISTANCE TO UV Date of Receipt : Aug 01,2017 Testing Start Date : Aug 01,2017 Testing End Date : Aug 09,2017 Test result(s) : For further details,please refer to the following page(s) Signed for DECAI Standards Technical Center
TEST REPORT NO: DECAI20170710 Date: AUG 06,2017 Page: 2of 3 Note: Pass:Meet the requirements; Fail:Does not meet the requirements; /:Not Apply to the judgment. Original Sample Photo:
SOFTWARE TEST REPORT (STR)
SOFTWARE TEST REPORT (STR) Contents 1 Scope 1.1 Identification 1.2 System overview 1.3 Document overview 2. Referenced documents 3. Overview of test results 3.1 Overall assessment of the software tested 3.2 Impact of test environment 3.3 Recommended improvements 4. Detailed test results 4.x (Project-unique identifier of a test) 4.x.1 Summary of test results 4.X.2 Problems encountered 4.x.2.y (Project-unique identifier of a test case) 4.x.3 Deviations from test cases/procedures 4.x.3.y (Project-unique identifier of a test case) 5. Test log 6. Notes A. Annexes
Software Test Report (STR) I - Scope. This clause should be divided into the following subclauses. 1.1 Identification. This subclause shall contain a full identification of the system and the software to which this document applies, including, as applicable, identification number(s), title(s), abbreviations, version number(s), and release number(s). 1.2 System overview. This subclause shall briefly state the purpose of the system and the software to which this document applies. It shall describe the general nature of the system and software; summarize the history of system development, operation, and maintenance; identify the project sponsor, acquirer, user, developer, and maintenance organizations; identify current and planned operating sites; and list other relevant documents. 1.3 Document overview. This subclause shall summarize the purpose and contents of this document and shall describe any security or privacy protection considerations associated with its use. 2. Referenced documents. This clause shall list the number, title, revision, date, and source of all documents referenced in this 3. Overview of test results. This clause should be divided into the following subclauses to provide an overview of test results. 3.1 Overall assessment of the software tested. This subclause shall: a. Provide an overall assessment of the software as demonstrated by the test results in this report b. Identify any remaining deficiencies, limitations, or constraints that were detected by the testing performed. Problem/change reports may be used to provide deficiency information. c. For each remaining deficiency, limitation, or constraint, describe: 1 )Its impact on software and system performance, including identification of requirements not met 2) The impact on software and system design to correct it 3) A recommended solution/approach for correcting it 3.2 Impact of test environment. This subclause shall provide an assessment of the manner in which the test environment may be different from the operational environment and the effect of this difference on the test results. 3.3 Recommended improvements. This subclause shall provide any recommended improvements in the design, operation, or recommended improvements are provided, this subclause shall state "None." 4. Detailed test results. This clause should be divided into the following subclauses to describe the detailed results for each test. Note: The word "test' means a related collection of test cases. 4.x (Protect-unique identifier of a test). This subclause shall identify a test by project- unique identifier and should be divided into the following to describe the test results. 4.x. I Summary of test results. This subclause shall summarize the results of the test. The summary shall include, possibly in a table, the completion status of each test case associated with the test (for example, 'all results as expected,' "problems encountered," "deviations required'). When the completion status is not 'as expected,' this subclause shall reference the following subclauses for details. 4.x.2 Problems encountered. This subclause should be divided into subclauses that identify each test case in which one or more problems occurred. 4.x.2.y (Protect-unique identifier of a test case). This subclause shall identify by project- unique identifier a test case in which one or more problems occurred, and shall provide:
TEST REPORT 检验报告
No.: SHF101A1279 TEST REPORT 检验报告 Name of Sample: 样品名称： 糖足宝（袜子） Applicant: 委托单位：美国+ MD 2929N Main N.Logan. Utah https://www.wendangku.net/doc/f56383357.html,A Test Purpose: 检验类别： ENTRUST TEST 委托检验 Intertek Testing Services Ltd., Shanghai 6/F., No. 2 Building, Shanghai Comalong Industrial Park, No. 889 Yishan Road, Shanghai, 200233, China. 上海天祥质量技术服务有限公司 中国上海市宜山路889号齐来工业城2号楼6层西侧邮政编码: 200233 Tel: 0086-21-61206565，Fax: 0086-21-64954500
TEST REPORT REPORT No.: SHF101A1279 PREPARED AND CHECKED BY: AUTHORIZED BY: FOR INTERTEK TESTING SERVICES FOR INTERTEK TESTING SERVICES LTD., SHANGHAI LTD., SHANGHAI RICHARD CHAI JOHN WANG FOOD LAB MANAGER FOOD DIVISION MANAGER Page 1 of 3 NAME OF SAMPLE 产品名称 糖足宝（袜子） TEST PURPOSE 检验类别 ENTRUST TEST SPECIFICATION 型号、规格、等级 / TRADEMARK 商标 / CLIENT 委托单位 美国+ MD MANUFACTURER 生产单位 / DATE SAMPLE RECEIVED 委托样品收到日期 Jun. 09, 2010 2010年06月09日 SAMPLE QUANTITY 样品数量 1 piece PRODUCTION DATE 生产日期 / CODE / NUMBER 批号或编号 / TESTING STANDARD 检验依据或判定标准 ASTM E 2149-01-2001 TESTING PERIOD 检验日期 Jun. 09, 2010 TO Jun. 14, 2010 2010年 06月09日至 2010年06月14日 TESTING CONTENT 检验内容 CIRCUMSTANCES ARE IN THE REPORT ATTACHMENT. 详见检验报告附页。 CONCLUSION 检验结论 SUPPLY REAL MEASURING DATA 提供实测数据 CIRCUMSTANCES ARE IN THE REPORT ATTACHMENT 详见检验报告附页 签发日期2010年06月 14日 REMARK 备注 THE TESTING RESULTS ARE ONLY VALID FOR THE SAMPLE TESTED. 检测结果仅对来样负责。 *********************************************************************** TO BE CONTINUED
TEST REPORT TEMPLATE - FEP_QN (REV03)
DATE: OCT 31, 2014PAGE 1 OF 7 SECTION 1 FEP/QN TEST MATRIX Material Types 8 HE Nickel (Ni)#Aluminum (Al) Copper (Cu) Cobalt (Co) Organic Tin as Tin (Sn) Coatings √√√√√√Wood / Metal / Glass / Ceramics √√/ / / / General materials √√/ / / √Liquid & Sticky materials √√/ / / √Dry, Brittle and Powder like materials √√/ / / √ NOTE: 1 √= Applicable; / = Not applicable 2 # Total Nickel (Ni) content requirement also applies to non-small parts SECTION 2 FEP/QN TEST REPORT TEMPLATE CONCLUSION: TEST SAMPLES TEST STANDARD RESULT {To be filled in by lab} SRS-018 PASS / FAIL EN 71-3:2013 (Selected Heavy Elements) PASS / INCONCLUSIVE / FAIL Directive 2009/48/EC, Appendix A, total Nickel (Ni) content in accessible materials PASS / FAIL SRS-046 Phthalates PASS / FAIL Diisobutyl phthalate (DiBP) content PASS / SEE RESULT LABORATORIES SHALL REVISE THE LIMITS BELOW FOR OTHER MATERIAL CATEGORIES
TEST REPORT
D R A F T The content of this PDF file is accordance with the original issued reports for reference only.此PDF 電子檔內容根據原簽發之紙本報告製作，僅供參考用。 Unless otherwise stated the results shown in this test report refer only to the sample(s)tested.This test report cannot be reproduced,except in full,without prior written permission of the Company.除非另有說明，此報告結果僅對測試之樣品負責。本報告未經本公司書面許可，不可部份複製。 This Test Report is issued by the Company under its General Conditions of Service which is available on request or accessible at https://www.wendangku.net/doc/f56383357.html,/terms_and_conditions.htm.Attention is drawn to the limitation of liability,indemnification and jurisdiction issues defined therein.Any holder of this Test Report is advised that information contained hereon reflects the Company’s findings at the time of its intervention only and within the limits of Client’s instructions,if any.The Company’s sole responsibility is to its Client and this document does not exonerate parties to a transaction from exercising all their rights and obligations under the transaction documents.Any unauthorized alteration,forgery or falsification of the content or appearance of this document is unlawful and offenders Mechanical &Hardgoods Lab Report No ：HY/2009/70221Page ：1of 6Date ：2009/10/08 REMO,Inc.(c /o REMO Asia Inc.) 28101Industry Drive, Valencia,California 91355,USA The following merchandise was submitted &identified by the applicant as:Type of Product:Style/Item No:Manufacturer/Vendor:Country of Origin:Lollipop-Drum,6-8-10"OD ET-7106&7108&7110-00REMO China China,P.R.Sample Receiving Date:Testing Period:2009/01/14&2009/07/092009/01/15–02/26&2009/07/10–10/07 We have tested the submitted sample(s)as requested and the following results were obtained:Test Requested For compliance with lead in paint/similar surface coating material,lead in accessible substrate materials and phthalates content in US Public Law 110-314(HR 4040‘Consumer Product Safety Improvement Act of 2008’). Test Results -Please refer to next page(s).Results summary Test item Result Lead in paint /similar surface coating material PASS Lead in accessible substrate materials PASS Phthalates PASS Overall Conclusion The submitted samples comply with the requested test requirements. *This report is combined with report of HY/2009/10283* Signed for and on behalf of SGS Taiwan Ltd. Iris Huang Supervisor
测试报告(HD-SPI-VER-TestReport-SystemTest)V1.0
物联网生产指挥系统 系统测试报告 XXXX有限公司 未经允许，文档内容不可全部或部分发表、复制、使用于任何目的。
目录 1.引言 (1) 1.1.编写目的 (1) 1.2.项目背景 (1) 1.3.定义规约 (1) 1.4.参考资料 (2) 2.测试概要 (2) 2.1.进度回顾 (2) 2.2.测试用例 (2) 2.3.测试方法 (2) 2.4.测试环境 (3) 3.测试结果 (3) 3.1.需求覆盖率 (3) 3.2.缺陷汇总 (4) 3.3.缺陷分析 (6) 3.4.遗留缺陷 (6) 4.测试结论与建议 (6) 4.1.测试结论 (6) 4.2.典型缺陷引入原因分析 (7) 4.3.测试建议 (7)
1.引言 1.1.编写目的 本测试报告为XXXX系统二期的系统分析报告，目的在于总结测试以及分析测试结果，描述系统是否符合需求。 预期人员包括测试人员、开发人员、项目主管、其他质量管理人员和需要阅读本报告的项目经理。 1.2.项目背景 1.3.定义规约 Bug严重性：分为致命、严重、一般、较小 Bug优先级：分为特急、加急、高、中、低、无 Bug出现频率：分为总是、有时、随机、没有试验、无法重现 致命bug：当系统无响应，处于死机状态，需要其他人工修复才可复原，点击某个菜单显示“页面不能够显示”或者返回异常错误或不能进行正常操作，影响用户正常使用的功能。 严重bug：出现页面功能点使用有误、有较大的功能缺陷的现象。 一般bug：页面中的非重点功能的操作问题，普通、较轻、界面及不影响使用的的功能缺陷。 较小bug：建议或意见。
1.4.参考资料 2.测试概要 2.1.进度回顾 2.2.测试用例 2.3.测试方法 主要采用黑盒测试方法。 测试系统对于所有功能点是否实现，正常及异常流程和数据是否正确，主要针对功能需求，主要关心功能是否实现。具体测试方法如下： 1.执行测试用例； 2.为随机测试中发现的问题补充测试用例； 3.进行回归测试。
中英文Test Report1
Test Report 测试报告 Page 1 of 3 Report No.报告编号RLSZC000466440001 第1页，共3页Applicant SHENZHEN FENGCAI PAINT SCIENCE & TECHNOLOGY CO.,LTD 申请人：深圳丰彩油墨科技有限公司 Address 3TH INDUSTRLAL AREA SHA JING BAOAN,SHENZHEN CHINA 地址：中国深圳宝安沙井第三工业区 Report on the submitted sample(s) said to be 报告提供样品 Sample Name INK 样品名称：油墨 Sample Description Blue-gray ink 样品简述蓝灰色油墨 Part No.部分编号：011,012,014,024,025,032,038,041,043,044,048,051,052,T-3,T-7,T-186,XT-300 Sample Received Date 样品接收日期2010年3月4号 Testing Period测试期：2010年3月4日—3月10日 Test Requested As specified by client, to determine the Fluorine(F), Chlorine(CI), Bromine(Br), Iodine(I) content in the submitted sample. 测试要求：由委托人指定，确定提交的样品中含有氟(F), 氯(CI), 溴(Br), 碘(I) 等要素 Test Method Test Result(s) Please refer to the following page(s). 测试结果请参阅以下页 Tested by测试员Inspected by 检验员 Approved by批准人Date日期 No. 56657036
EN 50564 Test report
Test Report standby and off mode , and network standby, electric power consumption of networked equipment Product under test Brand name as identified on product Netgear Model identification FVS336G v3 Version or serial number ‐‐ Product description Dual WAN Gigabit SSL VPN Firewall Regulatory reference EC Commission Regulation No. 1275/2008 and No. 801/2013 Name of applicant NETGEAR, Inc. Address of applicant 350 East Plumeria Drive, San Jose, California 95134, USA Name of test laboratory Sporton International Inc. Address of test laboratory 14 Fl ‐2, No. 186, Jianyi Road, Zhonghe District, New Taipei City, Taiwan Test report number X431514C024 Test date 2014‐05‐01 Prepared by Mindy Tsai Approved by Hans Hsieh Test results Availability to deactivate the wireless network connection N/A, no wireless network function. Availability of power management No. Default period of power management N/A Network port(s) providing power management function N/A
- Drop Test Report (跌落测试)
- SOFTWARE TEST REPORT (STR)
- 测试报告(HD-SPI-VER-TestReport-SystemTest)V1.0
- EMC test report
- 测试报告 Test Report
- Test Report
- 抗老化测试报告TEST REPORT
- TEST REPORT 检验报告
- TRANSIT TEST REPORT
- Test Report测试报告
- 硬度测试报告Hardness Test Report
- Test Report
- TEST REPORT
- 动车卫生间水盆密封试验报告 test Report
- EN 50564 Test report
- Derating test report
- 测试报告 Test Report
- 摩擦测试报告(Rubbing Test Report)-英文版
- 连接器群组测试报告,connectortestreport资料
- 材料试验报告Material test report