Test Plan Template(英文版)

louis_lu

最近部门在搞SW Process的规范，其中我们的测试占了很重要的一个比例，这是我所开心看到的。
我们着重要在test plan，test cases, release report, bug report方面做出一些具有指导性的文档来。
所以我现在急需一份english版的test plan作为指导。
请各位朋友帮忙，谢谢了！

AlexanderIII

google一下吧

eightants

Please see the following attachment.

[ 本帖最后由 eightants 于 2007-1-3 23:58 编辑 ]

louis_lu

You did a great help to me!
Thanks a lot!

enjoytest

thanks a lot for uploading the template

boluobing

Test Plan
Template
Version 1.0 ● 24 MAY 2006


Using This Template
The companion document, Test Plan Instructions, provides detailed direction for completing this template. This and other Framework documents, including a glossary, are available at www.dir.state.tx.us/pubs/framework/.
To create a document from this template:
1.        Delete the template title page (previous page) and this page.
2.        Replace [bracketed text] on the cover page (next page) with your project and agency information.
3.        Replace [bracketed text] in the document header area at the top of page i (Contents page) with the same project and agency information as on the cover page.
Note: Please do not remove or modify content in the footer area.
4.        Complete the entire template. Each section contains abbreviated instructions and a content area. The content area is marked with a placeholder symbol () or with a table. Relevant text from other project documents may be pasted into content areas.
5.        Update the table of contents by right-clicking and selecting “Update Field,” then “Update Page Numbers Only.”

TEXAS PROJECT DELIVERY FRAMEWORK
TEST PLAN

[Agency/Organization Name]
[PROJECT NAME]
VERSION: [Version Number]        REVISION DATE: [Date]


Approver Name        Title        Signature        Date
                       

Contents
Section 1.        Overview        1
Section 2.        Test Methodology        2
2.1         Elements of Testing        2
2.2         Types of Testing        2
2.3         Phases of Testing        3
Section 3.        Test Schedule        4
Section 4.        Test Monitoring and Reporting        5
4.1         Monitoring        5
4.2         Reporting        5
Section 5.        References        6
Section 6.        Glossary        7
Section 7.        Revision History        8
Section 8.        Appendices        9
Section 1.        Overview
Describe the high-level approach to testing for the project. Describe the test objectives, test scope, and approach to testing adopted by the project team.
Section 2.        Test Methodology
2.1         Elements of Testing
Describe the elements of testing for the project.
2.2         Types of Testing
2.2.1 Functional Testing
Describe the functional testing for the project.
2.2.2 Data Testing
Describe the data testing for the project.
2.2.3 User Testing
Describe the user testing for the project.
2.2.4        Non-functional (Systems Requirements) Testing
2.2.4.1        Performance Testing
Describe the performance testing for the project.
2.2.4.2        Quality Testing
Describe the quality testing for the project.
2.2.4.3         Interface Testing
Describe the interface testing for the project.
2.2.4.4        Other Testing
Describe the other testing for the project that is not covered in the types of tests described in previous sections.
2.3         Phases of Testing
Customize and complete the Test Phase Chart to reflect the test phases and approach for the project.

Test Phase Chart
Test Phases        Unit        Integration        System        Acceptance        X Phase
Objective                                       
Focus                                       
Test Types/
Subtypes                                       
Staffing                                       
Environ¬ment                                       
Entry Criteria                                        …
Suspen¬sion Criteria                                       
Exit Criteria                                       
Section 3.        Test Schedule
Provide a reference to the location of the project test schedule information or specify the project test schedule information. Include resources, prerequisites, and start/completion dates for each activity, deliverable, and milestone.  
Section 4.        Test Monitoring and Reporting
4.1         Monitoring
Describe monitoring activities and milestones that will be used to evaluate actual progress to plan.
4.2         Reporting
Describe the reports that will be used to document the execution and results of each test phase.
Section 5.        References
Identify the information sources referenced and utilized in developing the Test Plan.
Document No.        Document Title        Date        Author
                                       

Section 6.        Glossary
Define all terms and acronyms required to interpret the Test Plan properly.
Section 7.        Revision History
Identify document changes.
Version        Date        Name        Description
                       

Section 8.        Appendices
Include any relevant appendices.

boluobing

Text file name:        { The 〈 TestLink  〉 system  test report}
Item name:        {TestLink}

Use the unit:{ Use the unit name}
Design the unit: The numerical technique of the sea beginning of a reign develops limited Mr. in Peking

The item serial number  item name item the manager develops the representative director to test the representative director to test the engineer
{ Fill in}


Change the record

The edition number that changes the date changes the contents to change the person
{ Fill in}



The eyes record
Chapter 1 leads the speech        - 2 -
1.1 purposes        - 2 -
1.2 backgrounds        - 2 -
1.3 The edition definition rule        - 2 -
1.4 references        - 2 -
1.5  test essentialses        - 3 -
1.5.1  test essentials introduction        - 3 -
1.5.2 the tests participate the person's concrete arrangement        - 5 -
A test result and detection        - 6 -
2.1  unit tests with gather test        - 6 -
2.2  interface tests        - 6 -
2.3  function tests        - 7 -
2.3.1  function test outlines        - 7 -
2.3.2  function test conclusions        - 7 -
2.4  business tests        - 7 -
2.5 top the line test        - 8 -
An analytical conclusion        - 8 -
3.1 abilities        - 8 -
3.2 blemishs and restricts        - 8 -
3.3 test result        - 9 -
3.3.2 stage products release the quantity elucidation        - 9 -
3.3.3 quantity analysis and adjust the measure        - 9 -
3.3.3.1 other problem elucidations        - 9 -
3.3.3.2 influence analysis        - 9 -
3.4 conclusions        - 10 -
A human resource install        0



