Testobjects in SOA

As usual, you need to analyze the system you want to work with in order to subdivide it into smaller pieces that you can analyze and plan the tests, section by section. Are you accustomed to working with tests on a GUI, this will be testing more unit test. These methods will of course, that in turn is called by other systems. The more you enter the unit test more difficult it becomes to keep track of what you've tested, what to test, when it should be tested, etc. The test planning, reporting, and the other work associated with managing and reporting the test process becomes much of time that need to be closed. I recommend that you put yourself at a level so you can verify the services to be published out to the consumers of services, namely SOAP interface that should be called by other systems. Other underlying parts you need and ensure that developers take care of the tests of (for example, by setting requirements for unit tests and how they are performed). Moreover, it is important that you understand what the service should do, what data is transported and how it should be converted. You need to decide whether the answer you get when a call to a service:

* Is fully respect the parameters supplied, ie that all the parameters you expected return

* Is the full respect to all the data is delivered in its entirety. A risk may be that a box somewhere cut off and returned in a shorter version than the source.

* Is the undistorted, for example, that the data did not change the data type, the characters become garbled and the like