SOA Testing As A Service

388 views

Published on

Are services architectures compliant with service contracts ?

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
388
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

SOA Testing As A Service

  1. 1. SOA Testing As A Service Are services architectures compliant with service contracts ? Riccardo Fontanelli (Dedalus S.p.A.) riccardo.fontanelli@dedalus.eu - http://www.dedalus.eu/ Libero Maesano (Simple Engineering France s.a.r.l.) libero.maesano@simple-eng.com – http://simple-eng.comInternet of Services 2012 – 16 October 2012 - Diamant Center Brussels
  2. 2. 2 Problem statement SOA testing: MIDAS User Front End Services Why ? MIDAS Test Evaluation Planning SAUT Model MIDAS Test Generation Architecture Model Scheduling What ? Test Data How? Directives Test cases Journal Results Test cases Test cases & scenarios Test cases & scenarios & scenarios & scenarios Who ? MIDAS Test Execution Services Architecture Under Test MIDAS Where ? Test Management and Control MIDAS MIDAS TTCN-3 TTCN-3 Libraries TTCN-3 Librarie TTCN-3 Executable Librarie TTCN-3 Executable Bidirectional TTCN-3 Executable Adapters When ? ss TTCN-3 Executable message SAUT transmission TC TC Bidirectional Test Logging TC TC rpc TC How much ? MIDAS PaaSInternet of Services 2012 – 16 October 2012 - Diamant Center Brussels
  3. 3. 3 MIDAS answers• Why? – with the spreading of the digital economy - digital actors (systems and devices) collaborating without human intermediation and allowing the automation of business processes that support daily activities (e.g. e-Healthcare) – strong dependability and security of even ordinary tasks become critical issues• What? – testing is a must - formal checking and peer reviews are not enough - but the reasons for which it is necessary to test SOAs are the same that make SOA testing hard – lack of observability, trust, control of the services architecture participants – fundamental uncertainty, organizational complexity, cost, scalability• How? - automated, elastic, intelligent model-based and usage-based testing through self- provisioning• Who? – each participant’s owner can test the services architecture regions s/he is concerned with (eventually the entire architecture)• When? – if the Services Architecture Under Test (SAUT) is deployed, whenever s/he is ready to go• Where? – if the Services Architecture Under Test (SAUT) is deployed, wherever s/he is situated• How much? – pay for use Internet of Services 2012 – 16 October 2012 - Diamant Center Brussels
  4. 4. 4 The MIDAS solution MIDAS User Front End MIDAS Test MIDAS Services Evaluation Test Architecture Planning SAUT Generation Model Model Scheduling Test Data Journal Directives Test cases Results Test casesAutomated Test cases & scenarios Test cases & scenarios & scenarios & scenariosElasticIntelligent MIDAS Test Execution Services Architecture Under TestSOA Testing MIDAS MIDAS MIDAS TTCN-3 Test Management and Control TTCN-3self-service Libraries TTCN-3 Librarie TTCN-3 Executable Librarie TTCN-3 Executable Bidirectionalpay-as-you-go TTCN-3 Executable Adapters ss TTCN-3 Executable message SAUT transmission TC TC Bidirectional Test Logging TC TC rpc TC MIDAS PaaS Internet of Services 2012 – 16 October 2012 - Diamant Center Brussels
  5. 5. 5 MIDAS objectives• Framework for SOA testing automation 1. automated test suite generation (model-based, usage-based) 2. automated test run execution on a TTCN-3 engine 3. automated test evaluation, planning and dynamic scheduling based on probabilistic reasoning• Functional, interactional, security, usage-based testing – of individual digital actors (systems, devices…) – black-box testing – of large services architectures (choreographies, end-to-end transactions) – grey-box testing• Available as a Platform As A Service on cloud – self-service – pay-as-you-go – elastic, parallel, concurrent testing• Suitable for different organizational contexts and goals – acceptance, non regression, reliability, stress, debugging support … testing – failure detection, error identification, fault diagnosis• To be evaluated in two strategic domains – E-Healthcare standard services architecture (HSSP, OMG, HSSP1) – interoperability testing – Supply Chain Management services (also on mobile devices) architectures 1 Healthcare Services Specification Program (HSSP) - http://hssp.wikispaces.com/ Internet of Services 2012 – 16 October 2012 - Diamant Center Brussels
  6. 6. 6 Model-based testing• Testing is always model-based testing – at worst, the model is only in the head of the tester• Weak model-based SOA testing: testing services architecture participants’ behaviors with the help of test models + service usage models• Strong model-based SOA testing: testing services architecture participants’ behaviors with the help of service models + test models + service usage models• Service models = service contracts – not only interfaces, but also functions and external behaviors: – operations – what the provider does for the consumer (not how it does it!) – interactions - how the provider and the consumer interact in order to coordinate the service invocation, deliberation, delivery (or refusal), reporting – security - authentication, authorization, confidentiality, integrity, accountability, non repudiation – performance – volume, throughput, speed, scalability, availability, reliability, integrity, maintainability Service models are not implementation models!• Strong model-based testing is testing-by-contract !• Interoperability testing is testing against standard service contracts !• Service usage models to be confronted with service contracts• Test models are SAUT models + test purpose models• Service models (contracts) + service usage models + test models allow automatic generation of focused functional, interactional, security, and (tomorrow) performance test suites• Recommendations for testability of contracts and implementations – not any SOA can be submitted to automated, elastic, intelligent testing – strong MIDAS concern Internet of Services 2012 – 16 October 2012 - Diamant Center Brussels
  7. 7. 7 Cloud cooperation issues• Test and test data privacy - for a lot of potential customers, tests and test data are sensitive – MIDAS Framework and Platform must run on secure clouds• Legislation issues – e.g. dilemmas of European Branches of US Companies and of US Branches of European Companies – MIDAS Framework and Platform must be portable on different clouds• Interoperability – MIDAS platform interacts with large SAUTs eventually implemented on several clouds – MIDAS Platform cloud should be able to interoperate with “any” cloud – on interoperability platforms such as SOAP and REST – On request, MIDAS Platform cloud should be able to host the SAUT – the SAUT should be ported easily on the MIDAS Platform cloud• Scalability management - future development: testing SAUT against S(calability)LAs – SAUT and MIDAS Platform clouds should manage automated scalability• Other issues – we will see … Internet of Services 2012 – 16 October 2012 - Diamant Center Brussels
  8. 8. MIDAS Model and Inference Driven - Automated testing of Services architectures www.midas-project.eu THANK YOU FOR YOUR ATTENTIONInternet of Services 2012 – 16 October 2012 - Diamant Center Brussels

×