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
E - Test Script 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 Script template that may be copied and used to record the information necessary for conducting each test comprising a particular testing phase.
A completed example of a Test Script (Figure E.1) is also included for guidance.
For each test, a separate Test Script will need to be completed by the Test Analyst. Each Test Script contains the following sections:
▲ 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)
▲ Date of Test – the planned start date of testing (front sheet only)
▲ Test ID – the unique identifier for the test
▲ Purpose of Test – a brief description of the purpose of the test, including a reference, where appropriate, to the requirement that is to be tested (consider providing references to the requirements specification, design specification, user guide, operations guide and/or installation guide), as well as any dependencies from or to other Test Scripts/Test Cases
▲ Test Environment – a brief description of the environment under which the test is to be conducted (may include a description of the state of the AUT at the start of this test, details regarding the platform or operating system, as well as specific information about data used in this test)
[…]
- Type
- Chapter
- Information
- Testing ITAn Off-the-Shelf Software Testing Process, pp. 231 - 236Publisher: Cambridge University PressPrint publication year: 2001