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.
6.
7. Cross domain Integration testing Billing EAI ESB EAI BPM Commercial Orchestration CRM Technical Orchestration Portal New Development Existing systems Systems not ready yet
8. Isolation System under test LISA Test driver LISA Virtualization BPM Commercial Orchestration
9. Current Testing Environment LISA Testing UDDI registry SOAP request Service1 SAP Database Mainframe JDBC CICS Application under test
10. LISA VSE Decouples the Test Environment LISA Testing UDDI registry Service1 SAP Database Mainframe Application under test JDBC CICS MF1’ SOAP request Other Testing Manual/JUnit, HP Service Test SOA test, etc. LISA Virtual Service Environment (VSE) VS1’ DB1’
11.
12. Combine Steps in a test flow 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.
14.
15. Test automation for complex SOA based architectures More info: www.systemation.nl
Notes de l'éditeur
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