Mocking Static Methods Using Rhino.Mocks

Question

Is it possible to mock a static method using Rhino.Mocks? If Rhino does not support this, is there a pattern or something that would allow me to do the same?

Answer 1

Is it possible to mock a static method using Rhino.Mocks

No, It is Immpossible.

TypeMock can do this because it uses the CLR profiler to intercept and divert calls.

RhinoMocks, NMock, and Moq cannot do this because these libraries are simpler; they do not use the CLR profiler APIs. They are simpler in that they use proxies to intercept virtual members and front-end calls. The disadvantage of this simplicity is that they cannot mock certain things, such as static methods, static properties, private classes, or non-virtual instance methods.

Answer 2

Wrap the static method call in the virtual instance method in another class, and then say it.

Answer 3

If you cannot use TypeMock to intercept a method call, it is recommended that you use a template to create a proxy server that redirects to non-virtual or static methods that interest you during testing, and then set the expected value for the proxy server. To illustrate, consider the following classes.

class TypeToTest { public void Method() { } } interface ITypeToTest { void Method(); } class TypeToTestProxy : ITypeToTest { TypeToTest m_type = new TypeToTest(); public void Method() { m_type.Method(); } } 

By creating this proxy, you can now use ITypeToTest instead of where you went or installed an instance of TypeToTest , making sure that the default implementation uses TypeToTestProxy as it moves toward the actual implementation. Then you can create the ITypeToTest layout in the test code and set the expectations accordingly.

Please note that creating these proxies can be very tedious, error prone and time consuming. For this, I maintain a library and a set of tools that generate assemblies for you that contain these types. See this page for more details.

Answer 4

The only mockup framework that I know of supports legacy statics - TypeMock.

As Rytmis suggested, you need to wrap the statics with something (i.e. an instance class with virtual methods or an interface) that you can then smear.

Answer 5

This is the biggest drawback of Rhino Mocks. I do not know that Rhino Mocks is even possible to realize this without rethinking how he does his mockery.

Answer 6

I mocked moq, I don’t think we can mock static members using this because moQ creates a new proxy for the target (class or interface). Thus, only inherited members (virtual in the case of a class, public in terms of interface) can be mocked. It is clear that static members are not inherited, so the problem.