Version 1.6.0 has been released, with the following changes:

• Change: BPELUnit uses a different HTTP connection for each sendReceive activity. This ensures sendReceive activities are kept separate from each other and avoids race conditions.
• Change: the <script> in a test case <setUp> block is now run after loading the current row of the data source, so it can access its variables as well.
• Change: upgraded Velocity to 1.7 and integrated Velocity Tools 2.0 into the templates.
• Feature: <send> and <sendOnly> accept the new delay attribute, which contains an XPath expression that computes the delay to be used. The XPath expression can use variables in the data source. The old delaySequence attribute is still supported. However, it is forbidden to use delay and delaySequence in the same activity.
• Feature: The XPath expression in a <condition> can be generated by replacing the fixed <expression> element with a Velocity template in a <template> element.
• Feature: Support for setting HTTP headers on outgoing SOAP/HTTP connections.
• Feature: Support for having two WSDLs per partnerlink so that BPEL partner link types can be better imitated.
• Feature: Support for condition groups. Allows reuse of conditions across different receives.
• Feature: <data> and <template> in <send> can use the src attribute to load an XML document or Velocity template from a separate file.
• Feature: templates can use the new printer predefined context variable to print DOM elements back as XML.