Date post: | 19-Aug-2015 |
Category: |
Technology |
Upload: | edwin-systemation |
View: | 3,304 times |
Download: | 2 times |
© Systemation
SOA downside for testing
High Rate of Change
Highly Complex
Massive Reuse
+Increased Risk of Failure
© Systemation
The SOA Iceberg (or why UI testing is not enough)
The User InterfaceThe User Interface
The SOA based infrastructurebehind the
interface
The SOA based infrastructurebehind the
interface
10%
90%
Thin client
BPMESBCompositionServicesAdaptersLegacy systems
© Systemation
UI Testing, Error found…
Services
Customers Policies Claims ERP Credit Card System
CRMAccountingBank
S
S
S
S
S
S
SS S
S
S
S
S
S
SS
S S
SS
A+B
A+B
A+B A+B
A+B
A+B A+B
A+B
A+B
AppApp App
App
Business
Process
Applications
Legacy Applicatio
ns
© Systemation
UI Testing, User interface says OK…
Services
Customers Policies Claims ERP Credit Card System
CRMAccountingBank
S
S
S
S
S
S
SS S
S
S
S
S
S
SS
S S
SS
A+B
A+B
A+B A+B
A+B
A+B A+B
A+B
A+B
AppApp App
App
Business
Process
Applications
Legacy Applicatio
ns
© Systemation
Virtualization Example
OrderingSwing App
Processing Web App
CORBA App
ESB
Business Process App
A
Business Process App
B
Additional Apps Now &
Future
Database
Database
App ServerEJB, WS,
POJO
Load & Performance
Testers
ComponentDevelopers &
Testers
New Development
Existing systemsSystems not ready yet
© Systemation
Virtualization Example
OrderingSwing App
Processing Web App
CORBA App
ESB
Business Process App
A
Business Process App
B
Additional Apps Now &
Future
Database
Database
App ServerEJB, WS,
POJO
Load & Performance
Testers
ComponentDevelopers &
Testers
New Development
Existing systemsSystems not ready yet
Virtual servicesVirtual services
© Systemation
Introducing LISA
• Automated testing framework – Abstraction to shield the technology complexity– Point and Click interface, No scripts, no code
• Supports all major integration technologies– All ESB, BPM and EAI middleware– Both SOA and non-SOA
• Single tool for all test types– Unit, functional, regression, integration and load testing– Can be used by developers and QA
© Systemation
ComponentLISA
How LISA Tests components
1 Connect
2 Gather info
3 Invoke
4 Get response
5 React
Validate the component
Apply Test Data
Add test to a larger testprocess
6 Next Step
© Systemation
Combine Steps in a Workflow
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
Connect Component
Test Component
Handle ErrorVerify level 1
Verify level 2Undo actionClose connection
© Systemation
LISA supported technologies
• All web Technologies (SOAP, REST, …)
• All major integration technologies (ESB, EAI, BPM, Messaging, Corba, …)
– Including Tibco, Oracle/Bea, IBM, webMethods, …
• Web UI (HTML, AJAX, Flash, Swing, …)
• Databases
• Java technologies (Java, J2EE, JMS, EJB, Jdbc, Junit, RMI, …)
© Systemation
Summary
• For SOA test automation is required– Look for test automation for complex SOA based
application infrastructures– Don’t do manual testing
• Need a single solution for– All technologies + full middleware support– All test types (from unit to performance testing)– Should support both developers and QA
• Very important: Virtualization – Simplifies integration and E2E testing – Removes dependencies– Simulates assets needed for testing