Have you ever made a small change to a really complex service on a tight timeline hoping and praying you didn’t inadvertently hatch any new bugs while fixing your current one? If so, you’ll find that this pattern is a much better way to calm your nerves rather than a prescription from your doctor. This is because a framework that supports automated testing can quickly exercise every possible scenario in your service without being shackled to actual databases, web services, messaging queues or other external dependencies. In Part 1 of this series we discuss how to ensure that our project is set up in a modular way that will enable easy testing. Whenever your project requires calls to an external dependency such as a database, web service or messaging queue the best practice is to use a product like Oracle Service Bus to manage these interactions. However, if you don’t have a license to OSB like many shops I’ve encountered, you should utilize the Integration Service Pattern instead.
Receive a $500 discount for AVIO's Self Paced Oracle BPM 11g Developer Workshop with discount code "OOW2013". This offer is valid until Oracle OpenWorld 2013 concludes.