Agile Test Summary Report Template, Study Guides, Projects, Research of Designs and Groups

Download Agile Test Summary Report Template and more Study Guides, Projects, Research Designs and Groups in PDF only on Docsity! Agile Test Summary Report Template Introduction The following pages of this document contain a Test Summary Report template, which may be copied and used as the basis of a Test Summary Report for a particular iteration or phase of the test project. Where text appears within the body of this template in angle brackets (< >), this denotes a place marker, which must be replaced with the appropriate information for a particular testing phase. Text, which appears in italic, is provided for information only (such as illustrative examples), and should not appear in the final Test Summary Report. Test Summary Report Document Information {to <Client> Doc Standard} Project ID: <Project ID> the unique ID for this testing project Document Ref: <Doc Ref> a unique document reference for this document Iteration ID: <Iteration ID> the unique iteration ID AUT Title: <AUT Title> the definitive title of the application under test Date: <Date> the date this document was completed Distribution Copy Number Recipient 1. <recipient 1> 2. <recipient 2> 3. <recipient 3> etc. • Section 7 provides a summary of the major testing activities and events for the <Iteration ID> testing of the <AUT Title> 1.3 References A list of documents referenced within this Test Summary Report document. 2 Overview This section provides a high level overview of the significant events and activities documented during the <Iteration ID> testing of the <AUT Title>. This section also specifies the scope of the testing (what was and what was not tested), and specifying the test environment details (including the hardware, software and data used in the testing). For Example: The Iteration 02-Team-Org-Chart-01 Test for the CTS Wiki (v1.0, 2008) was begun on July 7th 2008 and completed on July 8th 2008. During this testing only the CTS Org Chart section of the Wiki was considered. The testing was conducted on an IBM T60 Laptop with 4Gbytes of memory running Microsoft Windows XP Professional V2002 SP2. 3 Variances This section is used to record any variances of the artefacts from those areas agreed on previously, especially in areas that may cause concern to the group accepting the test results, including any references to supporting documentation that covers the reasons for the deviations. For Example: Conditions observed during the course of testing resulted in the design of additional test cases to explore concerns regarding the CTS Wiki Org Chart Legibility. A number of additional defects were identified as a result, which were subsequently corrected and successfully re- tested. 4 Assessment This section provides a brief assessment of the comprehensiveness of the testing process for the completed testing phase against the test objectives and constraints specified in the Test Plan document. Where code coverage measurements have been made, the results should also be included in this section. This section also identifies any aspects of the AUT that were not tested as thoroughly as planned (due to insufficient time or resources). For Example: All Test Cases were executed with the exception of Test Cases 02-Team-Org-Chart-04 and 02- Team-Org-Chart-05 (testing the CTS Wiki Org Chart Navigation), which were omitted due to challenging testing timescales combined with the need to further investigate concerns associated with the CTS Wiki Org Chart Legibility. 5 Results This section provides a summary of the results of the <Iteration ID> testing of the <AUT Title>, identifies all resolved issues and summarises the details of their resolution, and lists any outstanding issues. For Example: Test Case 02-Team-Org-Chart-03 revealed problems with the legibility of the CT Wiki Org Chart (and in particular potential issues with Red-Green perceptually challenged users). The developers corrected the observed defects and the amended code passed the re-test. However, it was not possible within the time scales of the testing task to regression test the associated navigation requirements. This issue remains outstanding, and should be observed following installation and use in the live environment.