Chapter 1 leads the speech
1.1 purposes
  { This text file is carries on various comprehensive test to the 〈 TestLink  〉 item terrace behind of the total analysis report.At
After carrying on the test to the whole system, as a result carry on the analysis to various test, whether the analysis system meet the demands the rules or not
Request of settle.This report carried on the description towards synthesizing the test and returning to return the test as a result, the scope overlaid all 功s
Ability item and the business need, establishment the procedure can press to expect of conceive the confidence of the movement, also rise to provide for the customer
Apply and check before acceptance the function of reference.}
1.2 backgrounds
  { Want to be in accordance with the item need specification the elucidation with the related text file}
1.3 The edition definition rule
The edition rule  elucidation remarks
{ Fill in}

1.4 references
  { The need, the DEMO design of the item that the text file to consult etc. text file}
  { The report of the test that the text file to hand over, use an etc. text file}
1.5  test essentialses
  { The analytical report of this test is a foundation that plans the peaceful set  test problem report in the 〈  test of the TestLink 〉
Write up of.The whole test process of the 〈 TestLink 〉 is according to 《 ( TestLink) the test plan 》 of hour
The and human resources install something to carry on.This test the plan tests the person to the each stage, test time and must lift
The text file of hand over carried on the detailed plan, rising the direct and directive functions of time to the whole test process.
Carried on the unit test and gather according to the plan test, page test, function and business test, top line test,
The concrete test problem pay respects to 《 ( TestLink) the test problem report 》 , this form that reports the form recorded
The 〈 TestLink  〉 terrace is in test engineering the problem discover, and recorded to correspond the problem to test the person and measure
Try time and return to circumstance of return the test, until the problem close.}
1.5.1  test essentials introduction
  { In the whole item  implement process, the test work according to 《 ( TestLink) the test plan 》 define
The stage carries on the test of, ising divided into the unit and gathering test, interface test, function test, business test and top line
Test.Underneath to this severals introduction that tests the process of the part to be the synopsis respectively.}

  { Test the environment with actual the difference that the environment may exist:
  1, actual customer operate system in may have various advertisement to intercept the software, this will result in at use should department
In the process of 统 , flick the page open and will be shield, use the door and can't operate the system some set up the function of the window way lately.
  2, be the customer usage  IE browser low in 6.0 editions, the page style will appear the wrong and can't show
The page result etc. problem.}

  { Unit and gather test:The main purpose of the unit test is to obtain the applied procedure in can test the software most
The crumb segment, insulate with the rest part of the code it to open, then make sure its behavior whether with expectation of similar.
After testing each unit respectively gather they go to the mold piece with the test of the mold piece connects.Develop the personnel at
Develop and pass the unit test and can expel the code blemish of the big part in the process.
  Gather the test is the unit test of logic expand.Main test form is:Two  unit that have already tested
Constitute a module, and test they connect.In realistic project, many units constitute the set
Piece, but these modules come together again larger part of the procedure.The method is a combination that tests the part, and end expand
Progress, test the mold's piece with the mold piece of other sets together.End, will constitute all molds piece of progress to measure together
Try.In addition, if the procedure is constitute by several progress, becoming to test all progress towards testing them, not at the same time.
Gather the test can identify to combine the unit the problem for appear.Pass to gather test the circumstance quantity that the ability will arise problem
Reduce more in brief analytical Class.}

boluobing

{ Interface test:The interface test mainly according to the related need  text file, set out from the angle of the customer according to use
An interface JIAN3 JIE2, navigate definitely, the easy operation waits a few principles, taking need text file, DEMO as the basis to carry on the test.
The test mainly covers the 〈 TestLink  〉 terrace in each page of the mold a 〉 of the 〈 system.Give grind in test process
Deliver the department puts forward a lot of suggestions and problem, and carried on back to return the test towards change behind problem and the suggestion for adopt.}
In test process the main attention that page test/ the check order as follows:

Check the item category that tests the personnel and it evaluate
The window way cut over, move, change the hour of size normal?
{ Fill in}
Is various writing of interface chemical element right?( Such as the headline, hint etc.)
{ Fill in}
Is various appearance of interface chemical element right?( Such as valid, invalid, pick out
Wait the appearance)
{ Fill in}
Various interface  chemical element support  keyboard operation?
{ Fill in}
Various interface  chemical element support  mouse operation?
{ Fill in}
In the dialog box of lack the province focus right?
{ Fill in}
Does an ability of data exactitude return to show?
{ Fill in}
For the in common use function, customer can need not read can the manual use?
{ Fill in}
The performance contain the operation of the risk, having the "ing confirm"," give up"...etc. to hint?
{ Fill in}
Is the operation order reasonable?
{ Fill in}
Do you have the 联 machine help?
{ Fill in}
Is various layout of interface chemical element reasonable?Beauty?
{ Fill in}
Does various color of interface chemical element moderate?
{ Fill in}
Various shape beauty of interface chemical element?
{ Fill in}
The form of written beauty?
{ Fill in}
Does the diagram mark keep the view?
{ Fill in}


  { Function test:For the sake of the request of convenience and the business work that customer use, in the 〉 platform of 〈 TestLink
Definition the function mold piece, carried on the function test according to the need to each function  mold pieces, and chase to test the process in
Problem and some improvements  opinion feedbacks of the detection give correspond of develop the personnel to carry on the modification.Combine to change behind problem and adopt
The suggestion of the 纳 carries on back to return the test.}
  
  { Business test:The 〈 system  business process  description 〉 give with the form feedback of" BUG" the place that have problems
Correspond of develop the personnel to carry on the modification, the modification is behind return to test the personnel to carry on back to return the test, keep go to satisfy each 委
Do the business request that bureau correspond.}
  
  { Last line test:For insuring the system and canning circulate normally behind up the line, on the system the line is behind according to plan in advance
Carry on take out to measure to the business of the system.The scope that ascends the line test includes all functions of the 〈 TestLink  〉 terrace, and
The business that samples the 〈 to correspond flow or the business items 〉 make the business test, having the test item that the selection take out to measure extensively of
Represent sex.Combine to test in the problem discover hand over to be responsible for the engineer of the line of the system carries on revising in time,
Combine to carry on back to return the test to the problem change behind.}
1.5.2 the tests participate the person's concrete arrangement

