Hi there,

Currently, when running tests that use the Moles framework to mock/stub static and sealed types, NCrunch test runner is unable to run those tests. The MSTest runner is capable of running them because it is capable of setting up a hosted process within which it can execute the tests. When running those working tests under NCrunch, you get the following exception:

Microsoft.Moles.Framework.Moles.MoleInvalidOperationException: Moles requires tests to be IN an instrumented process.

In Visual Studio Unit Test, add the following attribute to your unit test method:

[TestMethod]
[HostType("Moles")] // add this attribute
public void Test()
{ ... }

Extensions are also available for most unit test frameworks. Please refer to the Moles manual.

at Microsoft.Moles.Framework.Moles.MoleRuntime.EnsureContext()
at Microsoft.Moles.Framework.Moles.MoleBase`1.GetInstance()
at Microsoft.Moles.Framework.Moles.MoleBase`1.set_InstanceBehavior(IMoleBehavior value)
at Microsoft.Moles.Framework.Moles.MoleBase`1..ctor()

...

Of course, that attribute is already there since the MSTest runner runs them just fine. Is this something you are able to support with NCrunch or will we need to ignore all tests that use this? Ignoring would not be ideal as a large percentage of tests are using Moles to mock out SharePoint libs which are notoriously difficult to test any other way.

Thanks,
Rob

Thanks for the response Remco :)

I'd like to argue that Moles will be around a lot longer than it'll take Fakes to get established. Moles hasn't been depricated other than that they won't introduce latest changes (including the name change) into VS2010 or VS2008, but one thing is obvious, significantly more people have invested in Moles than have done so in Fakes of course. There are a VAST number if enterprise shops still running on VS2008, and a significant number who have moved to VS2010.

This is a big decision as I'm sure you're aware and *most* will not be moving to VS11 any time soon. That means that there is at least a 2-3 year window where Moles support will be welcomed.

Lastly - I'm not sure if it's possible because I haven't seen the internals, but given that the MSTest runner runs these tests perfectly well, is it not somehow possible to piggyback off of that by running it using that runner instead of the NCRunch runners where you see the special Attribute used? This would solve the need for you to wait to find out how the hosted process works. Could be a great shortcut if it's possible to invoke programmatically.

Thanks again for a great tool!
Rob