Book contents
- Frontmatter
- Contents
- Foreword to the Second Edition by Geoff Thompson
- Foreword to the First Edition by Maurice Rosenburgh
- Acknowledgments
- 1 Introduction
- PART 1 THE TRADITIONAL TESTING PROCESS
- PART 2 THE TESTING PROCESS IN THE REAL WORLD: ILLUSTRATIVE CASE STUDIES
- PART 3 THE APPENDICES
- Appendix A Terms of Reference for Testing Staff
- Appendix B Testing Guides
- Appendix C Test Plan Document Template
- Appendix D Test Specification Document Template
- Appendix E Test Script Template
- Appendix F Test Result Record Form Template
- Appendix G Test Log Template
- Appendix H Test Certificate Template
- Appendix I Reuse Pack Checklist
- Appendix J Test Summary Report Template
- Appendix K Equivalence Partition Example
- Appendix L Boundary Value Analysis Example
- Appendix M State Transition Example
- Appendix N Pairwise Testing Example
- Appendix O Automated Testing Tool Selection Criteria
- Appendix P Usability Testing Overview
- Appendix Q Testing Process Health Check
- Appendix R The Testing of Object-Oriented Software
- Appendix S Pragmatic Test Process Adoption – a Real-World Example
- References
- Glossary
- Index
Appendix H - Test Certificate Template
Published online by Cambridge University Press: 03 May 2011
- Frontmatter
- Contents
- Foreword to the Second Edition by Geoff Thompson
- Foreword to the First Edition by Maurice Rosenburgh
- Acknowledgments
- 1 Introduction
- PART 1 THE TRADITIONAL TESTING PROCESS
- PART 2 THE TESTING PROCESS IN THE REAL WORLD: ILLUSTRATIVE CASE STUDIES
- PART 3 THE APPENDICES
- Appendix A Terms of Reference for Testing Staff
- Appendix B Testing Guides
- Appendix C Test Plan Document Template
- Appendix D Test Specification Document Template
- Appendix E Test Script Template
- Appendix F Test Result Record Form Template
- Appendix G Test Log Template
- Appendix H Test Certificate Template
- Appendix I Reuse Pack Checklist
- Appendix J Test Summary Report Template
- Appendix K Equivalence Partition Example
- Appendix L Boundary Value Analysis Example
- Appendix M State Transition Example
- Appendix N Pairwise Testing Example
- Appendix O Automated Testing Tool Selection Criteria
- Appendix P Usability Testing Overview
- Appendix Q Testing Process Health Check
- Appendix R The Testing of Object-Oriented Software
- Appendix S Pragmatic Test Process Adoption – a Real-World Example
- References
- Glossary
- Index
Summary
Introduction
This appendix contains a specimen test certificate template, which may be customized and used to formally record the successful completion of a specific test phase for a particular application under test (AUT). An electronic version of the template can be obtained using the following link: http://www.cambridge.org/9780521148016.
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 from 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 member of staff accepting the tested AUT (must be of an appropriate level of seniority, particularly for acceptance of third-party bespoke 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. 256 - 258Publisher: Cambridge University PressPrint publication year: 2010