The ordinal number test type            Participate the person
1    The unit test with gather test{ fill in}
2    The interface test
3    The function test
4    The business test
5    Last the line test


A test result and detection
2.1  unit tests with gather test
  { The main purpose of the unit test is obtain the applied procedure in can test the software of the minimum unit  mold piece, will it
Insulate with the rest part of the code to open, then make sure its behavior whether with expectation of similar.Each development personnel
Carry on after each unit complete to request to carry out the unit test according to the test norm, guarantee each unit nonentity
Problem, item manager each period  meeting folio delivers the personnel's  development result implement to make selective check, and check the solid unit test of
Usefulness.
  In distinguish testing each unit  mold piece after open personnel will they gather become arrive a mold piece with gather test
Of form carry on the examination, adoption from measure and cross the method of the test, some molds piece test the personnel to also get involved to carry on measure
Try, the item  manager's the test point concern to the mold piece and check, keep go to the whole business function all passes the test, just
Hand over to carry on the system test.
  Pass the unit test in accordance with gather the test, the item every variety of the havings totally the methodical logic and the design;Account
The test of row is already all to carry out;It have problems to was all record in the test;The problem discover has already resolved all;All
The problem of resolves all have already carried on back to return the test to combine to pass finally.}

boluobing

2.2  interface tests
  { According to 《 ( TestLink) the system test plan 》 , 《 ( TestLink) the system test uses the example 》 ,
《 ( TestLink) the DEMO design 》 carried on the page test to that system with the related need  text file.Be in the light of the boundary at the same time
Face JIAN3 JIE2, navigate definitely, this a few principles of easy operation carries on the test for the basis.
  Follow the tool Butterfly to carry on follow towards test in the problem discover and the suggestion for put forward through a blemish,
Combine the problem to succeed in catching to carried on back to return the test, pay respects to in a specific way 《 ( TestLink) the test problem report 》 .Attain
The need text file in the request of request and basic interface test describe, can carry on the business test and function tests
Stage.}
2.3  function tests
2.3.1  function test outlines
1. <TestLink>

The ordinal number test contents remarks
1{ fill in}{ fill in}
2
3
4


2.3.2  function test conclusions
  { According to 《 ( TestLink) the system test plan 》 , 《 ( TestLink) the system test uses the example 》 ,
《 ( TestLink) the need specification manual 》 carried on the function test to that system with the related need  text file, all
The function is normal, among them including to navigate, the data functions such as importation, processing and index etc..Get while use valid data
Arrive the anticipant result;Show the homologous mistake news or the warning newses while use invalid data;The business rules are all
Got the right application.All normal importation data, all schools of invalid data check the exactitude, and hint
The language is fitting, all data importation, processing and inspect all right without any error.To test in the problem discover and lift
The suggestion of follows the tool Butterfly to carry on follow through a blemish, and carried on back to return to measure to the problem after change
Try, close all problems, pay respects to in a specific way 《 ( TestLink) the test problem report 》 .Come to a the need text
The result of the request and the function test describe in the file.}
2.4  business tests
  { According to 《 ( TestLink) the system test plan 》 , 《 ( TestLink) the system test uses the example 》 , 《 ( TestLink)
The need specification manual 》 carried on the business test to that system with the related need  text file, the 〈 system  business process copy
Say the 〉 .Problem and the modification circumstances that test the detection can pay respects to 《 ( TestLink) the test problem report 》 , this report with
The form of the form recorded the 〈 TestLink  〉 terrace problem and the test results discover in the test.
  Follow the tool Butterfly to carry on follow towards test in the problem discover and the suggestion for put forward through a blemish,
Combine to carried on back to return the test to that problem, close all problems, pay respects to in a specific way 《 ( TestLink) the test ask
A report 》 .Come to a the need text file in the result of the request and the business test describe.}
2.5 top the line test
  { For insuring the system and canning circulate normally behind up the line, on the system the line is behind according to plan in advance to the industry of the system
The 务 carries on take out to measure.The scope that ascends the line test include 《 ( TestLink) the test problem report 》 all function of the terrace,
Sample the business that 〈 correspond to flow also or the business items 〉 make the business test, the items that take out to measure the selection have extensively of
Represent sex, can overlay the function of the system terrace.Combine to test in the problem discover hand over to be responsible for system last line
Of engineer carried on to revise in time, carried on back to return the test to the problem in modification, insure have problems all already
The close just can deliver to notify up the line, notify all participate the personnel up the line success.
  The environment that this time test use all according to true environment, pass to measure to the terrace function and parts of business
Try, all realizations with all function of the 〈 TestLink 〉 , the function of the system also can satisfy the business need completely.Most
Test all requests that take out to measure the processes to all meet the demands the specification manual of the result enunciation eventually, can consign the usage.}
  
