Book contents
- Frontmatter
- Contents
- Foreword
- Acknowledgments
- Testing IT
- 1 Introduction
- Part 1 The Traditional Testing Process
- 2 An Overview of Testing
- 3 Testing Techniques
- 4 The Management and Planning of Testing
- 5 Unit Testing
- 6 Integration Testing
- 7 System Testing
- 8 Systems Integration Testing
- 9 User Acceptance Testing
- 10 Operations Acceptance Testing
- 11 Regression Testing
- 12 Improving the Testing Process
- 13 Introduction, Adoption, and Maintenance of the Testing Process
- Part 2 The Testing Process in the Real World: Illustrative Case Studies
- Part 3 The Appendices
- References
- Glossary
- Index
10 - Operations Acceptance Testing
Published online by Cambridge University Press: 06 September 2009
- Frontmatter
- Contents
- Foreword
- Acknowledgments
- Testing IT
- 1 Introduction
- Part 1 The Traditional Testing Process
- 2 An Overview of Testing
- 3 Testing Techniques
- 4 The Management and Planning of Testing
- 5 Unit Testing
- 6 Integration Testing
- 7 System Testing
- 8 Systems Integration Testing
- 9 User Acceptance Testing
- 10 Operations Acceptance Testing
- 11 Regression Testing
- 12 Improving the Testing Process
- 13 Introduction, Adoption, and Maintenance of the Testing Process
- Part 2 The Testing Process in the Real World: Illustrative Case Studies
- Part 3 The Appendices
- References
- Glossary
- Index
Summary
If a man will begin with certainties, he shall end in doubts; but if he will be content to begin with doubts, he shall end in certainties
Francis BaconOverview
The objective of Operations Acceptance Testing is to confirm that the Application Under Test (AUT) meets its operations requirements, and to provide confidence that the system works correctly and is usable before it is formally “handed over” to the operations user. Operations Acceptance Testing is conducted by one or more Operations Representatives with the assistance of the Test Team.
Operations Acceptance Testing is considered distinct from User Acceptance Testing, which is used to verify that the AUT meets its business requirements, and to provide confidence that the system works correctly and is usable before it is formally “delivered” to the end user. In practice, where the AUT supports simple administrative facilities, Operations and User Acceptance Testing are often combined into a single testing exercise. Also see Chapter 9, User Acceptance Testing.
Operations Acceptance Testing should employ a Black Box approach to testing, and should make use of Thread Testing techniques to verify the high-level operations requirements of the system. In practice, the Operations Representatives will test the AUT by performing typical tasks that they would perform during their normal usage of the system.
Operations Acceptance Testing should also address the testing of the system documentation (such as operations guides) by the Operations Representative.
- Type
- Chapter
- Information
- Testing ITAn Off-the-Shelf Software Testing Process, pp. 81 - 88Publisher: Cambridge University PressPrint publication year: 2001