Re: [Nmock-general] remotable mocks

[Steve F. <st...@m3...>]

Owen Rogers wrote:
> the scenario for using a remotable mock is when writing the stub code
> to communicate with a remote server.  it enables you to mock out the
> behaviour of the server without needing to hit the server.  you can
> verify that the data passed back and forth can be correctly
> marshalled, that your remoting configuration is being properly
> loaded, and that (when you use RemotingConfiguration) you are
> actually hitting the remote instance -- not simply a local instance.

This is the sort of thing we tried to avoid in the old days on the 
grounds that we didn't want unit tests to check the platform 
(marshalling) or configuration. Now we've suffered so much pain from 
configuration issues, maybe we should change our tune, as long as the 
test is really meaningful. If you're in the same building, it might be 
worth slogging the issue out with TimM.

S.