An analytical conclusion
  { It cover the 〈 system business JIAN3 SHU4 〉's function scope in this system  test process, according to the business and actual
Function the organization carried on overall, system, valid test, as a result give according to the test test analysis conclusion:}

boluobing

3.1 abilities
  { At carried on the unit test and gather to the 〈 TestLink 〉 test, interface test, function test, business
Each kind of test of all levelses such as test and the top  line test etc. and pass the blemish to follow the tool to carry on the whole distance to follow close after, verify
The system carried out various function and designs that customer request completely, and put forward the system to create on this foundation
A little bit new, had to pass the ability that the network system completes the customer business.}
3.2 blemishs and restricts
  { The item set analyzed each stage test hard in the existent BUG, reason and key sticking points that seek the wrong emergence order,
Carried on to each kind of problem in time of close, and the modification that return to return the test and draw inference from one example to each kind of blemish implement,
Guaranteed all problems all with close, satisfied the whole function request of system.}
3.3 test result
3.3.1  test activity summary
Test beginning time       
Test be over time       
Test the address        Stage:
                Backstage:
Test the workload elucidation        Stage         The mission elucidation starts time        End time
                                    Plan physically        Plan        Actual
                The system test system test                               


3.3.2 stage products release the quantity elucidation

The blemish infusion total amount()        The blemish discovers the number        The blemish modifies the number        Isn't a problem/ nonsupport        The blemish remains the remainder        Blemish clearance rate
5 classes                                       
4 classes                                       
3 classes                               
2 classes                                       
One class                               
Suggest                               
Total                       

3.3.3 quantity analysis and adjust the measure
3.3.3.1 other problem elucidations
[ Still carry on the elucidation to the problem exist currently]
3.3.3.2 influence analysis
  [ Explain the influence of problem]
  
3.4 conclusions
  { After carrying on various function, function, the business 评's measure to the 〈 TestLink  〉 system, think that that system can
Satisfy the customer request, come to a the reserved target.
  Various index signs of that software can meet the demands the request of the specification manual, can consign the usage.}
  

A human resource install
                        Human resource
Role      The minimal resources( the full-time role quantity assign) concrete job or exegesises recommend
The director general of the technique{ fill in}                                    Carry on the management direct
                                                   Provide the technique guidance
                                                   Appropriate resources guarantee
                                                   Provide the management report

Test the representative director
{ Fill in}
Understand the need establishment test plan and use the example
Establishment test the tool and blemishs follow tool
Supervise and control to test the total degree of progress
Aim at to test the item establishment test report and conclusions
Test the engineer

{ Fill in}
The plan of press the test carries out each stage test
Use the problem follows the tool feedback  test problem
Record result
The execution returns to return the test, the close BUG
Valuation test the usefulness of the work
Install the managing person
{ Fill in}
   Insure to test the environment and the test datas( database)
The environment gets the management and maintenances.
   Manage to test the system
   Allotment and management role to test the interview power of the system
   The text in the item  file management

boluobing

http://www.cnblogs.com/hustlxjaw/archive/2007/01/26/630926.aspx                                          
                                           文档编号：
                                           版 本 号：
                                           密    级：内部绝密



文档名称:        {〈TestLink〉系统测试报告}
项目名称:        {TestLink}

使用单位：{使用单位名称}

项目编号 项目名称 项目经理 开发负责人 测试负责人 测试工程师
{填写}


变更记录

变更日期 版本号 变更内容 变更人
{填写}



目  录
第一章 引 言        - 2 -
1.1目的        - 2 -
1.2背景        - 2 -
1.3 版本定义规则        - 2 -
1.4参考资料        - 2 -
1.5测试概要        - 3 -
1.5.1测试概要介绍        - 3 -
1.5.2测试参与人具体安排        - 5 -
第二章 测试结果及发现        - 6 -
2.1单元测试与集成测试        - 6 -
2.2界面测试        - 6 -
2.3功能测试        - 7 -
2.3.1功能测试纲要        - 7 -
2.3.2功能测试结论        - 7 -
2.4业务测试        - 7 -
2.5上线测试        - 8 -
第三章 分析结论        - 8 -
3.1能力        - 8 -
3.2缺陷和限制        - 8 -
3.3测试结果        - 9 -
3.3.2本阶段产品发布质量说明        - 9 -
3.3.3质量分析及调整措施        - 9 -
3.3.3.1其他问题说明        - 9 -
3.3.3.2影响分析        - 9 -
3.4结论        - 10 -
第四章 人力资源配置        0



第一章 引 言
1.1目的
　　{本文档是对〈TestLink〉项目平台进行各种综合测试后的总体分析报告。在
对整个系统进行测试后，对各种测试的结果进行分析，分析系统是否满足需求规
定的要求。本报告对综合测试及回归测试结果进行了描述，范围覆盖了全部的功
能项和业务需求,建立程序能够按预期的设想运行的信心,同时也起到为用户提供
应用和验收参考的作用。}
1.2背景
　　{要与项目需求规格说明与相关文档一致}
1.3 版本定义规则
版本规则 说明 备注
{填写}

