Lisa

4,856 views

Published on

Complexity of SOA based testing.

Published in: Technology
  • Be the first to comment

Lisa

  1. 1. Testing Complex SOA based architectures
  2. 2. SOA downside for testing High Rate of Change Highly Complex Massive Reuse + Increased Risk of Failure
  3. 3. The SOA Iceberg (or why UI testing is not enough) 10% 90%
  4. 4. The SOA Iceberg (or why UI testing is not enough) The User Interface The SOA based infrastructure behind the interface 10% 90% Thin client BPM ESB Composition Services Adapters Legacy systems
  5. 5. UI Testing, Error found… Customers Policies Claims ERP Credit Card System CRM Accounting Bank Services S S S S S S S S S S S S S S S S S S S S A+B A+B A+B A+B A+B A+B A+B A+B A+B App App App App Business Process Applications Legacy Applications
  6. 6. UI Testing, User interface says OK… Customers Policies Claims ERP Credit Card System CRM Accounting Bank Services S S S S S S S S S S S S S S S S S S S S A+B A+B A+B A+B A+B A+B A+B A+B A+B App App App App Business Process Applications Legacy Applications
  7. 7. Virtualization Example Ordering Swing App Processing Web App CORBA App ESB Business Process App A Business Process App B Additional Apps Now & Future Database Database App Server EJB, WS, POJO Load & Performance Testers Component Developers & Testers New Development Existing systems Systems not ready yet
  8. 8. Virtualization Example Ordering Swing App Processing Web App CORBA App ESB Business Process App A Business Process App B Additional Apps Now & Future Database Database App Server EJB, WS, POJO Load & Performance Testers Component Developers & Testers New Development Existing systems Systems not ready yet Virtual services
  9. 9. Introduction LISA from iTKO
  10. 10. Introducing LISA <ul><li>Automated testing framework </li></ul><ul><ul><li>Abstraction to shield the technology complexity </li></ul></ul><ul><ul><li>Point and Click interface, No scripts, no code </li></ul></ul><ul><li>Supports all major integration technologies </li></ul><ul><ul><li>All ESB, BPM and EAI middleware </li></ul></ul><ul><ul><li>Both SOA and non-SOA </li></ul></ul><ul><li>Single tool for all test types </li></ul><ul><ul><li>Unit, functional, regression, integration and load testing </li></ul></ul><ul><ul><li>Can be used by developers and QA </li></ul></ul>
  11. 11. How LISA Tests components <ul><li>1 Connect  </li></ul><ul><li> 2 Gather info </li></ul><ul><li>3 Invoke  </li></ul><ul><li> 4 Get response </li></ul><ul><li>5 React  </li></ul>Component LISA Validate the component Apply Test Data Add test to a larger testprocess 6 Next Step
  12. 12. Combine Steps in a Workflow Connect Component Test Component Handle Error Verify level 1 Verify level 2 Undo action Close connection Your System iTKO LISA Steps  Your System iTKO LISA Connect   Gather info Invoke   Get response React  Steps  Your System iTKO LISA Connect   Gather info Invoke   Get response React  Steps  Your System iTKO LISA Connect   Gather info Invoke   Get response React  Steps  Your System iTKO LISA Connect   Gather info Invoke   Get response React  Steps  Your System iTKO LISA Connect   Gather info Invoke   Get response React  Steps  Your System iTKO LISA Connect   Gather info Invoke   Get response React  Steps 
  13. 13. LISA supported technologies <ul><li>All web Technologies (SOAP, REST, …) </li></ul><ul><li>All major integration technologies (ESB, EAI, BPM, Messaging, Corba, …) </li></ul><ul><ul><li>Including Tibco, Oracle/Bea, IBM, webMethods, … </li></ul></ul><ul><li>Web UI (HTML, AJAX, Flash, Swing, …) </li></ul><ul><li>Databases </li></ul><ul><li>Java technologies (Java, J2EE, JMS, EJB, Jdbc, Junit, RMI, …) </li></ul>
  14. 14. Summary <ul><li>For SOA test automation is required </li></ul><ul><ul><li>Look for test automation for complex SOA based application infrastructures </li></ul></ul><ul><ul><li>Don’t do manual testing </li></ul></ul><ul><li>Need a single solution for </li></ul><ul><ul><li>All technologies + full middleware support </li></ul></ul><ul><ul><li>All test types (from unit to performance testing) </li></ul></ul><ul><ul><li>Should support both developers and QA </li></ul></ul><ul><li>Very important: Virtualization </li></ul><ul><ul><li>Simplifies integration and E2E testing </li></ul></ul><ul><ul><li>Removes dependencies </li></ul></ul><ul><ul><li>Simulates assets needed for testing </li></ul></ul>

×