New Features in BPELUnit (HTTP Headers, 2 WSDL/partner, XML File import, Condition Groups)

[Daniel Luebke]

Hi,

in the last days I pushed some days to the BPELUnit git repository.
The first two features have been discussed a while ago, the third and
forth are new:
1. HTTP Header Support: BPELUnit can now send user-defined HTTP
headers, e.g. for authenticating a Web service call,
2. Two WSDLs per Partner: BPELUnit can now support two WSDL references
for a partner definition thereby allowing to use two different
services for the partner and reflecting BPEL's partner link concept
for a service provided by the process and a call-back service for the
partner
3. XML File references for outgoing data: BPELUnit can now "import"
XML files for the send part of an activity. Instead of the XML data
contained in the <data> element, the XML file is read and the data is
send as part of the activity.
4. Condition Groups: Conditions can be grouped in a condition group
and reused for multiple receives.

For the first two features the UI is already present in the tool
support project. For 3. and 4. it is missing for now.

I hope that these features are useful (they are born out of my own
project requirements) and welcome any feedback.

Daniel

[Antonio García Domínguez]

Hi Daniel,

Thanks for your hard work :-).

2011/10/31 Daniel Luebke <daniel...@gmail.com>

> 2. Two WSDLs per Partner: BPELUnit can now support two WSDL references
> for a partner definition thereby allowing to use two different
> services for the partner and reflecting BPEL's partner link concept
> for a service provided by the process and a call-back service for the

> partner.

This should be quite useful for us as well: we have to test some
asynchronous services and the old approach with BPELUnit (using two
different partner tracks) was a bit of a hack.

> 3. XML File references for outgoing data: BPELUnit can now "import"
> XML files for the send part of an activity. Instead of the XML data
> contained in the <data> element, the XML file is read and the data is
> send as part of the activity.

I like the idea. However, I'd prefer adding a src="my.xml" attribute
to <tes:data>, to be consistent with the syntax for the data sources
(either embedded inside the XML element, or linked through a src
attribute). We could do the same for the templates, using the same
src="my.vtl" attribute.

> 4. Condition Groups: Conditions can be grouped in a condition group
> and reused for multiple receives.

Nice idea as well, and I like the format too!

Antonio

[Daniel Luebke]

Hi,

today I pushed some changes to my private repo at
g...@github.com:dluebke/BPELUnit.git

I added condition group inheritance (only single parent group, check
for cyclic inheritance)

During this I also refactored the code that checks the bpts file. I
extracted it out from SpecificationLoader into a set of classes
implementing ITestSuiteValidator. This makes the SpecificationLoader a
bit leaner (it is still class too large) and make different validator
classes checking for different aspects (XML Schema validation, checks
for required fields extracted out from SpecificationLoader, and the
cyclic check for condition groups.) However, the middle one could be
split up into more parts and I think that there are checks that are
already covered by the schema validator.

However, this lead to an interesting side effect: Some end-to-end
tests for the templates failed because one tag is always shortened
from <a></a> to <a/> and thus the textual comparison fails. I
@ignore'ed these tests. I don't know yet why this happens.

In addition, I now added a validation rule that checks whether a
partner track in a test case is declared in the deployment section.
This broke some test suite files in the tests directory which I fixed
accordingly.

Due to the points illustrated in the last two paragraphs I only pushed
my changes to my private repo. I appreciate any feedback on this.

For my remarks regarding Antonio's remark see inline below.

Daniel


On 31 Okt., 19:20, Antonio García Domínguez <nyoesc...@gmail.com>
wrote:

> Hi Daniel,
>
> Thanks for your hard work :-).

Thanks :-)

[...]

[Daniel Luebke]

Hi,

I pushed some new updates to my private branch.

New and changes features:
- All XMLAnyElements (like in send, templates, WS-HT tasks) are now
having an optional src-attribute. The logic for importing files is now
generic and centralized in the SpecificationLoader
- Many fixes
- New preference page in Eclipse listing all registered deployers,
data sources etc. and their options.
- improved labels in Eclipse editor showing the operation name for
better development of tests

And probably many small improvements...

Feedback is as always welcome :-)

Daniel