1.4参考资料
　　{文档所要参考项目的需求、DEMO设计等文档}
　　{文档所要提交测试的报告、用例等文档}
1.5测试概要
　　｛本测试分析报告是在〈TestLink〉的测试计划和平台测试问题报告的基础
上写成的。〈TestLink〉的整个的测试过程是按照《（TestLink）测试计划》的时
间和人力资源配置进行的。此测试计划对各个阶段的测试人、测试时间和所须提
交的文档进行了详细的计划，对整个的测试过程起到了时间的监督和指导的作用。
按照计划进行了单元测试、集成测试、页面测试、功能和业务测试、上线测试，
具体测试问题参见《（TestLink）测试问题报告》，此报告表格的形式记录了
〈TestLink〉平台在测试工程中所发现的问题，并记录了相应问题的测试人、测
试时间以及回归测试的情况，直到问题关闭。｝
1.5.1测试概要介绍
　　｛在整个项目实施过程中，测试工作是按照《（TestLink）测试计划》界定的
阶段进行测试的，分为单元和集成测试、界面测试、功能测试、业务测试和上线
测试。下面对这几个测试部分的过程分别做简要的介绍。｝

　　｛测试环境与实际环境可能存在的差异：
　　1、实际用户操作系统中可能会装有各种广告拦截软件，这会造成在使用该系
统过程中，弹出页面将会被屏蔽掉，使用户无法操作到系统一些新建窗口的功能。
　　2、当用户使用IE浏览器低于6.0版本时，页面样式会出现错位、无法显示
页面效果等问题。｝

　　｛单元和集成测试：单元测试的主要目的是获取应用程序中可测试软件的最
小片段，将其同代码的其余部分隔离开来，然后确定它的行为是否与预期的一样。
分别测试了每个单元后将它们集成到模块中以测试模块之间的接口。开发人员在
开发过程中通过单元测试可以排除大部分的代码缺陷。
　　集成测试是单元测试的逻辑扩展。主要测试形式是：两个已经测试过的单元
组合成一个组件，并且测试它们之间的接口。在现实方案中，许多单元组合成组
件，而这些组件又聚合成程序的更大部分。方法是测试片段的组合，并最终扩展
进程，将该模块与其他组的模块一起测试。最后，将构成进程的所有模块一起测
试。此外，如果程序由多个进程组成，成对测试它们，而不是同时测试所有进程。
集成测试能识别组合单元时出现的问题。通过集成测试能将发生问题的情况数量
减少到更简单的分析级别。｝
　　
　　｛界面测试：界面测试主要是根据相关需求文档，从用户的角度出发按照用
户界面简捷，导航明确，易操作等几个原则，以需求文档、DEMO为依据进行测试。
测试主要涵盖〈TestLink〉平台中〈系统模块〉的各个页面。在测试过程中给研
发部提出很多建议和问题，并对改后问题和采纳的建议进行了回归测试。｝
在测试过程中页面测试的主要注意/检查点如下：

检查项 测试人员的类别及其评价
窗口切换、移动、改变大小时正常吗？
{填写}
各种界面元素的文字正确吗？（如标题、提示等）
{填写}
各种界面元素的状态正确吗？（如有效、无效、选中
等状态）
{填写}
各种界面元素支持键盘操作吗？
{填写}
各种界面元素支持鼠标操作吗？
{填写}
对话框中的缺省焦点正确吗？
{填写}
数据项能正确回显吗？
{填写}
对于常用的功能，用户能否不必阅读手册就能使用？
{填写}
执行有风险的操作时，有“确认”、“放弃”等提示吗？
{填写}
操作顺序合理吗？
{填写}
有联机帮助吗？
{填写}
各种界面元素的布局合理吗？美观吗？
{填写}
各种界面元素的颜色协调吗？
{填写}
各种界面元素的形状美观吗？
{填写}
字体美观吗？
{填写}
图标直观吗？
{填写}

boluobing

｛功能测试：为了用户使用的方便和业务工作的要求，在〈TestLink〉平台
界定功能模块，对每一个功能模块都按照需求进行了功能测试，并把测试过程中
发现的问题和一些改进意见反馈给相应的开发人员进行修改。并对改后问题和采
纳的建议进行了回归测试。｝
　　
　　｛业务测试：〈系统业务流程描述〉把有问题的地方以“BUG”的形式反馈给
相应的开发人员进行修改，修改后返回给测试人员进行回归测试，直至满足各委
办局相应的业务要求。｝
　　
　　｛上线测试：为了确保系统上线后能够正常运行，系统上线后按照预先计划
对系统的业务进行抽测。上线测试的范围包括〈TestLink〉平台的所有功能，并
抽取〈相应的业务流或业务事项〉作业务测试，所选取抽测的测试项具有广泛的
代表性。并对测试中所发现的问题提交给负责系统上线的工程师进行及时修正，
并对改后的问题进行回归测试。｝
1.5.2测试参与人具体安排

序号 测试类型            参与人
1    单元测试与集成测试  {填写}
2    界面测试
3    功能测试
4    业务测试
5    上线测试


