Hello
I am not sure if this is the exact forum for this question, so if it
isnt please let me know.
I have built a web service, and i want to apply some unit testing to
the various methods i will invoke - submit(), deliver(), etc ...
Is there any 'best practice' way of doing this? Should i test using a
filter on the pipeline object or via building an extension which will
be used after serialization?
Should i even test before serialization (if that is possible)?
I really am just looking for tips on how to verify that my web service
is behaving.
If it seems like there are holes in my understanding of things
pertaining to web services, web services extensions or related
technologies, there probably are. So feel free to say, read this link
or that link...
Thanks

Hello irwin.williams@gmail.com,

Using unit test for WS u can perfom black box testing.
WS is just contract, the interface u can only see - nothing else
U only can test the range of input and output data, and validate them.

Moreover, u *must* test what's your WS do. For this reason u need a mock
class (that will represent your WS in system)
and write additional unit test for actions performing by your WS

[quoted text, click to view]
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/members/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

ok, thanks man