Guidelines and suggested best practices for users of IBMĀ® RationalĀ® Test Workbench and Rational Test Virtualization Server
This document presents guidelines and suggested best practices for users of IBM Rational Test Workbench and Rational Test Virtualization Server, the IBM products that support Automated Integration Testing and Service Virtualization. A key component of Rational Test Workbench is Rational Integration Tester, the target of much of this document, but other components are given treatment as well.
Automated Integration Testing (also known as Sub-GUI testing) enables the injection of requests to interfaces or services, via the same technologies used by other consumers of that interface. The automation of this level of testing is a very strong accelerator for software testing ā and at the same time provides a terrific opportunity to increase the quality of software applications.
Service Virtualization is a technology and approach that can replace a live service with a software āresponderā, which consumes a tiny fraction of the resources that most live services would require. At the same time, this Virtual Service should be indistinguishable in operation from the live service for the test scenarios that the Virtual Service was designed to manage.
Before starting, thereās one overarching concept that should be addressed first. The System Under Test (SUT) is the program or function that must be tested. You never want to pretend to be (to ‘virtualize away’) the actual function you are testing – the code you have produced ā or you would never find all the bugs – this is a core idea that will be revisited throughout this guide.
Please note that while these are peer-reviewed best practices, some are necessarily a bit arbitrary. Your decisions will be more informed after reviewing this document, but your decisions are your own.
Lastly, the footnote URLs that are āshortenedā in this document all refer to IBM web sites. All other URLs are full URLs, in consideration for those who are sensitive to security.