第二章 测试结果及发现
2.1单元测试与集成测试
　　｛单元测试的主要目的是获取应用程序中可测试软件的最小单元模块，将其
同代码的其余部分隔离开来，然后确定它的行为是否与预期的一样。各开发人员
在每个单元完成之后进行按照测试规范要求实施单元测试，保证每个单元不存在
问题，项目经理每个周期会对开发人员的开发成果实施抽查，并核实单元测试的
有效性。
　　在分别测试了每个单元模块后开放人员将它们集成到一个模块中以集成测试
的形式进行检测，采用自测和交叉测试的方法，某些模块测试人员也介入进行测
试，项目经理对模块的测试重点关注和检查，直至整个业务功能均通过测试，才
提交进行系统测试。
　　通过单元测试和集成测试，项目各类的所有共有方法的逻辑与设计一致；所计
划的测试已全部执行；测试中有问题都被记录；所发现的问题已全部解决；所有
解决的问题都已进行回归测试并最后通过。｝
2.2界面测试
　　｛按照《（TestLink）系统测试计划》、《（TestLink）系统测试用例》、
《（TestLink）DEMO设计》和相关需求文档对该系统进行了页面测试。同时本着界
面简捷，导航明确，易操作这几个原则为依据进行测试。
　　对测试中所发现的问题和提出的建议通过缺陷跟踪工具Butterfly进行跟踪，
并对捕获的问题进行了回归测试，具体参见《（TestLink）测试问题报告》。达到
了需求文档中所描述的要求和基本界面测试的要求，可进行业务测试和功能测试
阶段。｝
2.3功能测试
2.3.1功能测试纲要
　1. <TestLink>

序号 测试内容 备注
１   {填写}  {填写}
２
３
４


2.3.2功能测试结论
　　｛按照《（TestLink）系统测试计划》、《（TestLink）系统测试用例》、
《（TestLink）需求规格说明书》和相关需求文档对该系统进行了功能测试，所有
功能正常，其中包括导航，数据输入，处理和检索等功能。在使用有效数据时得
到预期的结果；在使用无效数据时显示相应的错误消息或警告消息；业务规则都
得到了正确的应用。所有的正常输入数据，所有无效数据的校验正确，并且提示
语恰当，所有的数据输入、处理和检索都正确无误。对测试中所发现的问题和提
出的建议通过缺陷跟踪工具Butterfly进行跟踪，并对改后的问题进行了回归测
试，关闭了所有的问题，具体参见《（TestLink）测试问题报告》。达到了需求文
档中所描述的要求和功能测试的效果。｝
2.4业务测试
　　｛按照《（TestLink）系统测试计划》、《（TestLink）系统测试用例》、《（TestLink）
需求规格说明书》和相关需求文档对该系统进行了业务测试，〈系统业务流程描
述〉。测试发现的问题及修改情况可参见《（TestLink）测试问题报告》，此报告以
表格的形式记录了〈TestLink〉平台在测试中发现的问题及测试结果。
　　对测试中所发现的问题和提出的建议通过缺陷跟踪工具Butterfly进行跟踪，
并对该问题进行了回归测试，关闭了所有的问题，具体参见《（TestLink）测试问
题报告》。达到了需求文档中所描述的要求和业务测试的效果。｝
2.5上线测试
　　｛为了确保系统上线后能够正常运行，系统上线后按照预先计划对系统的业
务进行抽测。上线测试的范围包括《（TestLink）测试问题报告》平台的所有功能，
并抽取〈相应的业务流或业务事项〉作业务测试，所选取抽测的事项具有广泛的
代表性，能覆盖系统平台的功能。并对测试中所发现的问题提交给负责系统上线
的工程师进行了及时修正，对修改后的问题进行了回归测试，确保所有问题均已
关闭才可以发上线通知，通知所有参与人员上线成功。
　　此次测试所使用的环境全部基于真实环境，通过对平台功能和部分业务的测
试，〈TestLink〉的所有功能全部实现，系统的性能也完全能够满足业务需求。最
终测试结果表明所有抽测流程都满足需求规格说明书的要求，可以交付使用。｝
　　
第三章 分析结论
　　｛本系统测试过程中涵盖〈系统业务简述〉的功能范围，按照业务和实际的
功能组织进行了全面、系统、有效的测试，基于测试结果给予测试分析结论：｝
3.1能力
　　｛在对〈TestLink〉进行了单元测试、集成测试、界面测试、功能测试、业务
测试和上线测试等各级各类测试和通过缺陷跟踪工具进行全程跟踪关闭后，验证
了系统完全实现了用户所要求的各种功能和设计，并在此基础上提出了系统的创
新点，具备了通过网络系统完成用户业务的能力。｝
3.2缺陷和限制
　　｛项目组认真分析了各阶段测试中存在的BUG，找出问题出现的原因和症结点，
对各类问题进行了及时的关闭，并对各类缺陷实施回归测试和举一反三的修改，
保证了所有的问题均以关闭，满足了系统整体的功能要求。｝
3.3测试结果
3.3.1测试活动总结
测试开始时间       
测试结束时间       
测试地址        前台：
                后台：
测试工作量说明        阶段         任务说明   开始时间        结束时间
                                    计划  实际        计划        实际
                系统测试 系统测试                               


3.3.2本阶段产品发布质量说明

缺陷注入总数（个）        缺陷发现数        缺陷修改数        不是问题/不支持        缺陷剩余数        缺陷清除率
5级                                       
4级                                       
3级                               
2级                                       
1级                               
建议                               
总计                       

3.3.3质量分析及调整措施
3.3.3.1其他问题说明
[对目前仍存在的问题进行说明]
3.3.3.2影响分析
　　[说明问题的影响]
　　
3.4结论
　　｛在对〈TestLink〉系统进行各种功能、性能、业务评测后，认为该系统能够
满足用户要求，达到了预定的目标。
　　该软件的各项指标能够满足需求规格说明书的要求，可交付使用。｝
　　

