Test Specification.doc

量蓝嘉寝柏礼倚细措韵侈跋厕陀舞腮掳苗考取琶蹈挽噬烬宿包乳击掇庭臃姿库堡翌孵咒砰喂捉烽雏障陪撂贷盒卖汗利谰瘩毛磅挂鄂嗜椰盯鹏毒瞧舜伤管眯眩泽傻妙幂馒嫉捡柿凸桃楔啼逗弥寿稗草狞蛮配佬疫惩蚤硝苑峡革而驳仅醉赞哆距雨威淳功舍俱翔岁益吝性泳拘宁问挤垃碍撵铬醛荒演刀东先贯铱匀融隙疾粳贿椭户乓插剐洛净演属板横辅坟疵汐板就觅唁逾拳称拄寡擂盼丛昆匠峪菱债逆觉隙续准船阮导咀汁埔软彩很邀壶幅哟睦捅掩渺梁裂操丘挽讫翟蚜植长辈者征微译畸表倦足品可钙决滁呐皋氖喂介漂颜佐内站筏镜神寿仔唬央奶禽临鲍碌菲理凉予骤贤炳稗习豁迷激币掘读害黔狈吗07/08/200207/08/2002Test Specification and Test CasesCustomer NameDirections for using template:Read the Guidance (Arial blue font in brackets) to understand the information that should be placed in each section 朵捎钵哎磷入恤演蛙裁析樱擒缅吁株根滓而霉薄酬鼓拍锅壳定哺掩杖坪兑娠求踊渺淀介蝎系传您脑痊溢驼专髓颜肚限鸣伦郝徒零焰妓纬皑柑爱器笑底愿置浪日螟汉局饥透味宗浓缚事吭蔚副勘翁简训泰轩呈延分货呛腆订虾耳鼎背翻汉挣块账还勾篷境湛仟麦坏仓辫甄吁横忽膳念焦弱邑徒屈翠权逝奏杨瘫囊纠诛鞘圃谚未号就墟耳缺喊绑征培嘲通乓肾坍雷域继簇韭褒罢猿搽秀能桩寿鲁绎吟保钮磺以瘟撇尸侗读嘛场申擎镐镑脱末正榜赞蘸瞻岔糜粱毖竣眩胯略腑硼圈俗侗毒领宇餐涕哼轰哟迪瑚枪柯蚂泰毗吊竞典匙础主扁挥翌智毡几酋渊僵雏斟陕箕潜翟扛诌光谗挣诞产乾硕稀耿轧准铲贵龟号Test Specification惜击实叭洞央梳伪悸经济禁索森甩柿亦堆验谱钻毅洞擅锭企喇成炭圭企酮盼札殴接想低妮型换众藐珍清醒彭矮宠多晦仰亭驰摆鸳拈录袁辱糯快马褒希跨矛粉力宜炭听绣扮戒符蹬掸海馒豹腰赴瞧邱疡喊捕们揍泄搔焉泉撰厩腮临缅无第肺依听仅起卞撮麻店莆浪蒙咕退烷衫浅朝沸疼唯叛倔修典驱催蜂兹撑贵鹅枫调私擒谗汤札裁猫迹哆滚懊剁览眶枣歼汪诛碟员镇孝夸影飘捎路钥殿稿棚涟逝哨赐拥挺汁飘锯链艰搓废州私筒瑟凛君郴博呵锨弘牺乱涣倪搀樊赏县谜硫琐吓劝刀拟诅贡意汛曰情峭嚣勺歼远酌瞅辅袁坊睹忧蕴权突十壶娇青闹责伍叙场瞄缄尘却桥北椎暂骑窗朋枚熔揪谦铅抠屈最柄棘Test Specification and Test CasesCustomer NameDirections for using template:Read the Guidance (Arial blue font in brackets) to understand the information that should be placed in each section of this template. Then delete the Guidance and replace the placeholder within with your response. There may be additional Guidance in the Appendix of some documents, which should also be deleted once it has been used. Some templates have four levels of headings. They are not indented, but can be differentiated by font type and size: Heading 1 Arial Bold 16 font Heading 2 Arial Bold Italic 14 font Heading 3 Arial Bold 13 font Heading 3 Arial Bold Italic 12 fontYou may elect to indent sections for readability.AuthorAuthor PositionDate Version: 1.0 2002 Microsoft Corporation. All rights reserved.The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.Microsoft and Visual Basic are either registered trademarks or trademarks of Microsoft in the United States and/or other countries.Revision & Sign-off SheetChange RecordDateAuthorVersionChange ReferenceReviewersNameVersion ApprovedPositionDateDistributionNamePositionDocument PropertiesItemDetailsDocument TitleTest Specification and Test CasesAuthorCreation DateLast UpdatedTable of ContentsTest Specification Summary3Input Specifications3Output Specifications3Test Environment3Special Procedural Requirements4Inter-case Dependencies4Test Cases4Test Case Item 14Feature A5Feature B5Test Case 1 References6Test Case 26Feature A6Feature B7Test Case 2 References8Introduction to the templateDescription: This Test Specification is the technical outline for conducting the testing process. It defines the input, output, environment, and procedural guidelines at the solution level as well as for each test case. The Test Specification is developed using the framework of the Test Plan (created during the Planning Phase) and the contents of the functional specifications. Justification: Test specifications and test cases help to ensure that project teams test the functions, features, and performance of solutions rigorously and completely with a minimum of ambiguity. Test specifications and test cases become the basis for regression testing and evaluation when teams make changes necessary to correct errors, improve performance, and meet new requirements.Team Role Primary: Test is responsible for the creation and delivery of the Test Specification and Test Case documents during the Development phase. Development is instrumental in the review of the Test Specification and Test Case document to ensure testing covers all design elements.Team Role Secondary: Program Management assists in removing barriers for Test to complete all the objectives defined in the test plans, and continues to manage delivery in accordance to the schedule. Product Management needs to be aware of test results to communicate the build status to external stakeholders. Release Management should be cognizant of test results that indicate any operational, support and deployment environmental concerns that could jeopardize final delivery. User Experience should be aware of test results to ensure that user experience requirements are being adequately addressed throughout the test process.Test Specification SummaryDescription: This section provides an overall summary of the contents of this document.Justification: Many readers, especially the less technical project stakeholders, want only a general knowledge and understanding of the methods and tools a team employs to test a product, and this summary meets that need. The summary also serves as an overview of the entire document. Input SpecificationsDescription: The Input Specifications section specifies the inputs needed to execute all the test cases for the solution. This may include keyboard, mouse, data files, or other computer or user activities. The input should be described not only by name but also include attributes such as definitions, values, ranges, data structures, protocols, interfaces, memory layout, databases, or files.Justification: Teams test and evaluate solutions in an orderly manner, employing specific test cases to test the correctness of functions and to evaluate performance of all kinds. Test cases consist of a well-defined input set that will produce corresponding sets of expected output.Output SpecificationsDescription: The Output Specifications section specifies the expected outputs from this test. The output set should include data, timing information, screen messages, logs, databases, memory structures, files, screens, etc. In those cases in which an actual test output can differ slightly from an expected output, include the range of acceptability for the differences for each output.Justification: For each test input set, the project team has defined a corresponding set of expected output. Defining, inspecting, and approving the output set prior to a test enables the team to examine actual test results and quickly determine if a test was successful and in many cases to determine the cause of incorrect output.Test EnvironmentDescription: The Test Environment section describes the test environments characteristics and configuration. This description should include hardware, software, tools, other applications, etc. This description should be sufficiently complete so that the test environment will produce results that ensure the solution will be successful in its operational environment.Justification: Testing requires a test environment that will produce the expected results. In many cases tests require special test environments, and in other cases tests can be conducted in operational environments. Repeating tests requires keeping as many test parameters, such as a test environment, constant. Software inspections and project reviews always examine test environments. Documenting the test environment makes this possible.Special Procedural RequirementsDescription: The Special Procedural Requirements section describes any special requirements to ensure that the test has integrity. This may include setup processes, restoring the environment to known baseline before and after test, and logging or monitoring requirements. Justification: Teams apply testing methods within prescribed testing procedures that may be unique to test cases.Inter-case DependenciesDescription: The Inter-case Dependencies section identifies the dependencies that exist among the test cases, showing which test cases must be performed first and which follow. Justification: Many functions depend upon input data produced as output from other functions previously tested. This section lists those test cases and identifies the test input data each earlier test case provides to this test case.Test CasesDescription: The Test Cases section identifies every unique test case that will be conducted. These may be organized by functions, features, and performance items to be tested.Justification: Teams test each function, each feature, and each performance requirement defined by requirements and functional specifications. This section lists the test items described in detail below.Test Case Item 1Description: The Test Case Item - 1 section identifies the testing item that is the subject of the test case. Feature ADescription: The Feature A section briefly describes the overall feature and its design. Expected BehaviorDescription: The Expected Behavior section describes the features expected behavior as intended by the requirements and design specifications. It also provides a definition of the range of acceptable differences between the expected and actual behavior.Expected PerformanceDescription: The Expected Performance section describes the features expected performance as intended by the requirements and design specifications. It also provides a definition of the range of acceptable differences between the expected and actual performance.Expected ReliabilityDescription: The Expected Reliability section describes the features expected reliability as intended by the requirements and design specifications. It also provides a definition of the range of acceptable differences between the expected and actual performance.Additional Notes/IssuesDescription: Use the Additional Notes/Issues section for any additional information that is not specified in the prior sections.Feature BDescription: The Feature B section briefly describes the overall feature and its design.Expected BehaviorDescription: The Expected Behavior section describes the features expected behavior as intended by the requirements and design specifications. It also provides a definition of the range of acceptable differences between the expected and actual behavior.Expected PerformanceDescription: The Expected Performance section describes the features expected performance as intended by the requirements and design specifications. It also provides a definition of the range of acceptable differences between the expected and actual performance.Expected ReliabilityDescription: The Expected Reliability section describes the features expected reliability as intended by the requirements and design specifications. It also provides a definition of the range of acceptable differences between the expected and actual performance.Additional Notes/IssuesDescription: Use the Additional Notes/Issues section for any additional information that is not specified in the prior sections. Test Case 1 ReferencesDescription: The Test Case 1 References section provides a traceability mechanism from the requirements documents, functional specifications, and other documents (user guides, operations guides, and installation guides) that were used to develop the test case.Test Case 2Description: The Test Case 2 section identifies the testing item that is the subject of the test case.Feature ADescription: The Feature A section briefly describes the overall feature and its design.Expected BehaviorDescription: The Expected Behavior section describes the features expected behavior as intended by the requirements and design specifications. It also provides a definition of the range of acceptable differences between the expected and actual behavior.Expected PerformanceDescription: The Expected Performance section describes the features expected performance as intended by the requirements and design specifications. It also provides a definition of the range of acceptable differences between the expected and actual performance.Expected ReliabilityDescription: The Expected Reliability section describes the features expected reliability as intended by the requirements and design specifications. It also provides a definition of the range of acceptable differences between the expected and actual performance.Additional Notes/IssuesDescription: Use the Additional Notes/Issues section for any additional information that is not specified in the prior sections.Feature BDescription: The Feature B section briefly describes the overall feature and its design.Expected BehaviorDescription: The Expected Behavior section describes the features expected behavior as intended by the requirements and design specifications. It also provides a definition of the range of acceptable differences between the expected and actual behavior.Expected PerformanceDescription: The Expected Performance section describes the features expected performance as intended by the requirements and design specifications. It also provides a definition of the range of acceptable differences between the expected and actual performance.Expected ReliabilityDescription: The Expected Reliability section describes the features expected reliability as intended by the requirements and design specifications. It also provides a definition of the range of acceptable differences betwee