Test-driven development in an SOA environment, Part 2: Continuous integration with WebSphere Process Server

From the developerWorks archives

Donald Vines

Date archived: November 22, 2016 | First published: December 10, 2008

Part 1 of this series focused on using Cactus to write test cases for SCA data maps before writing the SCA business processes in IBM® WebSphere® Integration Developer. Part 2 looks at using CruiseControl as the continuous integration server to monitor the SCA artifacts in the CVS repository and run the test cases on IBM WebSphere Process Server whenever there are changes. This content is part of the IBM WebSphere Developer Technical Journal.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Business process management, WebSphere, SOA and web services
ArticleID=357725
ArticleTitle=Test-driven development in an SOA environment: Part 2: Continuous integration with WebSphere Process Server
publish-date=12102008