Creating and Modifying Simulator Definitions 5-9
Test Definition Selection Select the Test Definitions tab to display the Linked Test Definition Selection grid,
which displays information about test definitions associated with the simulator definition.
Available elements in the Linked Test Definition Selection grid are discussed in Table 5–7
.
5.3 How to Provide Multiple Request and Response Message Sets in a Single Simulator Definition
You can create a simulator definition that contains multiple pairs of request and response message data, as shown in
Figure 5–8 . This means that simulator definitions
only need to be created per usage requirements, not per test data requirements.
Figure 5–8 Providing Multiple Request and Response Message Sets in a Single
Simulator Definition
Status Displays the status of the simulator instance generated by the simulator
definition.
■
Initiated: The simulator instance has been initiated.
■
Ended: This status is only applicable to simulator instances that do not involve validations. Indicates that the instance has ended.
■
Faulted: The simulator instance could not execute properly due to exceptions or faults.
■
Failed: The simulator instance did not pass validation.
■
Passed: The simulator instance passed validation. Start Date
Displays the date and time at which the simulator instance was initiated.
End Date Displays the date and time at which the simulator instance ended.
Table 5–7 Linked Test Definition Selection Grid
Element Description
Delete Select one or more test definition rows that you want to delete and click
Delete
to execute the deletion. Assign
Click to access the Search Definitions - Test page, where you can search for a test definition to which you want to assign the simulator
definition. Refresh
Click to refresh the Modify Simulator Definition page.
Table 5–6 Cont. Simulator Instance Selection Grid
Element Description
5-10 Infrastructure Components and Utilities Users Guide
For example, if you want to simulate a service against five sets of test data, you can create a single simulator definition to simulate the service and include in it all five sets
of test data with which you can the service to operate. This is as opposed to creating five separate simulator definitions, one per combination of service and set of test data.
When a simulator definition that includes multiple test data sets is invoked, the appropriate data set is matched for use based on key attributes identified in the
request. At this point, the request validation and response provision can occur. Since we would typically use such definitions to handle several sets of data, it is
recommended that you choose the same key values for every set of data.
Request Message Format Use the format provided in
Example 5–1 to include multiple sets of request data in the
simulator definition. The CAVSRequestInputs and CAVSRequestInput_1 envelopes are autogenerated
upon the input of the endpoint URL value on the test definition. Use copy and paste commands to create more sets, such as CAVSRequestInput_2 and
CAVSRequestInput_3.
Example 5–1 Request Message Format
cavs:CAVSRequestInputs xmlns:cavs=http:schemas.xmlsoap.orgcavsrequestenvelope
cavs:CAVSRequestInput_1 soap:Envelope xmlns:soap=http:schemas.xmlsoap.orgsoapenvelope
soap:Body xmlns:ns1=http:xmlns.oracle.comSimpleProcess ns1:SimpleProcessProcessRequest
. . . ns1:SimpleProcessProcessRequest
soap:Body soap:Envelope
cavs:CAVSRequestInput_1
cavs:CAVSRequestInput_2 soap:Envelope xmlns:soap=http:schemas.xmlsoap.orgsoapenvelope
soap:Body xmlns:ns1=http:xmlns.oracle.comSimpleProcess ns1:SimpleProcessProcessRequest
. . . ns1:SimpleProcessProcessRequest
soap:Body soap:Envelope
cavs:CAVSRequestInput_2 cavs:CAVSRequestInputs
Response Message Format Use the format shown in
Example 5–2 to include multiple sets of response data in the
simulator definition.
Example 5–2 Response Message Format
cavs:CAVSResponseOutput_1 soap:Envelope xmlns:soap=http:schemas.xmlsoap.orgsoapenvelope
soap:Body xmlns:ns1=http:xmlns.oracle.comSimpleProcess ns1:SimpleProcessProcessResponse
. . . ns1:SimpleProcessProcessResponse
soap:Body
Creating and Modifying Simulator Definitions 5-11
soap:Envelope cavs:CAVSResponseOutput_1
cavs:CAVSResponseOutput_2 soap:Envelope xmlns:soap=http:schemas.xmlsoap.orgsoapenvelope
soap:Body xmlns:ns1=http:xmlns.oracle.comSimpleProcess ns1:SimpleProcessProcessResponse
. . . ns1:SimpleProcessProcessResponse
soap:Body soap:Envelope
cavs:CAVSResponseOutput_2 cavs:CAVSResponseOutputs
Envelope text is prepopulated. Enter actual message content within appropriate tags provided within the envelopes.
After entering request and response data sets and clicking the Generate Xpath button on the Modify Simulator Definition page, the XPath Selection grid provides access to
available XPath values and enables you to select the XPaths that must be treated as key nodes.
For more information about the Modify Simulator Definition page, see Section 5.2,
How to Modify a Simulator Definition. If your testing scenario includes test definitions, you can likewise create test
definitions that contain multiple request and response message sets that work with the sets defined in your simulator definition.
For more information, see Section 4.3, How to Provide Multiple Request and
Response Message Sets in a Single Test Definition.
5.4 How to Create a Simulator Definition that Supports Chatty Services