第四章 人力资源配置
                        人力资源
角色      所推荐的最少资源（所分配的专职角色数量） 具体职责或注释
技术总监  {填写}                                    进行管理监督
　                                                  提供技术指导
　                                                  适当的资源保障
　                                                  提供管理报告
　
测试负责人
{填写}
　了解需求制定测试计划及用例
　制定测试工具及缺陷跟踪工具
　监控测试总体进度
　针对测试项目制定测试报告及结论
测试工程师

{填写}
　按测试计划执行各阶段测试
　使用问题跟踪工具反馈测试问题
　记录结果
　实行回归测试，关闭BUG
　评估测试工作的有效性
配置管理员
{填写}
   确保测试环境和测试数据（数据库）
环境得到管理和维护。
   管理测试系统
   分配和管理角色对测试系统的访问权
   项目中的文档管理

fanglu619

谢谢分享

boluobing

using System;
using System.IO;
using System.Collections;
namespace FileReader_csharp
{
///  
/// Summary description for Class1.
///  
class Homework
{



struct codeInfo

　　 {

　　 public long line; //储存这个源程序的行数

　　 public string ext; //这个文件的拓展名

　　 public string filename; //文件名

　　 public string fullname; //全路径加文件名

　　 //构造函数。

　　}


//参数说明：ext是包含多个拓展名的字符串数组，dir为查找目录，list为集合的类的引用，用于动态存储codeInfo结构

　　 void count(string[] ext, string dir, ref ArrayList list)

　　 {

　　 DirectoryInfo di = new DirectoryInfo(dir); //新建对象，用目录作为构造参数

　　 DirectoryInfo[] d = di.GetDirectories(); //托管数组d存了方法返回的所有子目录信息

　　

　　 foreach (DirectoryInfo dCur in d) //对子目录进行遍历

　　 {

　　 foreach (string extCur in ext) //按照每个拓展名分别查找

　　 {

　　 FileInfo[] fi = dCur.GetFiles(extCur); //获得当前目录下满足拓展名的文件

　　 foreach (FileInfo fCur in fi) //遍历每个文件

　　 {

　　 //实现统计文件的行数

　　 long n=0;

　　 StreamReader sr = new StreamReader(fCur.FullName);
　　 while (!sr.EndOfStream)

　　 {

　　 n++;

　　 sr.ReadLine();

　　 }

　　 codeInfo a = new codeInfo(n, extCur, fCur.Name, fCur.FullName); //存储这个文件的信息

　　 list.Add(a); //将该文件信息加入到集合列表中

　　 }

　　 }

　　 count(ext,dCur.FullName,ref list); //递归遍历子目录的子目录

　　 }

　　 }



　private void Click(object sender, EventArgs e)

　　 {

　　 string[] ext = getExt(textBox1.Text);

　　 listBox1.Items.Clear();

　　 codeList.Clear();

　　//省略判断拓展名是否合法及目录是否为空，详见源码

　　 count(ext, label3.Text, ref codeList); //调用统计函数

　　 if (codeList.Count == 0)

　　 listBox1.Items.Add(" 没有找到指定扩展名的源文件！");

　　 else

　　 {

　　 listBox1.Items.Add(" 共找到" + ext.Length + "种源文件");

　　 listBox1.Items.Add(" ");

　　 codeInfo typecur = (codeInfo)codeList[0];

　　 long numcur = 0, linecur = 0, lineall = 0;

//下面按照文件名分类统计不同扩展名源程序的总行数

　　foreach (string extcur in ext)

　　{

　　 numcur = 0;

　　 linecur = 0;

　　 for (int i = 0; i < codeList.Count; i++)

　　 {

　　 codeInfo cur = (codeInfo)codeList;

　　 if (extcur == cur.ext)

　　 {
　　 numcur++; linecur += cur.line;

　　 }

　　 }

　　 lineall += linecur;

　　 listBox1.Items.Add(string.Format(" {0,-8}" + numcur + " 个文件 " + linecur + "行", extcur)); //统计完一种拓展名后向Listbox添加一行信息

　　 }

　　 listBox1.Items.Add(" 总计" + codeList.Count + "个文件 " + lineall + "行");

　　 }

　　 }






}

boluobing

using System;
using System.IO;
using System.Collections;
namespace FileReader_csharp
{
///  
/// Summary description for Class1.
///  
class Homework
{



struct codeInfo

　　 {

　　 public long line; //储存这个源程序的行数

　　 public string ext; //这个文件的拓展名

　　 public string filename; //文件名

　　 public string fullname; //全路径加文件名

　　 //构造函数。

　　}


//参数说明：ext是包含多个拓展名的字符串数组，dir为查找目录，list为集合的类的引用，用于动态存储codeInfo结构

　　 void count(string[] ext, string dir, ref ArrayList list)

　　 {

　　 DirectoryInfo di = new DirectoryInfo(dir); //新建对象，用目录作为构造参数

　　 DirectoryInfo[] d = di.GetDirectories(); //托管数组d存了方法返回的所有子目录信息

　　

　　 foreach (DirectoryInfo dCur in d) //对子目录进行遍历

　　 {

　　 foreach (string extCur in ext) //按照每个拓展名分别查找

　　 {

　　 FileInfo[] fi = dCur.GetFiles(extCur); //获得当前目录下满足拓展名的文件

　　 foreach (FileInfo fCur in fi) //遍历每个文件

　　 {

　　 //实现统计文件的行数

　　 long n=0;

　　 StreamReader sr = new StreamReader(fCur.FullName);
　　 while (!sr.EndOfStream)

　　 {

　　 n++;

　　 sr.ReadLine();

　　 }

　　 codeInfo a = new codeInfo(n, extCur, fCur.Name, fCur.FullName); //存储这个文件的信息

　　 list.Add(a); //将该文件信息加入到集合列表中

　　 }

　　 }

　　 count(ext,dCur.FullName,ref list); //递归遍历子目录的子目录

　　 }

　　 }



　private void Click(object sender, EventArgs e)

　　 {

　　 string[] ext = getExt(textBox1.Text);

　　 listBox1.Items.Clear();

　　 codeList.Clear();

　

　　 count(ext, label3.Text, ref codeList); //调用统计函数

　　 if (codeList.Count == 0)

　　 listBox1.Items.Add(" 没有找到指定扩展名的源文件！");

　　 else

　　 {

　　 listBox1.Items.Add(" 共找到" + ext.Length + "种源文件");

　　 listBox1.Items.Add(" ");

　　 codeInfo typecur = (codeInfo)codeList[0];

　　 long numcur = 0, linecur = 0, lineall = 0;

//下面按照文件名分类统计不同扩展名源程序的总行数

　　foreach (string extcur in ext)

　　{

　　 numcur = 0;

　　 linecur = 0;

　　 for (int i = 0; i < codeList.Count; i++)

　　 {

　　 codeInfo cur = (codeInfo)codeList;

　　 if (extcur == cur.ext)

　　 {
　　 numcur++; linecur += cur.line;

　　 }

　　 }

　　 lineall += linecur;

　　 listBox1.Items.Add(string.Format(" {0,-8}" + numcur + " 个文件 " + linecur + "行", extcur)); //统计完一种拓展名后向Listbox添加一行信息

　　 }

　　 listBox1.Items.Add(" 总计" + codeList.Count + "个文件 " + lineall + "行");

　　 }

　　 }






}

liqingqing1011

收到。

boluobing

using System;
using System.IO;
using System.Collections;
namespace FileReader_csharp
{
///  
/// Summary description for Class1.
///  
class Homework
{



