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
D - Test Specification Document 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 template for a Test Specification Document, guidance on its use, and where appropriate, examples of the typical contents of such a document. This template may be used as the basis of a Test Specification document for a particular test phase.
As described in Chapter 4 (The Management and Planning of Testing), each testing project must generate a Test Specification as one of the documents produced prior to the commencement of the testing activities.
Where text appears within the body of the 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 Specification Document.
Where references to “Appendices” appear within this appendix, these refer to other appendices in this book. The term “Annex” is used to refer to supplementary sections within this template.
The principal approach to be used in writing a Test Specification Document is to keep it brief and simple. Make best use of the supporting information presented in this book (such as the other relevant template appendices), as well as pertinent material from the appropriate testing phase chapters.
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 can be obtained from the Testing Manager or equivalent role).
- Type
- Chapter
- Information
- Testing ITAn Off-the-Shelf Software Testing Process, pp. 221 - 230Publisher: Cambridge University PressPrint publication year: 2001