An ICT development which occurred a number of years ago is Service Oriented Architecture (SOA). An increasing number of companies use Service Oriented Architecture. A consequence of this is that IT projects became involved with software development and software testing within a Service Oriented Architecture. In a growing number of projects, it became necessary to deal with a problematic test process. The most important problem was that the test efforts became disproportionately great relative to the other disciplines in a software development process. These test problems were the reason for looking into Service Oriented Architectures and their effects on software testing.

The test challenges which are mentioned by clients and test professionals of Sogeti are summarised in the following questions:

· Are the product risks different for an SOA environment?

· How is a single service tested?

· How do you minimise the test effort for testing existing services if they are reused in a new business process?

· What is the influence of external service providers on the end-to-end tests of services?

· How can test cases and test tools be optimally reused by future test projects?

· If because of reusability and configuration SOA leads to much shorter development cycles, can we also do something to shorten our test cycles?

· Who determines that the services delivered are ready for the production environment?

In this document these questions are answered with the TMap® SOA Model.

Click here to download the whitepaper.