I would like to see the existing test harness in ODE expanded to support more robust unit testing. The bpel-test project in the ode trunk is a good start. The default implementation of the MessageExchangeContext interface supports a simple probe service and a fault service. This concept could be expanded to include assertions on the data passed to the MessageExchangeContext as well as returning preconfigured responses. This interface alone would give you the hook you'd need to handle invokes. I'm not sure what facilities ODE has in place to control the scheduling of alarms but that's another area which could offer assertions as well as changing the actual value for the alarm (you might not want your bpel to have the full value for the wait/onAlarm during testing). I think the existing harness already supports multiple inbound messages but I'm not sure about how they're delivered.
On 2/25/09 11:47 AM, "Rafal Rusin" <[email protected]> wrote: Hello, what do you think of implementing a command line tool bpelrun, which could compile and run a process by sending a request from stdin and displaying response to stdout. This would speed up testing of various bpel constructs. It would be helpful in developing larger processes by copy-pasting from small examples. It could be also useful to do bpel unit testing. -- Rafał Rusin www.mimuw.edu.pl/~rrusin -- Mark Ford MIT Lincoln Laboratory 244 Wood Street Lexington MA 02420 (781) 981-1843
