CHOReOS Governance V&V: ParTes and ServicePot

Va

ne ss a Za

ho

ria

n &

Kri

sti

n

Lo ng

in

Di

ve

rti

m en to

N°

15

- Ph

ot

o

(c)

Eri

k To

m as

so n

Governance and V&V Framework(ParTes and ServicePot)

Final CHOReOS review 6/11/2013

Daniele Fanì – CNR, Unicam

2

Cliquez pour modifier les styles du texte du masqueDeuxième niveauTroisième niveauQuatrième niveauCinquième niveau

Governance and V&V Framework

Participant Testing

Governance

V&V

BPMN TestSuite generation and execution

ServicePot

extensible UDDI registry

3


ParTes what is it?

choreography specification

ParTes

generate skeletons as Test Cases, grouped in a Test Suite

for the integration testing

test suite for SoapUI

4


ParTes why use it?

traces to test provided by ParTes

+

A

BCT1

A

C

CT2

B

DCT3

+

choreography fragment

traces to test provided by a blind integration testing technique

CT1 → CT3 → CT2

CT3 → CT1 → CT2

CT1 → CT2 → CT3CT1 → CT3 → CT2

CT3 → CT1 → CT2CT3 → CT2 → CT1

CT2 → CT3 → CT1

CT2 → CT1 → CT3

5


ParTes how does it work?

+

A

B

CT1

A

CCT2

B

D

CT3

+

ParTes assumes that when a participant receives a message, it may change its internal state

A

B initial internal state

B B receives a message...

A B ...and changes its internal state

6



+

A

B

CT1

A

CCT2

B

D

CT3

+

A B B D

ParTes assumes that when a participant receives a message, it may change its internal state

B D A B

message sent by B, may depend by its internal state CT1 → CT3

CT3 → CT1

these two traces are considered relevant to be tested, since D may receives different messages from B

7



+

A

BCT1

A

C

CT2

B

DCT3

+ x

A

BCT1

A

C

CT3

x

A

BCT3

A

BCT1

A

BCT2

A

BCT2

avoid the parallelism just keeping only relevant traces

from parallel to exclusive choice

8


ServicePot what is it?

ServicePot

store

discovery supported

plugin

architecture

UDDI registry

choreographies, services, roles

9


ServicePot

ServicePot how does it work?

besides its features of storing/discovering, ServicePot allows to add plugins, automatically actionable before or after a ServicePot request

even ParTes can be integrated as plugin. It starts after a choreography or service registration

ServicePot console

10


• In the CHOReOS process, the services can dynamically enter and leave choreographies. Beside, a service can act in different choreographies with different roles

• The high dynamism makes difficult using classic integration testing techniques

• The problem is addressed by CHOReOS with the cooperation of two services: the registry ServicePot and the test-generator ParTes

Wrap-Up

Technology

CHOReOS Governance V&V: ParTes and ServicePot