Don't like visibility levels, change that
This came up with respect to MS MVC. The MS MVC team has decided to make some methods protected, and that makes testing using Rhino Mocks a bit of a pain.
Let us assume that I want test that the call to ProductController.Index() will render the "index.aspx" view. I can do something like:
[Test]
public void ShouldAskToRenderTheIndexAspxView()
{
MockRepository mocks = new MockRepository();
ProductController controller = mocks.PartialMock<ProductController>();
using(mocks.Record())
{
controller.RenderView("index.aspx"); // <<-- Compiler error here, RenderView is protected!
}
using (mocks.Playback())
{
controller.Index();
}
}
Problem, part of the Rhino Mocks design goal was the use of the compiler and tools as verifiers. I explicitly do not want to have strings in my code, and I put them only where I have no other choice. However, since Rhino Mocks by runtime subclassing, there is no issue with reflection calls...
This means that we can get around this limitation by using the following extension method:
public static void RenderView(this Controller self, string action)
{
typeof(Controller).GetMethod("RenderView").Invoke(self, new object[] { action} );
}
This is it, it will compile and work now.