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
8 - Systems Integration 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
There has never been an unexpectedly short debugging period in the history of computing
Steven Levy, “Hackers”Overview
The objective of Systems Integration Testing is to provide confidence that the Application Under Test (AUT) is able to interoperate successfully with other specified software systems and does not have an adverse affect on other systems that may also be present in the live environment, or vice versa. Systems Integration Testing is conducted by the Testing Team under the supervision of the Test Team Leader. Systems Integration Testing may also be termed Compatibility Testing, or simply Integration Testing (as it is termed in the British Library Testing Process, for example – see Chapter 14).
It is possible that the testing tasks performed during Systems Integration Testing may be combined with System Testing, particularly if the AUT has little or no requirement to interoperate with other systems.
Systems Integration Testing should employ Black Box techniques and will test the high-level interoperability requirements of the AUT without considering the internal construction of the AUT (for example, testing business processes and complete transactions that require intersystem communication or interaction). The use of Negative Testing and Error Guessing techniques (see Chapter 3) are particularly appropriate during Compatibility Testing for the purposes of uncovering any unanticipated problems.
In terms of the V Model, Systems Integration Testing corresponds to the Specification phase of the software development lifecycle (Figure 8.1).
- Type
- Chapter
- Information
- Testing ITAn Off-the-Shelf Software Testing Process, pp. 65 - 72Publisher: Cambridge University PressPrint publication year: 2001