By Juergenkress-Oracle on May 22, 2015
As in all software projects, quality assurance with thorough testing in integration projects is a key factor to success. Test-driven development focuses exactly on this aspect: unit and integration testing of integration elements must be done as soon as possible. The tests used in these phases must also be reproducible so that they can be run automatically in case of changes in the integration logic, thus guaranteeing that no unintended changes are made.
Oracle SOA/BPM Suite is a powerful tool suite for integration. This article shows how test-driven development can be done with the Oracle tooling. Integration elements built with Oracle SOA/BPM Suite are SCA composites made up of several components. Since mainly the integration layer is concerned, there is quite often heavy usage of external web services, database adapters, etc. The composites also usually have an inbound interface the invocation of which is the starting point of the integration logic.
it can be seen from above, the key to testing SCA composites is to
define an inbound message and assert the data found in various other
messages during the integration logic. Some easy scenarios can instantly
be identified. XSLT transformations within the composites can be
unit-tested without the complete logic itself for example. Likewise,
end2end testing is also easily done – at least for a web service
interface – thus assuring at least that the result is what we expected.
The problem is that for end2end testing, the correct functionality of
back-end systems is a prerequisite. If the back-end functionality is
developed parallel to the integration logic, end2end testing is far away
from test-driven development. Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.