ITko Lisa Systemation

3,090 views
2,935 views

Published on

Test automation and virtualization for complex SOA based architectures

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
3,090
On SlideShare
0
From Embeds
0
Number of Embeds
56
Actions
Shares
0
Downloads
130
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • The bad news is that , although all these IT initiatives add significant value, they are also making the environment more complex. For example, moving to SOA leads to the creation of smaller services, developed by multiple teams that are highly dependent on each other. Leveraging and Extending existing applications and coupling them with new technologies leads to a more heterogeneous environment. Offshoring adds another level of complexity of requiring collaboration between teams that may be separated from each other, not only by company boundaries, but by over 10 hours time difference. Worse still, we have the news is that not only is Complexity increasing exponentially, but the rate of Change is increasing at a equal pace. The need for Agility prescribes that the environment should be able to be changed rapidly and independently. The expected cycle time of changes is dropping from months to days. Companies like IBM, SAP, Oracle, webMethods, Software AG and others are talking to you about providing platforms that allow you to make these changes rapidly. That is fine and they are very good platforms for those purposes. But if you don’t have a good strategy around risk mitigation in this complex, continuously changing environment, you are setting yourself up for a Very High Risk of Failure.<number>
  • This decoupling is achieved using the LISA Virtual Services Environment. VSE can be used to simulate the behavior of the technologies you are dependent upon, both for functional as well as load testing. In this picture, a team is trying to develop and test components on the App server. Rather than wait for live access to all of those changing and constrained pieces, or trying to replicate and maintain such a complex environment, they simply virtualize all of those dependencies away. They use VSE to simulate the behavior of the ESB, CORBA apps, databases, and other components, in essence isolating their process so they can test and deliver their own functionality much earlier in the lifecycle.
  • How it WorksHow do we do this? LISA performs live Component Level testing against your technologies – then weaves those tests together to simulate entire business workflows, and then automates these tests continuously to ensure quality.Let’s say you are trying to manage and test an application. What would you really need to do is test at every level. This type of testing is the building block of everything we do.For instance: LISA will:1. First, LISA Connects to an object on the application server, or over the Internet.2. Next, LISA gathers information about the component, showing you how it can be interacted with.3. Then, you can Invoke, or “Stimulate” that service to create a result.4. LISA then Filters the Response from that object as a behavior – you can make an assertion here as part of your testing process.5. LISA can then React to that response and invoke the next step in the testing workflow… you can Save that response data, Validate that the behavior of a component or sequence of steps, save that sequence as a business workflow, Check that workflow in deployment, create reports on the activity and performance of a set of workflows… the list goes on.What is really unique is how you can apply LISA to a workflow
  • Combine Component tests into a Workflow TestLISA does not stop at a single component or application – the test then weaves those test processes together as a Test Suite to simulate entire business workflows, and then automates these tests continuously to ensure quality.Let’s say you are trying to manage and test an application. What would you really need to do is test at every level. This type of testing is the building block of everything we do.LISA can then React to that response and invoke the next step in the testing workflow… you can Save that response data, Validate that the behavior of a component or sequence of steps, save that sequence as a business workflow, Check that workflow in deployment, create reports on the activity and performance of a set of workflows… the list goes on.What is really unique is how you can apply LISA to a workflow
  • ITko Lisa Systemation

    1. 1. Systemation Test Automation With iTKO LISA Internet: www.systemation.nl Twitter: www.twitter.com/systemation Email: info@systemation.nl
    2. 2. The IT landscape is changing Increasing Complexity • Different Platforms/Technologies • Extremely complex processes • No more total overview after a change Increasing Number of releases • Frequent changes • Frequent platform/OS patches • Need to limit testing time Increasing Reuse • Remember: Reuse is a goal • High risk of side effects after changes • Need for automated regression testing © Systemation
    3. 3. SOA testing versus traditional testing Manual Testing • Costs / Quality ratio • Repeatability • There is not enough time! User Interface Testing • The UI is not available until the end of a project • You need a stable UI before you can automate • You miss 90% in a thin UI! Testing multiple technologies • TIBCO, Oracle, Cordys, webMethods • SOA, Java/.NET, Databases • Must all be natively supported © Systemation
    4. 4. The SOA Iceberg (or why UI testing is not enough) 10% The User Interface Thin client BPM ESB The SOA based Composition 90% infrastructure Services behind the Adapters interface Legacy systems © Systemation
    5. 5. LISA Key Differentiators Best in class test automation framework for complex “SOA” based architectures in all test phases Out of the box technology adapters (For all Platforms, SOA, Java, Databases, etc.) Unique Virtualisation of application resources © Systemation
    6. 6. Cross domain Integration testing • Single solution for all technologies Portal Test ESB Verify OK BPM Verify Error Commercial Orchestration EAI EAI CRM Billing Technical Orchestration © Systemation
    7. 7. Cross domain Integration testing Systems not ready yet Portal New Development ESB BPM Commercial Orchestration EAI EAI CRM Billing Technical Orchestration Existing systems © Systemation
    8. 8. Isolation System under test LISA Virtualization LISA Test driver BPM Commercial Orchestration © Systemation
    9. 9. Current Testing Environment UDDI registry SOAP request Service1 Application under test SAP JDBC Database LISA Testing CICS Mainframe © Systemation
    10. 10. LISA VSE Decouples the Test Environment UDDI registry SOAP request Service1 Application under test CICS SAP JDBC VS1’ LISA Testing DB1’ Database MF1’ Other Testing LISA Virtual Service Manual/JUnit, Environment (VSE) Mainframe HP Service Test SOA test, etc. © Systemation
    11. 11. How LISA Tests components LISA 1 Connect  Component  2 Gather info 3 Invoke   4 Get response 5 React 6 Next Step Validate the component Apply Test Data Add test to a larger testprocess © Systemation
    12. 12. Combine Steps in a test flow Connect Component iTK Y our O S ystem LIS A Steps  iTK Connect  Y our O S ystem Test Component LIS  Gather info A Invoke   Get response Steps  React  iTK Connect  Y our O S ystem LIS  Gather info Handle Error A Invoke   Get response Connect  Verify level 1 iTK Your Steps  O System React  LIS  Gather info A Invoke   Get response Steps  React  iTK Connect  Y our O S ystem LIS  Gather info A Invoke   Get response Steps  iTK Connect  Your React  O System iTK Connect  Y our LIS  Gather info O S ystem A LIS  Gather info Invoke  A Invoke   Get response  Get response Steps  React  Steps  React  Undo action Verify level 2 Close connection © Systemation
    13. 13. LISA supported technologies • Web Technologies (SOAP, REST, …) • All major integration technologies (ESB, EAI, BPM, Messaging, Corba, …) • Web User Interfaces (HTML, AJAX, Flash, Swing, …) • Databases • Java technologies (Java, J2EE, JMS, EJB, Jdbc, Junit, RMI, …) • And more © Systemation
    14. 14. Realized Customer Benefits • Reuse of test assets throughout the project life cycle • Exchange of test assets across domains • Test early in project life cycle • Shorter test throughput time (40-50%) • Less problem analyses time (60-70%) • Less manual QA testing (40-50%) • Higher test coverage (70-80%) • Less production defects (30-40%) © Systemation
    15. 15. Test automation for complex SOA based architectures More info: www.systemation.nl

    ×