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
H - Test Certificate 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 specimen test certificate, which may be customized and used to formally record the successful completion of a specific test phase for a particular Application Under Test (AUT).
Although it is unlikely that a test certificate will be used to formally record the successful completion of the earlier phases of the testing process, in any formal acceptance of an AUT, and in particular involving a third-party developer or supplier, the use of such a certificate should be mandatory.
When customizing the specimen test certificate template for a particular AUT under a specific testing phase, the following information should be considered for inclusion within the test certificate:
▲ The title of the AUT
▲ The Test Phase name
▲ A Statement of Acceptance describing the circumstances of the test, its date (and optionally, its location), and what the AUT has been tested against
▲ The signature of the staff member accepting the tested AUT (must be a senior level, particularly for acceptance of third-party developed systems or products). The signature should be dated.
▲ The signature of the Independent Test Observer (this item may not be appropriate for an Acceptance Test where the system has been supplied by a third-party organization). The signature should be dated.
▲ The signature of the Supplier or Developer (these need not be the representatives of a third-party organization—for example, the AUT may have been developed in-house, with a suitably senior representative of the development project signing). The signature should be dated.
- Type
- Chapter
- Information
- Testing ITAn Off-the-Shelf Software Testing Process, pp. 245 - 246Publisher: Cambridge University PressPrint publication year: 2001