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
G - Test Log 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 Log, which may be copied and used to record the activities and events comprising a particular test phase. An electronic version of the template is available from the following URL: <us.cambridge.org/titles/052179545X> (or, assuming the role has been implemented, a copy may be obtained from the Testing Manager or equivalent role).
The purpose of a Test Log is to document the chronological record of all relevant details of a testing project (in effect, a Test Log is a diary of all relevant events that have occurred during the testing project).
The Test Log forms part of the formal documentation associated with the testing project and will be filed at the completion of the testing project.
The Test Log template presented on the following pages is based on that found in Reference 1, with additional information from Reference 15, plus extensive feedback obtained firsthand in implementing Testing Frameworks for a number of clients (see the Case Study section of this book).
Two different Test Log pages are presented on successive pages:
▲ Test Log front sheet
▲ Test Log continuation sheet.
The information that needs to be filled in on the Test Log includes:
▲ Project ID – the unique project identifier
▲ AUT Title – the definitive title of the Application Under Test (front sheet only)
▲ AUT Version – the definitive version information for the AUT (front sheet only)
▲ Testing Phase – the title of the phase of testing being conducted (e.g., Unit Test, Integration Test, System Test) (front sheet only)
[…]
- Type
- Chapter
- Information
- Testing ITAn Off-the-Shelf Software Testing Process, pp. 241 - 244Publisher: Cambridge University PressPrint publication year: 2001