Professional Documents
Culture Documents
Wipro
Challenges
confidential
in SOA©Testing
Copyright 2007 Wipro Ltd Mr. Unnikrishnan Govindan-WiproWipro confidential © Copyright 2007 Wipro Ltd 1
Agenda
ll now..
•Testing ti
A testing
•Why is SO
different?
g – key
•SOA testin
elements
SOA – A recap..
SOA is …
An IT architectural approach that ...
Supports integration of repeatable
business tasks or linked services that ...
Can be accessed over a network when
needed, using ...
Standard interfaces
Benefits of SOA
On Demand Business
Greater alignment of business and IT
Component-based systems
Loosely coupled components and systems
A network-based infrastructure, enabling
geographically and technologically diverse
resources to work together
Greater code reuse
SOA is here!
Loose coupling
Limited view of service implementation changes
Each ‘reuse’ leads to more dependencies
Heterogeneous environment
Combination of legacy and new technologies
Test team is not used to ‘UI-less’ validation
Multiple points of failure
No clear view of point of failure
Difficult to isolate faults due to multiple layers
Security
Multiple security policies to be negotiated while
testing composite transactions
Strategy
Test early
Test services in isolation
Test all dependencies
People
Re-skill the existing test team
Induct developers into the test team
Tools
Evaluate test harnesses
Tests encompass functional, performance,
security and compliance
Knowledge of debugging tools
Compliance
Effective Service Level Management (SLM)
Define Quality of Service based on SLM
Prioritize service uptime
Collaboration
Strategy People Tools Compliance
Service
Domain for
Acceptance
SOA Impl.
Domain Client
Review & Service Acceptance Test Acceptance
Decomposition Review
Audit Plan Test
Decomposed Func. &
Domain Non-Func. Tested Service
Integration Tested
Service
All Services Service
Entry allocated Integration Test Test
Review Integration Exit
Vali- Integrate Plan Audit Vali-
Subsystem Test
Task dation Subsystems Integrated Task dation
Integration Subsystems
Integrated
Exit Entry
Subsystems
Development
Testing
Deployment
Strategy People Tools Compliance
Multi-skilled team
Functional testers
Automation
Performance Testing
Security testing
Developers (unit testing of services)
Collaborative effort
Developers and testers to be involved in test
asset creation
Quality to be owned by entire team and not
just the testers
Choose Wisely
Strategy People Tools Compliance
Performance Assurance
Service level
Integration/ interface bottlenecks
Transaction/ end-to-end test
Regulatory Board
Strategy People Tools Compliance
Project level
Governance model for interactions with
development team
Whose responsibility is it?
Q&A
www.wipro.com/testing