Describing the Purpose of the Composite Application Validation System

1 Introduction to the Composite Application Validation System 1-1 1 Introduction to the Composite Application Validation System The Composite Application Validation System CAVS is a framework that provides a structured approach to test integration of Oracle Application Integration Architecture AIA services. The CAVS includes test initiators that simulate web service invocations and simulators that simulate service endpoints. This chapter includes the following sections: ■ Section 1.1, Describing the Purpose of the Composite Application Validation System ■ Section 1.2, Describing Key Components of the CAVS Framework ■ Section 1.3, Describing the CAVS Design Assumptions and Knowledge Prerequisites

1.1 Describing the Purpose of the Composite Application Validation System

In the context of AIA, where there is a sequence of service invocations; spanning Application Business Connector Services ABCSs, Enterprise Business Services EBSs, Enterprise Business Flows EBFs, and participating applications; the CAVS test initiators and simulators enable a layered testing approach. Each component in an integration can be thoroughly tested without having to account for dependencies by using test initiators and simulators on either end. Consequently, when you build an integration, you have the ability to add new components to an already tested subset, allowing any errors to be constrained to the new component or to the interface between the new component and the existing component. This ability to isolate and test individual web services within an integration provides the benefit of narrowing the test scope, thereby distancing the service test from possible faults in other components. Test initiators and simulators can be used independent of each other, thereby allowing users to effectively substitute them for non-available AIA services or participating applications. The CAVS provides a repository that stores these test initiator and simulator definitions created by the CAVS user, as well as an interactive user interface to create and manage the same. Tests can be configured to run individually or in a single-threaded batch. The CAVS provides value as a testing tool throughout the integration development life cycle: 1-2 Infrastructure Components and Utilities Users Guide ■ Development Because integration developers working with AIA are dealing with integrating disparate systems, they typically belong to different teams. To this end, the CAVS provides an effective way to substitute dependencies, letting developers focus on the functionality of their own service rather than being preoccupied with integrations to other services. ■ Quality assurance The CAVS allows quality assurance engineers to unit and flow test integrations, thereby providing a way to easily certify different pieces of an integration. The reusability of test definitions, simulators, and test groups helps in regression testing and provides a quick way to certify new versions of services.

1.2 Describing Key Components of the CAVS Framework