Preparing to Use the Composite Application Validation System 2-11
7.
To obtain the Response Message XML text:
a. Click the reply Output element to get your test definition response message
XML text.
b. Click the Copy details to clipboard link at the bottom of the pop-up box
displaying output Variable data.
c.
Open an XML editor and paste the XML text into a blank document.
d.
Remove the opening and closing inputVariable XYZ_InputVariable, in the case of a non-BPEL service, such as a participating application service
and part elements.
e.
Copy and paste the remaining XML text in the default SOAP envelope provided in the Response Message field on the Test Definition page or
Simulator Definition page.
Note: Obtaining response message XML text is only applicable when
testing a synchronous process.
2-12 Infrastructure Components and Utilities Users Guide
3
Introduction to Defining and Running CAVS Tests Using the CAVS UI 3-1
3
Introduction to Defining and Running CAVS Tests Using the CAVS UI
This chapter includes the following sections:
■
Section 3.1, Describing the CAVS UI
■
Section 3.2, Overview of Defining and Running CAVS Tests
■
Section 3.3, How to Execute CAVS Definitions as Web Services
3.1 Describing the CAVS UI
The Composite Application Validation System CAVS enables you to configure test data, execute tests, review test results, and migrate tests using the following user
interface UI components.
Test Definitions A test definition is a configuration of a single execution of the test initiator service. The
test definition stores test data and test execution instructions. A test definition can be executed alone, or in a single-threaded batch as a part of a group definition.
You will find that the values you set for a test definition and simulator definition are similar. The test definition differs from the simulator definition in that it is an active
participant in the CAVS framework, initiating tests. The test definition carries the following values that are not a part of the simulator definition. These values inform
the active state of the test definition:
■
Endpoint URL
■
SOAP Action For more information about test definitions, see
Chapter 4, Creating and Modifying Test Definitions.
If required by the business service pattern of the web service you are testing, you can assign a simulator definition to the test definition.
Simulator Definitions A simulator definition is a configuration of a single execution of response simulator
service. The simulator definition simulates a web service and receives data from the tested web service and returns previously defined data so that the tested web service
can continue processing.
3-2 Infrastructure Components and Utilities Users Guide
You will find that the values you set for a simulator definition and test definition are similar. The simulator definition differs from the test definition in that it is a passive
participant in the CAVS framework, awaiting initiation.
The simulator definition carries the following additional XPath attributes that are not a part of the test definition. These values participate in simulator definition request
matching:
■
Is Node Key
■
Key Node Value For more information about simulator definitions, see
Chapter 5, Creating and Modifying Simulator Definitions.
The success of the test is verified based on the simulator definitions previously defined data being accurately returned and matched to the expected response results
defined in the test definition.
Group Definitions A group definition is a configuration of a single execution of one or more test
definitions in a single-threaded batch.
Test Instances A test instance captures the details of the execution of a test definition.
Simulator Instances A simulator instance captures the details of a simulator definitions behavior during
the execution of a test definition with which it is associated.
Group Instances A group instance captures the details of the execution of a group definition.
Component Overview
Figure 3–1 provides a high-level overview of the relationships among the CAVS
components discussed in this section.
Figure 3–1 Overview of CAVS Component Relationships
Introduction to Defining and Running CAVS Tests Using the CAVS UI 3-3
3.2 Overview of Defining and Running CAVS Tests