schemaorg_apache_xmlbeans.src.TestSuite.xsd Maven / Gradle / Ivy
The newest version!
The testSuite root element
The testSuite root type
A name for this suite
The base URL of the simulated partners and
client. The framework will extract a port from
this URL; it will also be used for asynchronous
callbacks. The URL should end with a slash;
partnerTrack names will be appended. Default is
http://localhost:7777/ws/
Deployment section of this test suite. Specifies
the PUT and partners
Test case section of this test suite. Specifies
test cases
The test partners of the PUT (this section is not strictly required but
considered good practise to keep track of things).
The deployment section type
The Process Under Test, which will be tested in
this suite.
The PUT deployment information type
WSDL file of the PUT
The name of the put
The type of the put - must be one of the types registered in BPELUnit through the extensions.xml file
A partner deployment information
Location of the defining WSDL file
The testCase section
One test case represents one interaction sequence with the PUT
A testCase
An activity track
Send a message and wait for an ACK.
Receive a message, send an ACK.
Send a message and wait for a qualified
response.
Receive a message, and answer with a
qualified response.
Receive a message, send an ACK, and then
send a qualified asynchronous response and
expect an ACK.
Send a message, expect an ACK, and then wait
for a qualified asynchronous messageand send
an ACK.
An activity track for a partner
If specified, XPath expression (with access to the variables in the partner track context) which must hold for the partner track to be run.
If false, all activities in the partner track will be skipped. Skipped tasks are considered to have passed.
A send activity. Note: delay override and delaySequence are mutually exclusive: if you use both, BPELUnit will report an error.
A send operation
Verbatim XML to be used as the SOAP body
of the message to be sent.
Apache Velocity template to be expanded
to produce the SOAP body.
A receive activity
A receive operation
A reference by id to a condition group defined in the same test suite. The conditions specified in this condition group are also checked at test run like the conditions specified in this activity.
A two-way activity
A (sync or async) two-way operation
Header processor. Can add addressing info to outgoing calls and extract it from incoming calls.
A header processor
Name to look the processor up in the configuration.
A simple property/value type
Wrapper for the XML Any Element
A single activity
A single activity
Mapping type for data copy operations
Copies an input element from the input message to an output element from the output message. Only makes sense in rcv/send operations.
A copy operation
XPath expression on raw XML data
XPath expression on raw XML data
Velocity script to be run before each test case
on the test case VelocityContext.
A condition group is a set of conditions that can be applied to receive activities.