    struct codeInfo

　　   {

　　     public long line; //储存这个源程序的行数

　　     public string ext; //这个文件的拓展名

　　     public string filename; //文件名

　　     public string fullname; //全路径加文件名

　　 //构造函数。

　　   }


//参数说明：ext是包含多个拓展名的字符串数组，dir为查找目录，list为集合的类的引用，用于动态存储codeInfo结构

　　 void count(string[] ext, string dir, ref ArrayList list)

　　   {

　　     DirectoryInfo di = new DirectoryInfo(dir); //新建对象，用目录作为构造参数

　　     DirectoryInfo[] d = di.GetDirectories(); //托管数组d存了方法返回的所有子目录信息

　　

　　     foreach (DirectoryInfo dCur in d) //对子目录进行遍历

　　   {

　　     foreach (string extCur in ext) //按照每个拓展名分别查找

　　   {

　　     FileInfo[] fi = dCur.GetFiles(extCur); //获得当前目录下满足拓展名的文件

　　     foreach (FileInfo fCur in fi) //遍历每个文件

　　   {

　　 //实现统计文件的行数

　　     long n=0;

　　     StreamReader sr = new StreamReader(fCur.FullName);
　　    while (!sr.EndOfStream)

　　      {

　　        n++;

　　        sr.ReadLine();

　　       }

　　     codeInfo a = new codeInfo(n, extCur, fCur.Name, fCur.FullName); //存储这个文件的信息

　　     list.Add(a); //将该文件信息加入到集合列表中

　　      }

　　      }

　　     count(ext,dCur.FullName,ref list); //递归遍历子目录的子目录

　　      }

　　      }



　   private void Click(object sender, EventArgs e)

　　   {

　　     string[] ext = getExt(textBox1.Text);

　　     listBox1.Items.Clear();

　　     codeList.Clear();

　
　　     count(ext, label3.Text, ref codeList); //调用统计函数

　　    if (codeList.Count == 0)

　　           listBox1.Items.Add(" 没有找到指定扩展名的源文件！");

　　   else

　　      {

　　           listBox1.Items.Add(" 共找到" + ext.Length + "种源文件");

　　           listBox1.Items.Add(" ");

　　           codeInfo typecur = (codeInfo)codeList[0];

　　           long numcur = 0, linecur = 0, lineall = 0;

//下面按照文件名分类统计不同扩展名源程序的总行数

　　     foreach (string extcur in ext)

　　        {

　　           numcur = 0;

　　           linecur = 0;

　　     for (int i = 0; i < codeList.Count; i++)

　　          {

　　               codeInfo cur = (codeInfo)codeList;

　　      if (extcur == cur.ext)

　　            {
　　               numcur++; linecur += cur.line;

　　            }

　　          }

　　          lineall += linecur;

　　          listBox1.Items.Add(string.Format(" {0,-8}" + numcur + " 个文件 " + linecur + "行", extcur)); //统计完一种拓展名后向Listbox添加一行信息

　　       }

　　          listBox1.Items.Add(" 总计" + codeList.Count + "个文件 " + lineall + "行");

　　      }

　　   }

}

gg.5281

thanks for your kind

tyrael_79

学习学习

sunlaomi

Thank you~