NCover / MSTEST

Looking for sites/blogs that explain thoroughly the use of NCover with MSTEST.

Thanks.

Re: Coverage over a .NET remoting connection

Not sure how you got on with this but the approach we take is to write unit tests invoking the objects by referencing the "remote" assemblies directly from our test project - i.e. take remoting completely out of the equation. From a "unit test" perspective it adds no value trying to test it as being Microsoft framework code you should just assume it "works". If you are testing client methods that invoke a method via remoting then you can use mock objects and inversion of control patterns to replace the remoting call to focus the unit tests on the client code under test.

From an integration testing perspective on the other hand you may want to test the client method invocation using the remoting infrastructure you have - but we would never run code coverage during integration testing, only during unit tests.

As for if you "really must" invoke some remoting code within your unit test - I cant help you with that part of your question as I have never tried it. It could well be a limitation of how the profiler works or Peter's implementation but I'm just guessing...

Re: Old defect in 1.3.3 - is there a workaround?

Can you only install the 2.0 runtime and then run NCover in 2.0 and your application in 1.1?

Roger

Re: Old defect in 1.3.3 - is there a workaround?

I tend to doubt it, for a variety of reasons (mostly auto-applied patches from corporate that won't be expecting .NET 2.0, or Windows installer 3.0 (which it seems to require)).

Sigh.