|
|
|
|
|
|
|
|
|
|
Considered constraints to test
In our context, conformance testing concerns the functional behaviour of BPEL compositions, and addresses also non-functional properties particularly the necessary time to perform a certain action.
- Considered functional constraints:
A Web service composition is a flow of interactions between a central service (composed service) and its partner services. During these interactions, messages are exchanged between the composed service and its partners.
- Testing the interaction with partner services:
In order to test the correctness of these interactions with respect to specification in hand, we verify the control flow (i.e. the sequence of activities execution in the BPEL process). Besides, we check if the right partner service is invoked (in case of invoke activity).
- Testing the types of variables in the messages exchanged between the BPEL process and its partner services:
In such a case, we verify the types of the variables appearing in the messages exchanged between the BPEL process and its partner services. Information about the required variable types is described in the WSDL files of each partner service.
- Testing the type of the final response sent by the BPEL to its customer:
In such a case, we verify the type of the variable appearing in the final message exchanged between the BPEL process and its invoker. Information about the required variable type is described in the WSDL and XSD files of the BPEL process.
|
|
|
