Unit testing Web service

[Vlad]

I am implementing class that uses Web service written by another and it is
not implemented yet. How can I test my class using NUnit framework without
make changes in future when web service will be implemented?

[Sami Vaaraniemi]

"Vlad" <Vl**@discussions.microsoft.com> wrote in message
news:E3**********************************@microsof t.com...

I am implementing class that uses Web service written by another and it is
not implemented yet. How can I test my class using NUnit framework without
make changes in future when web service will be implemented?

One way to test the Web Service consumer application is to use the mock
object pattern with the Web Service proxy.

All you need is the WSDL of the Web Service. Use the WSDL to generate a Web
Service proxy for the client object, and then modify the proxy to return
hard-coded responses to the client application.

As a side-note, this would be easier if the proxy generator generated
virtual methods so one could subclass the proxy and override the methods. As
it stands now, you will have to modify the generated proxy code and the
downside is that you'll lose the modifications every time the proxy is
regenerated.

Regards,
Sami

[Dilip Krishnan]

Vlad,

One way to test the Web Service consumer application is to use the
mock object pattern with the Web Service proxy.
Ideal way to proceed!

All you need is the WSDL of the Web Service. Use the WSDL to generate
a Web Service proxy for the client object, and then modify the proxy
to return hard-coded responses to the client application.

As a side-note, this would be easier if the proxy generator generated
virtual methods so one could subclass the proxy and override the
methods. As it stands now, you will have to modify the generated proxy
code and the downside is that you'll lose the modifications every time
the proxy is regenerated.

Not necessarily. You could just generate a server stub and implement the
web methods and and make the server return the dummy responses. The only
place that will be affected would be in the client side Url that the proxy
hits :)

HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dkrishnan at geniant dot com
http://www.geniant.com

[Vlad]

Thanks guys!
I understand but the class that uses web service is a singleton and clients
of this class donot have ability to setup it with implementation of web
service (mock or real proxy)? What to do in this case?
"Dilip Krishnan" wrote:

Vlad,

One way to test the Web Service consumer application is to use the
mock object pattern with the Web Service proxy.

Ideal way to proceed!

All you need is the WSDL of the Web Service. Use the WSDL to generate
a Web Service proxy for the client object, and then modify the proxy
to return hard-coded responses to the client application.

As a side-note, this would be easier if the proxy generator generated
virtual methods so one could subclass the proxy and override the
methods. As it stands now, you will have to modify the generated proxy
code and the downside is that you'll lose the modifications every time
the proxy is regenerated.

Not necessarily. You could just generate a server stub and implement the
web methods and and make the server return the dummy responses. The only
place that will be affected would be in the client side Url that the proxy
hits :)

HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dkrishnan at geniant dot com
http://www.geniant.com

[Dilip Krishnan]

Hello Vlad,
Just a wild swag at what you could do.... :) You could consider redesigning
your singleton class to control those parameters. Try this pattern [0] to
give you some insights into whats possible.
[0] - http://www.martinfowler.com/articles/injection.html
HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dkrishnan at geniant dot com
http://www.geniant.com

Thanks guys!
I understand but the class that uses web service is a singleton and
clients
of this class donot have ability to setup it with implementation of
web
service (mock or real proxy)? What to do in this case?
"Dilip Krishnan" wrote:

Vlad,

One way to test the Web Service consumer application is to use the
mock object pattern with the Web Service proxy.

Ideal way to proceed!

All you need is the WSDL of the Web Service. Use the WSDL to
generate a Web Service proxy for the client object, and then modify
the proxy to return hard-coded responses to the client application.

As a side-note, this would be easier if the proxy generator
generated virtual methods so one could subclass the proxy and
override the methods. As it stands now, you will have to modify the
generated proxy code and the downside is that you'll lose the
modifications every time the proxy is regenerated.

Not necessarily. You could just generate a server stub and implement
the web methods and and make the server return the dummy responses.
The only place that will be affected would be in the client side Url
that the proxy hits :)

HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dkrishnan at geniant dot com
http://www.geniant.com