Overcoming SOA testing challenges

by admin on June 22, 2011

Some people say service-oriented architecture (SOA) testing isn’t really new, that this type of testing has occurred in-house ever since there’s been middleware. However, that type of testing does differ from testing traditional applications. On top of that, SOA is being used more often, which means more of those types of applications need to be tested.

This special report takes a look at the challenges of testing SOA applications, as well as blind spots to be aware of. It also provides technical tips for conducting the different types of tests that are required.
Working with the business

Building a test system

  • Building a testing system for SOA
    Rami Jaamour discusses the best place to begin when building a testing system for SOA and how to establish a quality policy as part of the overall SOA governance strategy.

Unit testing

Functional and regression testing

  • Use functional and regression testing to validate SOA solutions
    With SOA applications, the quality of the individual services does not necessarily translate into the overall quality of the business solution. It is the quality of the whole that truly matters. In this tip, David W. Johnson explains how to use functional and regression testing to validate that SOA solutions deliver the business functionality required.

Performance testing

Security testing

  • Be aware of SOA application security issues
    Making disparate systems work together via Web services and SOA can save money, time, and frustration. But if you aren’t careful, the combination can leave you open to attack.

#SQASolutionShare on FacebookShare on Google+Share on LinkedInTweet about this on TwitterEmail this to someone

Previous post:

Next post: