SOA stands for service-oriented architecture. SOA consists collection of services and these services communicate with each other. A service is a unit of work done by a service provider to achieve desired results for a service consumer. The main idea behind developing services is to achieve re-usability. A service will be designed or build by the service provider and that service will be used by the consumers depending on the need. For examples a payment gateway is an e-commerce application service provider that authorizes payments for e-businesses. Payment gateways protect credit card details by encrypting sensitive information to ensure information is passed securely between the customer and merchant
SOA and Integration testing
There is impressive rise in the use of SOA and integration to provide better business process visibility to organizations mainly Insurance and Banking sectors. The ease and low cost of integrating new systems together makes SOA a well-organized and valuable business asset. However challenge remains in testing SOA as its architecture coupled with many systems and services. So how can the testing world ensure all those crucial parts are working properly?
Integration testing is a crucial phase in SOA testing where it will give more insight to see what’s happening inside the SOA environment, communication, message flows, transformation rules. End-to-End testing identifies defects and corrects them before the defect causes serious workflow interruptions
SOA Integration testing challenges
Defects in the SOA environment is very difficult to diagnosis because data in the messages is transmitted in protocols which is inaccessible to the typical tester as a result these defects usually aren’t seen until the full system can be tested at the very end of the project which is more costly to fix
Data will be usually transmitted in the form of XML messages. Testing team has to understand and verify the various sections in the XML messages by validating against the transformation rules defined for the systems
Data communicated within the different systems will not be the same as data will be converted bases on the systems and services
SOA and integration environments are made up of many components like Web Services, enterprise service buses, legacy systems, databases and files
Role of the testers
Data will be usually transmitted in the form of XML messages. Testing team has to understand and verify the various sections in the XML messages by validating against the transformation rules defined for the systems
Data communicated within the different systems will not be the same as data will be converted bases on the systems and services
SOA and integration environments are made up of many components like Web Services, enterprise service buses, legacy systems, databases and files
Role of the testers
- Testing team should understand SOA architecture
- Use of test harness to validate message transformations and business rules
- Understand XML schemas and preparing test data based on the schema, transformation rules and business rules
- Closely working with development team some time need to become a communicator between different development teams to validate transformation rules
- Testers must be much more technical and understand how to work with SOAP, WSDLs, networking & telecommunication concepts and various platforms and technologies (Java vs .Net, Windows vs Unix/Linux vs. mainframe, etc.)
