Databases Reference
In-Depth Information
Composite testing
The problem with the system test is that it may fail for many reasons and often
those reasons are unclear. Composite level testing allows us to isolate the individual
composites and test them against their specifications. To do this, we inject requests
from the client and emulate the references used by the composite, so that we have
complete control over all interactions between the composite and the references it
interfaces with.
This type of testing is good for identifying defects in the composite, but must be treated
with care, as individual services may behave differently from the emulated versions of
those services. Testing of a composite is shown in the following diagram:
Component testing
The framework was designed for testing composites, but it may also be used to
provide a test harness for individual services, as shown in the following diagram. In
this case, a pass-through assembly is provided that allows injection of messages into
the service. The BPEL
Composite
and the
Service
are then configured with suitable
assertions to ensure that the service is behaving as expected.
