Book contents
- Frontmatter
- Contents
- Foreword
- Acknowledgments
- Testing IT
- 1 Introduction
- Part 1 The Traditional Testing Process
- Part 2 The Testing Process in the Real World: Illustrative Case Studies
- Part 3 The Appendices
- A Terms of Reference for Testing Staff
- B Testing Guides
- C Test Plan Document Template
- D Test Specification Document Template
- E Test Script Template
- F Test Result Record Form Template
- G Test Log Template
- H Test Certificate Template
- I Re-use Pack Checklist
- J Test Summary Report Template
- K Equivalence Partition Example
- L Boundary Analysis Example
- M State Transition Example
- N Automated Testing Tool Selection Criteria
- O Usability Testing Overview
- P Testing Process Health Check
- Q The Testing of Object-Oriented Software
- References
- Glossary
- Index
J - Test Summary Report Template
Published online by Cambridge University Press: 06 September 2009
- Frontmatter
- Contents
- Foreword
- Acknowledgments
- Testing IT
- 1 Introduction
- Part 1 The Traditional Testing Process
- Part 2 The Testing Process in the Real World: Illustrative Case Studies
- Part 3 The Appendices
- A Terms of Reference for Testing Staff
- B Testing Guides
- C Test Plan Document Template
- D Test Specification Document Template
- E Test Script Template
- F Test Result Record Form Template
- G Test Log Template
- H Test Certificate Template
- I Re-use Pack Checklist
- J Test Summary Report Template
- K Equivalence Partition Example
- L Boundary Analysis Example
- M State Transition Example
- N Automated Testing Tool Selection Criteria
- O Usability Testing Overview
- P Testing Process Health Check
- Q The Testing of Object-Oriented Software
- References
- Glossary
- Index
Summary
Introduction
This appendix contains a Test Summary Report template, which may be copied and used as the basis of a Test Summary Report for a particular testing phase. The purpose of a Test Summary Report is to summarize the result of a particular testing phase and to provide the basis for subsequent improvement of the testing process.
As described in Chapter 4 (The Management and Planning of Testing), each testing project must generate a Test Summary Report as one of the documents produced at the conclusion of any given testing phase.
The principal approach to be used in writing a Test Summary Report is to try to produce a short, succinct document. Make best use of the supporting information presented in this book (such as the other relevant templates), as well as pertinent material from the appropriate testing phase chapters.
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 that appears in italic type is provided for information only (such as illustrative examples), and should not appear in the final Test Summary Report.
An electronic version of the template is available from the following URL: <us.cambridge.org/titles/052179546X> (or, assuming the role has been implemented, a copy may be obtained from the Testing Manager or equivalent role).
- Type
- Chapter
- Information
- Testing ITAn Off-the-Shelf Software Testing Process, pp. 249 - 254Publisher: Cambridge University PressPrint publication year: 2001